Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Failure of one Region does not interrupt healthy remaining regional capacity under synthetic load. However, this does not establish the required outcome: a newly added target account receives the intended stack instances while an excluded OU does not.

The released image digest is present in each target Region before workloads attempt recovery. However, this does not establish the required outcome: a newly added target account receives the intended stack instances while an excluded OU does not.

The first Region deploys, the second Region waits for approval, and rejection prevents restricted rollout. However, this does not establish the required outcome: a newly added target account receives the intended stack instances while an excluded OU does not.

One-time offline export cannot satisfy the narrow write-freeze window. The stated evidence instead indicates: Migration tasks are tracked in separate team documents with no common portfolio state.

Source virtualization format was mistaken for a guarantee of target runtime compatibility. The stated evidence instead indicates: Migration tasks are tracked in separate team documents with no common portfolio state.

A simple online copy was selected without calculating network capacity and transfer duration. The stated evidence instead indicates: Migration tasks are tracked in separate team documents with no common portfolio state.

Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance. The stated evidence instead indicates: Findings remain siloed in local account consoles and cannot be triaged centrally.

Teams confuse key material rotation with replacing the KMS key ID and losing access to old data. The stated evidence instead indicates: Findings remain siloed in local account consoles and cannot be triaged centrally.

One overbroad bucket-level policy grants both teams access to all data. The stated evidence instead indicates: Findings remain siloed in local account consoles and cannot be triaged centrally.

Threat detection remains inconsistently deployed across member accounts and Regions. The stated evidence instead indicates: Findings remain siloed in local account consoles and cannot be triaged centrally.

Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance. The stated evidence instead indicates: Findings remain siloed in local account consoles and cannot be triaged centrally.

Teams confuse key material rotation with replacing the KMS key ID and losing access to old data. The stated evidence instead indicates: Findings remain siloed in local account consoles and cannot be triaged centrally.

Every static asset fetch goes to a distant origin instead of the edge cache. The specific problem here is that instance-local caches cannot share consistent ephemeral state across horizontally scaled hosts.

Region-specific public IPs and DNS routing do not provide the needed global anycast transport optimization. The specific problem here is that instance-local caches cannot share consistent ephemeral state across horizontally scaled hosts.

No event archive exists to replay notifications that failed during downstream processing. The specific problem here is that instance-local caches cannot share consistent ephemeral state across horizontally scaled hosts.

Cluster compute totals are misleading because the needed task resources are not schedulable. The specific problem here is that capacity commitments are purchased solely from forecast without checking historical eligible use.

Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance. The specific problem here is that capacity commitments are purchased solely from forecast without checking historical eligible use.

Premium IOPS are maintained without evidence of workload needing them. The specific problem here is that capacity commitments are purchased solely from forecast without checking historical eligible use.

Fixed hot storage is retained for every object because teams cannot forecast access patterns. The stated evidence instead indicates: Storage capacity was fixed without safe growth management under variable data requirements.

Objects remain indefinitely in higher-cost storage despite a proven low-access retention pattern. The stated evidence instead indicates: Storage capacity was fixed without safe growth management under variable data requirements.

Every read request traverses the backing DynamoDB service despite highly reusable cacheable data. The stated evidence instead indicates: Storage capacity was fixed without safe growth management under variable data requirements.

Static IAM user access keys were embedded in the external CI configuration. The stated evidence instead indicates: Every static asset fetch goes to a distant origin instead of the edge cache.

Instance-local caches cannot share consistent ephemeral state across horizontally scaled hosts. The stated evidence instead indicates: Every static asset fetch goes to a distant origin instead of the edge cache.

The team assumes an x86 machine image and native binaries can run unchanged on arm64. The stated evidence instead indicates: Every static asset fetch goes to a distant origin instead of the edge cache.

Licensing constraints were omitted until after destination EC2 instances were chosen. The stated evidence instead indicates: Database engine migration was assumed to be a simple homogeneous replication job.

Migration tasks are tracked in separate team documents with no common portfolio state. The stated evidence instead indicates: Database engine migration was assumed to be a simple homogeneous replication job.

Complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration. The stated evidence instead indicates: Database engine migration was assumed to be a simple homogeneous replication job.

This action targets a different technical need: A Kinesis data stream has increasing write throttling because producers exceed the capacity of its current shard configuration. It does not replace either required solution in A or B. Kinesis stream performance depends on provisioned or on-demand capacity and balanced partition keys; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A transactional RDS workload must automatically fail over within the Region on an AZ failure. It does not replace either required solution in A or B. RDS Multi-AZ provides standby capacity for automated intra-Region failover, not read scaling by itself; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A compliance dataset is rarely accessed after 90 days but must remain recoverable with several-hour retrieval tolerance. It does not replace either required solution in A or B. Lifecycle transitions reduce storage expense only if retrieval and minimum-duration constraints fit; verify the two stated requirements independently rather than accepting an unrelated change.

Separate VPC copies and peering links were created instead of sharing centrally governed subnets. The specific problem here is that each application team is provisioning its own disconnected backbone gateway.

Local Config assessments exist but no aggregation exposes cross-account status. The specific problem here is that each application team is provisioning its own disconnected backbone gateway.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The specific problem here is that each application team is provisioning its own disconnected backbone gateway.