Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

The destination bucket is present but replication cannot use the destination KMS key. The specific problem here is that backup administrators can freely delete critical recovery points despite required immutability.

All containers share a single placement failure domain and cannot be rescheduled in time. The specific problem here is that backup administrators can freely delete critical recovery points despite required immutability.

Read-only analytical traffic saturates the production database's single writable instance. The specific problem here is that backup administrators can freely delete critical recovery points despite required immutability.

This action targets a different technical need: A legacy application has a few-hour RTO but cannot justify running the complete secondary stack continuously. It does not replace either required solution in A or B. Pilot light retains critical replicated services while reconstructing additional capacity during recovery; 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.

This action targets a different technical need: A public API has repeated abusive requests from a single source network but normal distributed traffic should continue. It does not replace either required solution in A or B. WAF rate-based rules can limit excessive HTTP request patterns by aggregation key; verify the two stated requirements independently rather than accepting an unrelated change.

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: Attackers continuously probe application URLs and security needs request-level evidence for rule tuning. It does not replace either required solution in A or B. WAF logs provide request and rule evaluation evidence for security tuning; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An EC2 fleet has low utilization and a migration team wants instance-family replacement recommendations backed by memory metrics. It does not replace either required solution in A or B. Compute Optimizer estimates rightsizing opportunities subject to compatibility and workload validation; verify the two stated requirements independently rather than accepting an unrelated change.

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

Local activity trails are not consolidated into the audit security boundary. The specific problem here is that no archive or retention mechanism was configured before the subscriber outage.

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

Static IAM user access keys were embedded in the external CI configuration. The stated evidence instead indicates: IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

Raw CloudTrail logs were collected but no managed threat-detection findings were enabled. The stated evidence instead indicates: IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

Independent release scripts lack enforceable promotion ordering and approval evidence. The stated evidence instead indicates: IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

Participant-owned permitted resources deploy into the shared subnet while networking account retains network ownership. However, this does not establish the required outcome: the consumer role reads approved encrypted objects but cannot decrypt other protected datasets.

The delegated account receives findings from participating member accounts and permitted Regions. However, this does not establish the required outcome: the consumer role reads approved encrypted objects but cannot decrypt other protected datasets.

Employees sign in using enterprise identities and receive only the mapped roles in assigned accounts. However, this does not establish the required outcome: the consumer role reads approved encrypted objects but cannot decrypt other protected datasets.

The repeated key lookup hits DAX with lower latency while noncacheable paths use the underlying table. However, this does not establish the required outcome: file-system throughput reaches target under representative concurrent processing without exhausted credits.

Failure of one Region does not interrupt healthy remaining regional capacity under synthetic load. However, this does not establish the required outcome: file-system throughput reaches target under representative concurrent processing without exhausted credits.

Records are ingested within supported throughput limits without hot-shard throttling under replayed load. However, this does not establish the required outcome: file-system throughput reaches target under representative concurrent processing without exhausted credits.

Chargeback results trace shared spend to accounted requests or accountable service consumers. However, this does not establish the required outcome: data-transfer charges drop while latency and resilience objectives still pass.

Release decisions reference tracked error rate and latency burn rather than raw instance uptime alone. However, this does not establish the required outcome: data-transfer charges drop while latency and resilience objectives still pass.

Eligible baseline compute spend receives discounts without excessive underused commitment. However, this does not establish the required outcome: data-transfer charges drop while latency and resilience objectives still pass.

Workflow state and failure recovery are hidden in fragile custom imperative scripts. The specific problem here is that shared data and internal method calls prevent independent deployment and scale.

Separate component logs cannot be correlated to customer transactions. The specific problem here is that shared data and internal method calls prevent independent deployment and scale.

The migration plan assumes a new AWS Snowball Edge device can still be ordered even though new-customer ordering is unavailable. The specific problem here is that shared data and internal method calls prevent independent deployment and scale.

A test ingress rule is flagged and corrected through the authorized remediation workflow. However, this does not establish the required outcome: pending tasks become schedulable and p95 latency improves without wasting an additional empty cluster.

Representative traffic reaches required throughput with improved CPU efficiency and no driver errors. However, this does not establish the required outcome: pending tasks become schedulable and p95 latency improves without wasting an additional empty cluster.

Each registered consumer receives an independent read-throughput path and lag falls during peak events. However, this does not establish the required outcome: pending tasks become schedulable and p95 latency improves without wasting an additional empty cluster.

Fixed EC2 capacity is provisioned 24/7 despite infrequent invocation. The specific problem here is that console-created infrastructure diverged from versioned architecture definitions.

The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability. The specific problem here is that console-created infrastructure diverged from versioned architecture definitions.

Independent release scripts lack enforceable promotion ordering and approval evidence. The specific problem here is that console-created infrastructure diverged from versioned architecture definitions.