Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Events captured during the fault can be replayed to a corrected consumer after recovery. However, this does not establish the required outcome: a poison message goes to the DLQ after configured attempts while valid following messages proceed.

A simulated transient error is retried according to policy and a persistent error follows a defined failure branch. However, this does not establish the required outcome: a poison message goes to the DLQ after configured attempts while valid following messages proceed.

The API meets latency SLOs under bursts and incurs low idle compute spend without permanently allocated hosts. However, this does not establish the required outcome: a poison message goes to the DLQ after configured attempts while valid following messages proceed.

The inspection design allows forward and return packets to use different stateful inspection appliances. The specific problem here is that there is no independently functioning VPN path when private connectivity goes down.

The team relies exclusively on retrospective end-of-month billing statements. The specific problem here is that there is no independently functioning VPN path when private connectivity goes down.

A single Direct Connect circuit creates a site-to-cloud connectivity single point of failure. The specific problem here is that there is no independently functioning VPN path when private connectivity goes down.

Revoking a staff member's assignment removes their delegated access without per-account user deletion. However, this does not establish the required outcome: production account requests are governed by the intended production policy and sandbox accounts by their own boundaries.

Traffic crosses the regional peering attachment only for specifically installed and approved prefixes. However, this does not establish the required outcome: production account requests are governed by the intended production policy and sandbox accounts by their own boundaries.

Central compliance dashboards include resource findings from configured participating accounts and Regions. However, this does not establish the required outcome: production account requests are governed by the intended production policy and sandbox accounts by their own boundaries.

Application reliability still depends on one unmanaged database host and manual restores. The specific problem here is that a one-time export leaves days of writes uncopied before final deployment.

Separate component logs cannot be correlated to customer transactions. The specific problem here is that a one-time export leaves days of writes uncopied before final deployment.

An all-at-once replacement has unacceptable outage and rollback risk. The specific problem here is that a one-time export leaves days of writes uncopied before final deployment.

Application lists omit runtime call dependencies and produce broken split-wave migrations. The specific problem here is that all assets are scheduled for direct rehost even when some are obsolete or unsuitable.

Tight synchronous coupling propagates a noncritical downstream failure to the primary transaction. The specific problem here is that all assets are scheduled for direct rehost even when some are obsolete or unsuitable.

Licensing constraints were omitted until after destination EC2 instances were chosen. The specific problem here is that all assets are scheduled for direct rehost even when some are obsolete or unsuitable.

A single-Region Aurora cluster lacks a suitable crossregional disaster recovery target. The stated evidence instead indicates: A single-Region DynamoDB table cannot accept the required local writes after that Region fails.

The inspection design allows forward and return packets to use different stateful inspection appliances. The stated evidence instead indicates: A single-Region DynamoDB table cannot accept the required local writes after that Region fails.

The backup Region exists but DNS routing never changes after primary endpoint failure. The stated evidence instead indicates: A single-Region DynamoDB table cannot accept the required local writes after that Region fails.

A standard read replica is assumed to be a synchronous multi-Region failover mechanism without promotion. The stated evidence instead indicates: A backup exists but no restore procedure or measured restore duration has been proven.

The service relies solely on application code with no rate-based edge filtering. The stated evidence instead indicates: A backup exists but no restore procedure or measured restore duration has been proven.

A single active Region was incorrectly advertised as having near-zero recovery time. The stated evidence instead indicates: A backup exists but no restore procedure or measured restore duration has been proven.

This action targets a different technical need: A busy event-routing platform must retain dropped partner events for later controlled replay after a bug fix. It does not replace either required solution in A or B. EventBridge event archives retain matching historical events for later replay; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A service currently stores a database password in deployment environment text and needs managed rotation without code updates. It does not replace either required solution in A or B. Secrets Manager can store and rotate secrets with applications retrieving current authorized values; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Business records must remain tamper-resistant during the retention period even if a security administrator compromises a backup account. It does not replace either required solution in A or B. Backup Vault Lock compliance controls can enforce retained recovery-point immutability; verify the two stated requirements independently rather than accepting an unrelated change.

Console-created infrastructure diverged from versioned architecture definitions. The stated evidence instead indicates: One abrupt DNS change replaced every consumer endpoint with no controlled canary or rollback.

Basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow. The stated evidence instead indicates: One abrupt DNS change replaced every consumer endpoint with no controlled canary or rollback.

The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability. The stated evidence instead indicates: One abrupt DNS change replaced every consumer endpoint with no controlled canary or rollback.

Events remain confined to local account buses because cross-account bus authorization is absent. The stated evidence instead indicates: Each application team is provisioning its own disconnected backbone gateway.

Individual accounts use drifting custom schedules that do not match central backup policy. The stated evidence instead indicates: Each application team is provisioning its own disconnected backbone gateway.

Overlapping network prefixes make ordinary VPC peering route selection ambiguous. The stated evidence instead indicates: Each application team is provisioning its own disconnected backbone gateway.

Failed security or smoke tests prevent production deployment while passing builds can be promoted. However, this does not establish the required outcome: the alias sends the intended approximate percentage to the canary version and reverts after a simulated alarm.

A newly added target account receives the intended stack instances while an excluded OU does not. However, this does not establish the required outcome: the alias sends the intended approximate percentage to the canary version and reverts after a simulated alarm.

Storage-class distribution follows observed access and availability constraints without extensive manual classification. However, this does not establish the required outcome: the alias sends the intended approximate percentage to the canary version and reverts after a simulated alarm.