Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Backup images exist but no continuously replicated recovery environment or launch plan is configured. The specific problem here is that every backup copy resides in the same administration boundary as the threatened workloads.

All accounts share one indiscriminate service-control policy despite different risk profiles. The specific problem here is that every backup copy resides in the same administration boundary as the threatened workloads.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The specific problem here is that every backup copy resides in the same administration boundary as the threatened workloads.

This recommendation targets a different problem: Finance collects optimizer suggestions from Compute Optimizer, Trusted Advisor and cost dashboards but counts the same recommendation more than once. Although Consolidated savings recommendations should not be summed blindly across sources, it does not directly satisfy the present scenario. The actual required acceptance result is: Tested gp3 configuration meets IO SLOs at lower monthly storage and provisioned-performance cost.

Capacity commitments are purchased solely from forecast without checking historical eligible use. The specific problem here is that premium IOPS are maintained without evidence of workload needing them.

Console edits accumulate because no one compares deployed state with infrastructure definitions. The specific problem here is that premium IOPS are maintained without evidence of workload needing them.

This action targets a different technical need: A customer-facing Lambda API has unacceptable first-request latency after inactive periods despite low average invocation cost. It does not replace either required solution in A or B. Lambda provisioned concurrency keeps selected execution environments initialized to reduce startup latency; 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: A corporate SOC needs one prioritized security findings view across enabled security services and Regions. It does not replace either required solution in A or B. Security Hub consolidates security posture and findings from participating services; verify the two stated requirements independently rather than accepting an unrelated change.

Backup administrators can freely delete critical recovery points despite required immutability. The specific problem here is that a backup exists but no restore procedure or measured restore duration has been proven.

Imperative glue retries all upstream steps and creates duplicate side effects. The specific problem here is that a backup exists but no restore procedure or measured restore duration has been proven.

Every component must be rebuilt from scratch after failure, despite a tighter RTO. The specific problem here is that a backup exists but no restore procedure or measured restore duration has been proven.

Storage capacity was fixed without safe growth management under variable data requirements. The specific problem here is that static worker capacity ignores observable demand while processing latency varies.

S3 calls egress through NAT because no supported endpoint route was configured. The specific problem here is that static worker capacity ignores observable demand while processing latency varies.

Region-specific public IPs and DNS routing do not provide the needed global anycast transport optimization. The specific problem here is that static worker capacity ignores observable demand while processing latency varies.

Failure of one Region does not interrupt healthy remaining regional capacity under synthetic load. However, this does not establish the required outcome: read replica lag is measured and promotion produces a usable independent writer during a DR drill.

A primary health-check failure leads subsequent name resolutions toward the healthy backup Region. However, this does not establish the required outcome: read replica lag is measured and promotion produces a usable independent writer during a DR drill.

The released image digest is present in each target Region before workloads attempt recovery. However, this does not establish the required outcome: read replica lag is measured and promotion produces a usable independent writer during a DR drill.

P95 latency and unit costs improve in a representative arm64 canary with all native libraries working. However, this does not establish the required outcome: the resulting image has verified packages, a traceable version and permitted availability in target accounts.

The alias sends the intended approximate percentage to the canary version and reverts after a simulated alarm. However, this does not establish the required outcome: the resulting image has verified packages, a traceable version and permitted availability in target accounts.

Identical input configurations yield reviewed deployment changes and detectable drift rather than ad hoc resources. However, this does not establish the required outcome: the resulting image has verified packages, a traceable version and permitted availability in target accounts.

Threat detection remains inconsistently deployed across member accounts and Regions. The stated evidence instead indicates: Resource-based trust was not evaluated beyond local IAM identity permission reports.

Findings remain siloed in local account consoles and cannot be triaged centrally. The stated evidence instead indicates: Resource-based trust was not evaluated beyond local IAM identity permission reports.

Administrators run sensitive maintenance scripts with no enforced approval or trail. The stated evidence instead indicates: Resource-based trust was not evaluated beyond local IAM identity permission reports.

This action targets a different technical need: A large retail monolith has tightly coupled inventory, checkout and customer modules that scale as one deployment. It does not replace either required solution in A or B. Domain-aligned service boundaries require APIs and deliberate data ownership separation; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A source MySQL workload must migrate to Amazon RDS MySQL without an engine conversion project. It does not replace either required solution in A or B. Homogeneous migrations usually focus on data replication, compatibility details and cutover rather than engine-language rewrite; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A collection of EC2 workers shares POSIX files and needs common file semantics while scaling workers separately. It does not replace either required solution in A or B. EFS provides managed shared NFS file storage for distributed Linux clients; verify the two stated requirements independently rather than accepting an unrelated change.

Management-account-only operations were mistaken for necessary daily centralized security administration. The specific problem here is that separate VPC copies and peering links were created instead of sharing centrally governed subnets.

New accounts are assembled by ad hoc scripts with inconsistent security baselines. The specific problem here is that separate VPC copies and peering links were created instead of sharing centrally governed subnets.

Savings recommendations exist in separate consoles and are double counted in spreadsheets. The specific problem here is that separate VPC copies and peering links were created instead of sharing centrally governed subnets.

This action targets a different technical need: A read-heavy reporting application needs an up-to-date secondary regional database copy that can be promoted in a disaster. It does not replace either required solution in A or B. Cross-Region read replicas are asynchronous and may require explicit promotion in recovery; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A platform team deploys the same baseline IAM roles and configuration stacks into 70 governed member accounts. It does not replace either required solution in A or B. CloudFormation StackSets manages stack instances across accounts and Regions from a controlled template; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A central security team needs automated detections for unusual cross-account API activity and suspected credential misuse. It does not replace either required solution in A or B. GuardDuty consumes AWS data sources to identify suspicious behavior and report findings; verify the two stated requirements independently rather than accepting an unrelated change.