Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: A Route 53 failover policy must move users between two independent public endpoints when the primary application fails. It does not replace either required solution in A or B. DNS health-based failover changes record responses, but clients may cache prior results; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A product catalog on DynamoDB receives many repeated eventually consistent key lookups and requires microsecond cache responses. It does not replace either required solution in A or B. DAX offers managed in-memory caching for eligible DynamoDB read workloads; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A queue-backed worker fleet is underloaded overnight but still runs a fixed large number of instances. It does not replace either required solution in A or B. Queue-driven scaling aligns paid worker capacity with outstanding workload; verify the two stated requirements independently rather than accepting an unrelated change.

Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO. The specific problem here is that no event archive exists to replay notifications that failed during downstream processing.

Imperative glue retries all upstream steps and creates duplicate side effects. The specific problem here is that no event archive exists to replay notifications that failed during downstream processing.

DNS simple routing cannot automatically reflect the application's health. The specific problem here is that no event archive exists to replay notifications that failed during downstream processing.

Complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration. The specific problem here is that all analytics jobs depend on a single custom ETL server and its directly attached storage.

Always-on monolith capacity is required merely to handle infrequent independent endpoints. The specific problem here is that all analytics jobs depend on a single custom ETL server and its directly attached storage.

Tight synchronous coupling propagates a noncritical downstream failure to the primary transaction. The specific problem here is that all analytics jobs depend on a single custom ETL server and its directly attached storage.

DNS simple routing cannot automatically reflect the application's health. The specific problem here is that single-AZ database storage and compute are a single zonal failure domain.

Instance capacity is pinned to one zone with no automated target recovery. The specific problem here is that single-AZ database storage and compute are a single zonal failure domain.

The destination bucket is present but replication cannot use the destination KMS key. The specific problem here is that single-AZ database storage and compute are a single zonal failure domain.

Discount usage improves with fewer unused reservation hours and measured baseline cost changes. However, this does not establish the required outcome: new instances become healthy before major traffic shift and rollback restores the previous code path.

Failed deliveries retry under the configured policy and exhausted messages reach the DLQ. However, this does not establish the required outcome: new instances become healthy before major traffic shift and rollback restores the previous code path.

The stack tolerates the injected zonal fault and stop alarms terminate experiments as planned. However, this does not establish the required outcome: new instances become healthy before major traffic shift and rollback restores the previous code path.

Always-on monolith capacity is required merely to handle infrequent independent endpoints. The specific problem here is that application reliability still depends on one unmanaged database host and manual restores.

Developers assume SQS has identical JMS or broker feature semantics to the source stack. The specific problem here is that application reliability still depends on one unmanaged database host and manual restores.

Complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration. The specific problem here is that application reliability still depends on one unmanaged database host and manual restores.

A primary health-check failure leads subsequent name resolutions toward the healthy backup Region. However, this does not establish the required outcome: terminating all instances in one zone leaves healthy targets and Auto Scaling replaces lost capacity.

Read latency and writer CPU improve under reporting load without routing writes to read replicas. However, this does not establish the required outcome: terminating all instances in one zone leaves healthy targets and Auto Scaling replaces lost capacity.

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: terminating all instances in one zone leaves healthy targets and Auto Scaling replaces lost capacity.

This action targets a different technical need: A noncritical archive service has a 24-hour RTO and may restore its configuration and data from protected backups. It does not replace either required solution in A or B. Backup-and-restore DR suits longer RTO targets when restore execution is practiced; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A shared EFS file system slows a data-processing batch even though compute workers are mostly idle. It does not replace either required solution in A or B. EFS throughput characteristics must match concurrent IO patterns and required sustained rate; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A revenue-critical public endpoint requires proactive DDoS response coordination and protected eligible application resources. It does not replace either required solution in A or B. Shield Advanced adds advanced DDoS protection and response support for supported resources; verify the two stated requirements independently rather than accepting an unrelated change.

Config findings are left as unactioned notifications while risky drift remains exposed. The stated evidence instead indicates: Untracked imperative orchestration repeats previous side effects after transient failures.

Metrics and logs are not organized into actionable per-service operational signals. The stated evidence instead indicates: Untracked imperative orchestration repeats previous side effects after transient failures.

Capacity planning ignores demand spikes or hot keys that concentrate requests. The stated evidence instead indicates: Untracked imperative orchestration repeats previous side effects after transient failures.

Individual Security Hub instances were not centrally delegated or aggregated. The stated evidence instead indicates: Resource policies were never checked for access beyond the organization's trust boundary.

Individual IAM users were being created per account instead of using centralized workforce federation. The stated evidence instead indicates: Resource policies were never checked for access beyond the organization's trust boundary.

The team relies exclusively on retrospective end-of-month billing statements. The stated evidence instead indicates: Resource policies were never checked for access beyond the organization's trust boundary.

This action targets a different technical need: Two Regions are deployed but customer requests stay routed to the failed primary endpoint indefinitely. It does not replace either required solution in A or B. DNS failover needs a health-signal and routing policy that actually switches answers; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Operations retains detached EBS volumes after instance termination and pays for unused storage for months. It does not replace either required solution in A or B. EBS storage billing continues for allocated volumes until they are deleted or otherwise changed; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An EC2 application needs sustained random IOPS independent of EBS volume storage-size growth. It does not replace either required solution in A or B. gp3 separates baseline volume storage size from configurable IOPS and throughput within limits; verify the two stated requirements independently rather than accepting an unrelated change.