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: Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

The backup Region exists but DNS routing never changes after primary endpoint failure. The stated evidence instead indicates: Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

Individual IAM users were being created per account instead of using centralized workforce federation. The stated evidence instead indicates: Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

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: An incident reviewer needs a timeline of a suspicious IAM policy change made across member accounts. It does not replace either required solution in A or B. CloudTrail API event evidence supports investigation of changes to account control-plane resources; verify the two stated requirements independently rather than accepting an unrelated change.

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.

Individual IAM users were being created per account instead of using centralized workforce federation. The stated evidence instead indicates: Disjoint local-account trails leave central auditors with incomplete visibility.

The architecture assumes that Transit Gateway peering automatically propagates interregional routes. The stated evidence instead indicates: Disjoint local-account trails leave central auditors with incomplete visibility.

Resource policies were never checked for access beyond the organization's trust boundary. The stated evidence instead indicates: Disjoint local-account trails leave central auditors with incomplete visibility.

Every static asset fetch goes to a distant origin instead of the edge cache. The specific problem here is that the team assumes an x86 machine image and native binaries can run unchanged on arm64.

Region-specific public IPs and DNS routing do not provide the needed global anycast transport optimization. The specific problem here is that the team assumes an x86 machine image and native binaries can run unchanged on arm64.

A public bucket policy exposes origin objects outside the intended CloudFront access path. The specific problem here is that the team assumes an x86 machine image and native binaries can run unchanged on arm64.

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.

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: The security team manages GuardDuty separately in 50 accounts and misses newly created member accounts. It does not replace either required solution in A or B. Central GuardDuty administration supports ongoing multi-account detection enrollment; verify the two stated requirements independently rather than accepting an unrelated change.

Separate point-to-point VPC peering connections lack transitive routing and are difficult to govern at scale. The specific problem here is that a single Direct Connect circuit creates a site-to-cloud connectivity single point of failure.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The specific problem here is that a single Direct Connect circuit creates a site-to-cloud connectivity single point of failure.

There is no independently functioning VPN path when private connectivity goes down. The specific problem here is that a single Direct Connect circuit creates a site-to-cloud connectivity single point of failure.

Restoring a suitable past timestamp creates a usable table with correct records. However, this does not establish the required outcome: after a simulated endpoint failure, new DNS queries return the secondary healthy Region.

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: After a simulated endpoint failure, new DNS queries return the secondary healthy Region. The associated design principle is: DNS failover needs a health-signal and routing policy that actually switches answers.

Chargeback results trace shared spend to accounted requests or accountable service consumers. However, this does not establish the required outcome: after a simulated endpoint failure, new DNS queries return the secondary healthy Region.

Repeated uncached database work dominates response latency and compute expense. The stated evidence instead indicates: A non-Kubernetes orchestrator was chosen despite strict Kubernetes extension compatibility requirements.

Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads. The stated evidence instead indicates: A non-Kubernetes orchestrator was chosen despite strict Kubernetes extension compatibility requirements.

Always-on monolith capacity is required merely to handle infrequent independent endpoints. The stated evidence instead indicates: A non-Kubernetes orchestrator was chosen despite strict Kubernetes extension compatibility requirements.

This action targets a different technical need: Enterprise billing shows a stable EC2 spend baseline but Savings Plans are not aligned with actual account usage. It does not replace either required solution in A or B. Savings Plan decisions require evidence about coverage and utilization of eligible compute; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An ECS fleet is experiencing p99 delays but per-container CPU and memory usage are absent from operational dashboards. It does not replace either required solution in A or B. Container Insights provides enhanced telemetry for container infrastructure; 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.

An all-at-once replacement has unacceptable outage and rollback risk. The stated evidence instead indicates: A one-time export leaves days of writes uncopied before final deployment.

Local instance disks are wrongly used as a shared durable POSIX file system. The stated evidence instead indicates: A one-time export leaves days of writes uncopied before final deployment.

Workflow state and failure recovery are hidden in fragile custom imperative scripts. The stated evidence instead indicates: A one-time export leaves days of writes uncopied before final deployment.

This action targets a different technical need: Many workload VPCs need access to a privately published service without opening routing to the provider's whole VPC. It does not replace either required solution in A or B. AWS PrivateLink exposes a selected service to consumers without full network-to-network reachability; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Legal and nonproduction workloads require different organizational guardrails but must share central billing. It does not replace either required solution in A or B. Organizational units help assign governance boundaries to related member accounts; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Dozens of overprovisioned EC2 instances need evidence-based CPU and memory sizing recommendations before changing families. It does not replace either required solution in A or B. Compute Optimizer uses resource metrics and recommendations but must be checked against workload SLOs; verify the two stated requirements independently rather than accepting an unrelated change.