Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Local Config assessments exist but no aggregation exposes cross-account status. The specific problem here is that a single-Region Aurora cluster lacks a suitable crossregional disaster recovery target.

No archive or retention mechanism was configured before the subscriber outage. The specific problem here is that a single-Region Aurora cluster lacks a suitable crossregional disaster recovery target.

A single-Region DynamoDB table cannot accept the required local writes after that Region fails. The specific problem here is that a single-Region Aurora cluster lacks a suitable crossregional disaster recovery target.

Restoring a suitable past timestamp creates a usable table with correct records. However, this does not establish the required outcome: unhealthy containers leave active target selection promptly while healthy targets continue receiving requests.

That evidence is associated with a separate architecture requirement: A mission-critical RDS instance is single-AZ and routine maintenance causes extended application downtime. It does not prove that this case was remediated. The relevant observation must be: Unhealthy containers leave active target selection promptly while healthy targets continue receiving requests. The associated design principle is: Load balancer health checks must match actual application readiness rather than superficial liveness.

New cryptographic material is used when rotation occurs while previously encrypted data remains decryptable. However, this does not establish the required outcome: unhealthy containers leave active target selection promptly while healthy targets continue receiving requests.

The application is exposed to one database host or zonal compute failure. The stated evidence instead indicates: Health checks use an unrelated always-200 endpoint that does not reflect the service readiness.

Administrators run sensitive maintenance scripts with no enforced approval or trail. The stated evidence instead indicates: Health checks use an unrelated always-200 endpoint that does not reflect the service readiness.

In-place mass deployment removed rollback capacity before verifying the new version. The stated evidence instead indicates: Health checks use an unrelated always-200 endpoint that does not reflect the service readiness.

Orders complete independently of notification delays, while consumers process retries and duplicate deliveries safely. However, this does not establish the required outcome: the proposed target design has documented permitted license use and tracked license utilization.

Owners can trace migration milestones and blockers for each workload without conflicting local spreadsheets. However, this does not establish the required outcome: the proposed target design has documented permitted license use and tracked license utilization.

Captured workload attributes reveal which servers can be rehosted together and which need further assessment. However, this does not establish the required outcome: the proposed target design has documented permitted license use and tracked license utilization.

This action targets a different technical need: A high-throughput EC2 network service shows packet processing CPU saturation and must exploit modern instance network acceleration. It does not replace either required solution in A or B. Enhanced networking capabilities require compatible instance types and operating-system drivers; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A DynamoDB application requires recovery from accidental writes to an earlier point within a month. It does not replace either required solution in A or B. DynamoDB PITR restores to a selected point within its available recovery window; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A public S3 bucket and KMS key unexpectedly trust principals outside the company's AWS organization. It does not replace either required solution in A or B. Access Analyzer detects eligible resource trust outside its zone of trust; verify the two stated requirements independently rather than accepting an unrelated change.

The dominant query wait events can be linked to the observed transaction latency. However, this does not establish the required outcome: burst replay avoids throttling while partition-level demand remains within supported constraints.

Origin request count drops under a multi-edge cache miss test while freshness remains correct. However, this does not establish the required outcome: burst replay avoids throttling while partition-level demand remains within supported constraints.

Security Hub centrally displays eligible standardized findings with source context preserved. However, this does not establish the required outcome: burst replay avoids throttling while partition-level demand remains within supported constraints.

Unhealthy containers leave active target selection promptly while healthy targets continue receiving requests. However, this does not establish the required outcome: restoring a suitable past timestamp creates a usable table with correct records.

Failed deliveries retry under the configured policy and exhausted messages reach the DLQ. However, this does not establish the required outcome: restoring a suitable past timestamp creates a usable table with correct records.

Release decisions reference tracked error rate and latency burn rather than raw instance uptime alone. However, this does not establish the required outcome: restoring a suitable past timestamp creates a usable table with correct records.

Administrators run sensitive maintenance scripts with no enforced approval or trail. The stated evidence instead indicates: WAF rules are deployed without visibility into which requests they affect.

Threat detection remains inconsistently deployed across member accounts and Regions. The stated evidence instead indicates: WAF rules are deployed without visibility into which requests they affect.

CloudTrail management events are not retained or centrally available for review. The stated evidence instead indicates: WAF rules are deployed without visibility into which requests they affect.

One abrupt DNS change replaced every consumer endpoint with no controlled canary or rollback. The specific problem here is that independent release scripts lack enforceable promotion ordering and approval evidence.

In-place overwriting of every production instance removed the healthy comparison environment. The specific problem here is that independent release scripts lack enforceable promotion ordering and approval evidence.

Imperative glue retries all upstream steps and creates duplicate side effects. The specific problem here is that independent release scripts lack enforceable promotion ordering and approval evidence.

Snapshot creation is mistaken for proof the application can actually be restored. The stated evidence instead indicates: One overbroad bucket-level policy grants both teams access to all data.

WAF rules are deployed without visibility into which requests they affect. The stated evidence instead indicates: One overbroad bucket-level policy grants both teams access to all data.

CloudTrail management events are not retained or centrally available for review. The stated evidence instead indicates: One overbroad bucket-level policy grants both teams access to all data.

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 high-traffic EC2 service must release a risky version while keeping a rapid rollback path and without terminating all healthy targets at once. It does not replace either required solution in A or B. Blue-green deployment separates old and new environments to support safe traffic shifting; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Large fault-tolerant batch analytics jobs can be interrupted and resumed while the team pays full on-demand prices. It does not replace either required solution in A or B. Spot Instances optimize interruptible capacity costs when jobs tolerate reclaim events; verify the two stated requirements independently rather than accepting an unrelated change.