Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

No archive or retention mechanism was configured before the subscriber outage. The specific problem here is that synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

Per-account one-off inspections do not continuously evaluate drift across accounts. The specific problem here is that synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

A single-Region Aurora cluster lacks a suitable crossregional disaster recovery target. The specific problem here is that synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

Every component must be rebuilt from scratch after failure, despite a tighter RTO. The stated evidence instead indicates: All containers share a single placement failure domain and cannot be rescheduled in time.

A single active Region was incorrectly advertised as having near-zero recovery time. The stated evidence instead indicates: All containers share a single placement failure domain and cannot be rescheduled in time.

Instance capacity is pinned to one zone with no automated target recovery. The stated evidence instead indicates: All containers share a single placement failure domain and cannot be rescheduled in time.

On-premises DNS has no forwarding path into the VPC's Route 53 Resolver. The stated evidence instead indicates: A single Direct Connect circuit creates a site-to-cloud connectivity single point of failure.

A broad VPC peering link was used where a service-scoped private access path was needed. The stated evidence instead indicates: A single Direct Connect circuit creates a site-to-cloud connectivity single point of failure.

An overly broad assumed-role session is not constrained to the vendor's assigned resources. The stated evidence instead indicates: A single Direct Connect circuit creates a site-to-cloud connectivity single point of failure.

The abusive source crosses its request threshold and is blocked without blocking allowed sample traffic. However, this does not establish the required outcome: small traffic shares move to the new stack first; an error alarm redirects traffic to the proven stack.

Identical input configurations yield reviewed deployment changes and detectable drift rather than ad hoc resources. However, this does not establish the required outcome: small traffic shares move to the new stack first; an error alarm redirects traffic to the proven stack.

Requests switch to the replacement environment only after health tests pass, and rollback returns traffic to old targets. However, this does not establish the required outcome: small traffic shares move to the new stack first; an error alarm redirects traffic to the proven stack.

A single Direct Connect circuit creates a site-to-cloud connectivity single point of failure. The specific problem here is that the architecture assumes that Transit Gateway peering automatically propagates interregional routes.

Separate point-to-point VPC peering connections lack transitive routing and are difficult to govern at scale. The specific problem here is that the architecture assumes that Transit Gateway peering automatically propagates interregional routes.

The remote principal has S3 object access but lacks required key-policy and IAM decrypt permission. The specific problem here is that the architecture assumes that Transit Gateway peering automatically propagates interregional routes.

Eligible new source objects replicate with appropriate destination encryption and remain readable during source outage. However, this does not establish the required outcome: a regional drill scales warm standby to full capacity within the stated recovery time and data tolerance.

The load balancer continues serving from healthy remaining tasks during a forced zone failure. However, this does not establish the required outcome: a regional drill scales warm standby to full capacity within the stated recovery time and data tolerance.

Free storage stays above emergency thresholds while capacity grows within policy rather than being oversized initially. However, this does not establish the required outcome: a regional drill scales warm standby to full capacity within the stated recovery time and data tolerance.

This action targets a different technical need: A shared API must protect downstream capacity during a request spike without losing monitoring of throttled clients. It does not replace either required solution in A or B. API Gateway throttle controls bound request rates but callers should handle 429 responses; 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: Unpredictably accessed objects are retained for a year, but no reliable access-frequency segmentation is known. It does not replace either required solution in A or B. S3 Intelligent-Tiering can move eligible objects among access tiers based on access frequency; verify the two stated requirements independently rather than accepting an unrelated change.

The selected time window can be replayed to the target bus without inventing events that were never archived. However, this does not establish the required outcome: draining all nodes in one zone still leaves enough healthy replicas serving traffic from others.

Employees sign in using enterprise identities and receive only the mapped roles in assigned accounts. However, this does not establish the required outcome: draining all nodes in one zone still leaves enough healthy replicas serving traffic from others.

Writes in either Region replicate to the other and conflict handling matches the business design. However, this does not establish the required outcome: draining all nodes in one zone still leaves enough healthy replicas serving traffic from others.

On-demand initialization latency is not addressed for the critical invocation path. The stated evidence instead indicates: Shared per-shard read throughput is divided among too many polling consumers.

Capacity planning ignores demand spikes or hot keys that concentrate requests. The stated evidence instead indicates: Shared per-shard read throughput is divided among too many polling consumers.

Config findings are left as unactioned notifications while risky drift remains exposed. The stated evidence instead indicates: Shared per-shard read throughput is divided among too many polling consumers.

The team assumes an x86 machine image and native binaries can run unchanged on arm64. The stated evidence instead indicates: Single-AZ database storage and compute are a single zonal failure domain.

No event archive exists to replay notifications that failed during downstream processing. The stated evidence instead indicates: Single-AZ database storage and compute are a single zonal failure domain.

DNS simple routing cannot automatically reflect the application's health. The stated evidence instead indicates: Single-AZ database storage and compute are a single zonal failure domain.

Static security policy documents are not technically enforced against resource drift. The specific problem here is that console edits accumulate because no one compares deployed state with infrastructure definitions.

Uncorrelated logs hide where the end-to-end latency accumulates. The specific problem here is that console edits accumulate because no one compares deployed state with infrastructure definitions.

Service-specific Health notifications are not routed into incident processes. The specific problem here is that console edits accumulate because no one compares deployed state with infrastructure definitions.