Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow. The stated evidence instead indicates: Independent release scripts lack enforceable promotion ordering and approval evidence.

Individual account stacks were created manually and drift from the approved baseline. The stated evidence instead indicates: Independent release scripts lack enforceable promotion ordering and approval evidence.

One abrupt DNS change replaced every consumer endpoint with no controlled canary or rollback. The stated evidence instead indicates: Independent release scripts lack enforceable promotion ordering and approval evidence.

No event archive exists to replay notifications that failed during downstream processing. The specific problem here is that every reporting query was sent to the cluster writer endpoint despite available readers.

A backup exists but no restore procedure or measured restore duration has been proven. The specific problem here is that every reporting query was sent to the cluster writer endpoint despite available readers.

Unbounded request bursts overload backends because no gateway rate protection is configured. The specific problem here is that every reporting query was sent to the cluster writer endpoint despite available readers.

Traffic crosses the regional peering attachment only for specifically installed and approved prefixes. However, this does not establish the required outcome: cost and Usage Reports or Cost Explorer show tagged team spend after activation and reporting delay.

Tested resized instances meet p95 latency goals while recommended savings are observed. However, this does not establish the required outcome: cost and Usage Reports or Cost Explorer show tagged team spend after activation and reporting delay.

Dashboards identify targeted buckets with abnormal storage patterns and lifecycle candidates. However, this does not establish the required outcome: cost and Usage Reports or Cost Explorer show tagged team spend after activation and reporting delay.

CloudTrail management events are not retained or centrally available for review. The specific problem here is that role policies retain privileges indefinitely without evidence about actual service usage.

Threat detection remains inconsistently deployed across member accounts and Regions. The specific problem here is that role policies retain privileges indefinitely without evidence about actual service usage.

Failed notifications disappear because no supported retry and DLQ design is in place. The specific problem here is that role policies retain privileges indefinitely without evidence about actual service usage.

Instance capacity is pinned to one zone with no automated target recovery. The specific problem here is that dNS simple routing cannot automatically reflect the application's health.

Route 53 active-passive failover requires a matched primary and secondary failover record, with a health check or supported alias health evaluation directing queries to a healthy standby. A primary record plus TTL testing cannot divert traffic to a missing secondary.

Repeated retries of one failed message prevent useful error isolation and redrive workflow. The specific problem here is that dNS simple routing cannot automatically reflect the application's health.

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: Several member accounts buy overlapping Reserved Instances, yet unused reservations remain in the organization. It does not replace either required solution in A or B. RI coverage should be evaluated at consolidated billing scope where sharing is enabled; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Hundreds of EC2 hosts need scheduled patch windows with evidence of patch compliance and approved maintenance boundaries. It does not replace either required solution in A or B. Systems Manager supports fleet patching with centralized baselines and maintenance windows; verify the two stated requirements independently rather than accepting an unrelated change.

Mainframe batch and transaction semantics were treated as if they were ordinary Linux workloads. The stated evidence instead indicates: All consumers wait for a nightly export despite a near-real-time freshness requirement.

Workflow state and failure recovery are hidden in fragile custom imperative scripts. The stated evidence instead indicates: All consumers wait for a nightly export despite a near-real-time freshness requirement.

Shared data and internal method calls prevent independent deployment and scale. The stated evidence instead indicates: All consumers wait for a nightly export despite a near-real-time freshness requirement.

This action targets a different technical need: A platform team learns about upcoming service maintenance only after workloads start failing. It does not replace either required solution in A or B. AWS Health can surface AWS-side events relevant to affected resources and accounts; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A global media site sends repeated uncached misses to an expensive origin even with widespread CloudFront edge caches. It does not replace either required solution in A or B. CloudFront Origin Shield can consolidate cache misses through an additional regional layer; 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.

Savings recommendations exist in separate consoles and are double counted in spreadsheets. The stated evidence instead indicates: Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

No archive or retention mechanism was configured before the subscriber outage. The stated evidence instead indicates: 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 stated evidence instead indicates: Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

Shared data and internal method calls prevent independent deployment and scale. The specific problem here is that complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration.

Partners are forced to replace SFTP clients with AWS SDK calls without business approval. The specific problem here is that complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration.

Replicating table data alone does not translate incompatible source SQL constructs. The specific problem here is that complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration.

This action targets a different technical need: Finance collects optimizer suggestions from Compute Optimizer, Trusted Advisor and cost dashboards but counts the same recommendation more than once. It does not replace either required solution in A or B. Consolidated savings recommendations should not be summed blindly across sources; verify the two stated requirements independently rather than accepting an unrelated change.

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: Hundreds of EC2 hosts need scheduled patch windows with evidence of patch compliance and approved maintenance boundaries. It does not replace either required solution in A or B. Systems Manager supports fleet patching with centralized baselines and maintenance windows; verify the two stated requirements independently rather than accepting an unrelated change.