Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Only source-region S3 versioning is enabled, but no replication rule or role exists. The stated evidence instead indicates: Backup images exist but no continuously replicated recovery environment or launch plan is configured.

New accounts are assembled by ad hoc scripts with inconsistent security baselines. The stated evidence instead indicates: Backup images exist but no continuously replicated recovery environment or launch plan is configured.

A single-Region Aurora cluster lacks a suitable crossregional disaster recovery target. The stated evidence instead indicates: Backup images exist but no continuously replicated recovery environment or launch plan is configured.

A simple online copy was selected without calculating network capacity and transfer duration. The stated evidence instead indicates: Source virtualization format was mistaken for a guarantee of target runtime compatibility.

Local instance disks are wrongly used as a shared durable POSIX file system. The stated evidence instead indicates: Source virtualization format was mistaken for a guarantee of target runtime compatibility.

Migration tasks are tracked in separate team documents with no common portfolio state. The stated evidence instead indicates: Source virtualization format was mistaken for a guarantee of target runtime compatibility.

Operational excellence requires observable application SLOs tied to business-critical behavior. The two requirements instead call for these controls: (A) Gate a least-privilege Systems Manager Automation runbook with an aws:approve step and retain change approval and execution records; (B) Use S3 Access Points or carefully scoped bucket policies to isolate each team's required object prefixes.

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: 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: An internal monolithic API has independently scalable request handlers and low idle traffic. It does not replace either required solution in A or B. Serverless APIs can separate scaling from continuously provisioned application servers; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A legacy data center lacks a trustworthy inventory of server CPU, memory, installed processes and network connections. It does not replace either required solution in A or B. Application discovery captures real workload characteristics needed for migration planning; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An ecommerce backend repeatedly recomputes expensive reads for product listings that change infrequently. It does not replace either required solution in A or B. Correct cache placement and invalidation reduce repeated work without violating freshness needs; verify the two stated requirements independently rather than accepting an unrelated change.

The delegated account receives findings from participating member accounts and permitted Regions. However, this does not establish the required outcome: the assumed session can read the approved prefix and is denied a separate confidential prefix.

A simulated Direct Connect failure moves approved routes to VPN tunnels and restore reverses route preference. However, this does not establish the required outcome: the assumed session can read the approved prefix and is denied a separate confidential prefix.

The consumer role reads approved encrypted objects but cannot decrypt other protected datasets. However, this does not establish the required outcome: the assumed session can read the approved prefix and is denied a separate confidential prefix.

Failed notifications disappear because no supported retry and DLQ design is in place. The stated evidence instead indicates: Snapshot creation is mistaken for proof the application can actually be restored.

Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance. The stated evidence instead indicates: Snapshot creation is mistaken for proof the application can actually be restored.

The application is exposed to one database host or zonal compute failure. The stated evidence instead indicates: Snapshot creation is mistaken for proof the application can actually be restored.

Backup images exist but no continuously replicated recovery environment or launch plan is configured. The stated evidence instead indicates: Teams have only aggregate bills and cannot locate the source of inefficient storage usage.

On-demand usage was left wholly uncommitted despite predictable baseline compute consumption. The stated evidence instead indicates: Teams have only aggregate bills and cannot locate the source of inefficient storage usage.

Instances were resized from average CPU alone despite memory or traffic constraints. The stated evidence instead indicates: Teams have only aggregate bills and cannot locate the source of inefficient storage usage.

This action targets a different technical need: An SNS topic invokes an asynchronous HTTP subscriber with intermittent failures and business needs controlled redelivery. It does not replace either required solution in A or B. SNS subscriber reliability relies on delivery retries and appropriately configured dead-letter destinations; 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.

This action targets a different technical need: A Kinesis stream has adequate shard write capacity but multiple consumers compete for read throughput and fall behind. It does not replace either required solution in A or B. Kinesis enhanced fan-out provides dedicated consumer read throughput within service limits; verify the two stated requirements independently rather than accepting an unrelated change.

Cluster compute totals are misleading because the needed task resources are not schedulable. The stated evidence instead indicates: Misses from different edge caches repeatedly burden the same origin.

Gp2 capacity-linked performance assumptions lead to wasteful storage growth. The stated evidence instead indicates: Misses from different edge caches repeatedly burden the same origin.

Administrators run sensitive maintenance scripts with no enforced approval or trail. The stated evidence instead indicates: Misses from different edge caches repeatedly burden the same origin.

This action targets a different technical need: Network administrators must manage a shared subnet centrally while application accounts place their own resources in it. It does not replace either required solution in A or B. VPC sharing separates network ownership from application resource ownership; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A customer database needs a near-real-time cross-Region read replica and an established disaster recovery promotion procedure. It does not replace either required solution in A or B. Aurora Global Database supports low-latency crossregional replication with explicit recovery operations; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Employees across dozens of AWS accounts must use one corporate identity provider and centrally standardized account assignments. It does not replace either required solution in A or B. IAM Identity Center coordinates workforce SSO permission sets across accounts; verify the two stated requirements independently rather than accepting an unrelated change.

A single Direct Connect circuit creates a site-to-cloud connectivity single point of failure. The specific problem here is that the inspection design allows forward and return packets to use different stateful inspection appliances.

The architecture assumes that Transit Gateway peering automatically propagates interregional routes. The specific problem here is that the inspection design allows forward and return packets to use different stateful inspection appliances.

Each business unit manually maintains duplicative IAM users in workload accounts. The specific problem here is that the inspection design allows forward and return packets to use different stateful inspection appliances.