Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Read replica lag is measured and promotion produces a usable independent writer during a DR drill. However, this does not establish the required outcome: a drill scales the secondary stack from its minimal footprint within the agreed RTO.

An unauthorized attempt to delete a protected recovery point is denied before retention expires. However, this does not establish the required outcome: a drill scales the secondary stack from its minimal footprint within the agreed RTO.

The released image digest is present in each target Region before workloads attempt recovery. However, this does not establish the required outcome: a drill scales the secondary stack from its minimal footprint within the agreed RTO.

Local activity trails are not consolidated into the audit security boundary. The specific problem here is that per-account one-off inspections do not continuously evaluate drift across accounts.

Public ACM-issued certificates were wrongly assumed to provide a corporate private CA chain. The specific problem here is that per-account one-off inspections do not continuously evaluate drift across accounts.

Local identity permissions were incorrectly treated as overriding organizational guardrails. The specific problem here is that per-account one-off inspections do not continuously evaluate drift across accounts.

Source virtualization format was mistaken for a guarantee of target runtime compatibility. The stated evidence instead indicates: Migration estimates are based solely on outdated procurement records rather than measured workload behavior.

Mainframe batch and transaction semantics were treated as if they were ordinary Linux workloads. The stated evidence instead indicates: Migration estimates are based solely on outdated procurement records rather than measured workload behavior.

Database engine migration was assumed to be a simple homogeneous replication job. The stated evidence instead indicates: Migration estimates are based solely on outdated procurement records rather than measured workload behavior.

Static worker capacity ignores observable demand while processing latency varies. The stated evidence instead indicates: Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO.

Backup administrators can freely delete critical recovery points despite required immutability. The stated evidence instead indicates: Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO.

A single active Region was incorrectly advertised as having near-zero recovery time. The stated evidence instead indicates: Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO.

Static security policy documents are not technically enforced against resource drift. The specific problem here is that threat detection remains inconsistently deployed across member accounts and Regions.

CloudTrail management events are not retained or centrally available for review. The specific problem here is that threat detection remains inconsistently deployed across member accounts and Regions.

Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance. The specific problem here is that threat detection remains inconsistently deployed across member accounts and Regions.

Shared costs are assigned by arbitrary percentage without service consumption evidence. The stated evidence instead indicates: Unattached volumes are treated as free merely because they are not mounted.

Patch application is manual and lacks consistent baseline selection and change evidence. The stated evidence instead indicates: Unattached volumes are treated as free merely because they are not mounted.

Potential savings from the same infrastructure change are double counted in separate reports. The stated evidence instead indicates: Unattached volumes are treated as free merely because they are not mounted.

Each application team is provisioning its own disconnected backbone gateway. The stated evidence instead indicates: The team relies exclusively on retrospective end-of-month billing statements.

Resource tags were never activated as billing cost allocation dimensions. The stated evidence instead indicates: The team relies exclusively on retrospective end-of-month billing statements.

Teams have only aggregate bills and cannot locate the source of inefficient storage usage. The stated evidence instead indicates: The team relies exclusively on retrospective end-of-month billing statements.

This action targets a different technical need: A public application must divert DNS traffic away from an endpoint when health checks show it has failed. It does not replace either required solution in A or B. DNS failover requires health-aware routing and realistic expectations for cached answers; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A steady service has predictable cross-family compute usage and seeks discounts without binding to one EC2 instance family. It does not replace either required solution in A or B. Compute Savings Plans discount eligible compute spending with an hourly commitment; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A global static web application experiences high latency because users repeatedly fetch unchanged assets from one Region. It does not replace either required solution in A or B. CloudFront edge caching reduces origin fetches for cacheable content; verify the two stated requirements independently rather than accepting an unrelated change.

Workload service calls repeatedly cross paid network boundaries without quantified need. The specific problem here is that teams purchase more RIs independently without measuring existing shared coverage.

Shared costs are assigned by arbitrary percentage without service consumption evidence. The specific problem here is that teams purchase more RIs independently without measuring existing shared coverage.

Health checks use an unrelated always-200 endpoint that does not reflect the service readiness. The specific problem here is that teams purchase more RIs independently without measuring existing shared coverage.

Cross-account access findings identify external principals and clear only when permissions are corrected. However, this does not establish the required outcome: team A reads only its permitted dataset and an attempt to fetch team B's restricted dataset is rejected.

Pending tasks become schedulable and p95 latency improves without wasting an additional empty cluster. However, this does not establish the required outcome: team A reads only its permitted dataset and an attempt to fetch team B's restricted dataset is rejected.

Existing and new participating accounts report eligible findings to the delegated administrator. However, this does not establish the required outcome: team A reads only its permitted dataset and an attempt to fetch team B's restricted dataset is rejected.