Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Every static asset fetch goes to a distant origin instead of the edge cache. The stated evidence instead indicates: Every reporting query was sent to the cluster writer endpoint despite available readers.

No event archive exists to replay notifications that failed during downstream processing. The stated evidence instead indicates: 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 stated evidence instead indicates: Every reporting query was sent to the cluster writer endpoint despite available readers.

This action targets a different technical need: Critical backups must be scheduled consistently across many application accounts and retained by policy. It does not replace either required solution in A or B. Organization backup policies support common baseline definitions but still require functioning target configuration; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Two acquired subsidiaries have overlapping RFC1918 VPC CIDRs but must exchange traffic with a shared integration endpoint. It does not replace either required solution in A or B. Overlapping address spaces require translation or service-level isolation rather than simple routed peering; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Variable monthly expenses must trigger alerts for unusual spending spikes without predefined per-service thresholds. It does not replace either required solution in A or B. Cost Anomaly Detection learns spending patterns and flags unusual expenditures; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Customer-uploaded S3 objects must appear in a second Region for durability and region-isolation objectives. It does not replace either required solution in A or B. Cross-Region Replication asynchronously copies eligible objects between configured buckets; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Several accounts have steady EC2 and Fargate spend and need a commitment that applies to qualifying compute usage flexibly. It does not replace either required solution in A or B. Compute Savings Plans apply eligible usage discounts across supported services and configurations; 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.

Ordinary regional endpoints offer neither the requested global anycast entry point nor accelerator health steering. The specific problem here is that overlapping network prefixes make ordinary VPC peering route selection ambiguous.

Per-account one-off inspections do not continuously evaluate drift across accounts. The specific problem here is that overlapping network prefixes make ordinary VPC peering route selection ambiguous.

The architecture assumes that Transit Gateway peering automatically propagates interregional routes. The specific problem here is that overlapping network prefixes make ordinary VPC peering route selection ambiguous.

Resource tags were never activated as billing cost allocation dimensions. The specific problem here is that the team relies exclusively on retrospective end-of-month billing statements.

Overlapping network prefixes make ordinary VPC peering route selection ambiguous. The specific problem here is that the team relies exclusively on retrospective end-of-month billing statements.

On-demand usage was left wholly uncommitted despite predictable baseline compute consumption. The specific problem here is that the team relies exclusively on retrospective end-of-month billing statements.

Local Config assessments exist but no aggregation exposes cross-account status. The specific problem here is that events remain confined to local account buses because cross-account bus authorization is absent.

A broad VPC peering link was used where a service-scoped private access path was needed. The specific problem here is that events remain confined to local account buses because cross-account bus authorization is absent.

Each application team is provisioning its own disconnected backbone gateway. The specific problem here is that events remain confined to local account buses because cross-account bus authorization is absent.

This action targets a different technical need: A global static web application experiences high latency because users repeatedly fetch unchanged assets from one Region. It does not replace either required solution in A or B. CloudFront edge caching reduces origin fetches for cacheable content; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A transactional RDS workload must automatically fail over within the Region on an AZ failure. It does not replace either required solution in A or B. RDS Multi-AZ provides standby capacity for automated intra-Region failover, not read scaling by itself; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An AWS KMS-encrypted data key is shared with a role but decrypts still fail because the key's resource policy grants no access. It does not replace either required solution in A or B. KMS key authorization depends on the owning key policy as well as applicable principal policies; verify the two stated requirements independently rather than accepting an unrelated change.

That evidence is associated with a separate architecture requirement: A company wants to identify IAM permissions that have not been used recently before removing high-risk privileges. It does not prove that this case was remediated. The relevant observation must be: Database failover restarts service within the tested objective after a zone loss. The associated design principle is: RDS Multi-AZ maintains standby capacity for high availability and managed failover.

That evidence is associated with a separate architecture requirement: A DynamoDB application requires recovery from accidental writes to an earlier point within a month. It does not prove that this case was remediated. The relevant observation must be: Database failover restarts service within the tested objective after a zone loss. The associated design principle is: RDS Multi-AZ maintains standby capacity for high availability and managed failover.

That evidence is associated with a separate architecture requirement: An Application Load Balancer intermittently forwards traffic to unhealthy containers after their readiness endpoint fails. It does not prove that this case was remediated. The relevant observation must be: Database failover restarts service within the tested objective after a zone loss. The associated design principle is: RDS Multi-AZ maintains standby capacity for high availability and managed failover.

This action targets a different technical need: A company has shared Reserved Instances in its payer organization and wants to quantify benefit distribution across linked accounts. It does not replace either required solution in A or B. Consolidated billing can share eligible reservations across member accounts subject to sharing settings; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A headquarters requires a resilient private link to workloads in two Regions and must avoid routing all traffic over the public internet. It does not replace either required solution in A or B. Independent Direct Connect circuits and correctly associated gateways improve hybrid-path resiliency; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A global web application must fail over to a secondary Region if the primary public endpoint becomes unhealthy. It does not replace either required solution in A or B. Route 53 health-check failover can redirect future DNS resolutions between operational regional endpoints; verify the two stated requirements independently rather than accepting an unrelated change.

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: requests switch to the replacement environment only after health tests pass, and rollback returns traffic to old targets.

Read latency and writer CPU improve under reporting load without routing writes to read replicas. However, this does not establish the required outcome: requests switch to the replacement environment only after health tests pass, and rollback returns traffic to old targets.

Failed security or smoke tests prevent production deployment while passing builds can be promoted. However, this does not establish the required outcome: requests switch to the replacement environment only after health tests pass, and rollback returns traffic to old targets.

Developers assume SQS has identical JMS or broker feature semantics to the source stack. The stated evidence instead indicates: Tight synchronous coupling propagates a noncritical downstream failure to the primary transaction.

Workflow state and failure recovery are hidden in fragile custom imperative scripts. The stated evidence instead indicates: Tight synchronous coupling propagates a noncritical downstream failure to the primary transaction.

Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads. The stated evidence instead indicates: Tight synchronous coupling propagates a noncritical downstream failure to the primary transaction.