Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

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: A transactional RDS instance becomes slow under concurrency and the team needs to distinguish SQL waits from CPU pressure. It does not replace either required solution in A or B. Database performance diagnostics should identify the specific bottleneck before scaling; 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.

Cloud instances access approved services privately while disallowed API paths are rejected. However, this does not establish the required outcome: the abusive source crosses its request threshold and is blocked without blocking allowed sample traffic.

The authorized role decrypts the designated ciphertext while an unrelated role remains denied. However, this does not establish the required outcome: the abusive source crosses its request threshold and is blocked without blocking allowed sample traffic.

Excess requests return expected throttling responses while permitted traffic continues under peak simulation. However, this does not establish the required outcome: the abusive source crosses its request threshold and is blocked without blocking allowed sample traffic.

This action targets a different technical need: A product catalog on DynamoDB receives many repeated eventually consistent key lookups and requires microsecond cache responses. It does not replace either required solution in A or B. DAX offers managed in-memory caching for eligible DynamoDB read workloads; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A queue-backed worker fleet is underloaded overnight but still runs a fixed large number of instances. It does not replace either required solution in A or B. Queue-driven scaling aligns paid worker capacity with outstanding workload; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A high-traffic EC2 service must release a risky version while keeping a rapid rollback path and without terminating all healthy targets at once. It does not replace either required solution in A or B. Blue-green deployment separates old and new environments to support safe traffic shifting; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A service needs to replay historical event notifications after a downstream subscriber defect is corrected. It does not replace either required solution in A or B. EventBridge archives support bounded replay of previously captured events; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A central audit account needs immutable delivery of logs from all workload accounts and Regions. It does not replace either required solution in A or B. An organization trail and protected storage form a centralized account-wide auditing design; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Security analysts need one cross-account aggregation view of prioritized findings without requesting console access in every workload account. It does not replace either required solution in A or B. Security Hub delegated administration centralizes findings while each source account retains its own resources; verify the two stated requirements independently rather than accepting an unrelated change.

The CDN forwards every request to origin due to ineffective cache keys or caching headers. The stated evidence instead indicates: Basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow.

Service API traffic depends on public egress or an unintended NAT route despite a private-access requirement. The stated evidence instead indicates: Basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow.

A static password in deployment parameters cannot be centrally rotated safely. The stated evidence instead indicates: Basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow.

Each registered consumer receives an independent read-throughput path and lag falls during peak events. However, this does not establish the required outcome: origin request count drops under a multi-edge cache miss test while freshness remains correct.

Security Hub centrally displays eligible standardized findings with source context preserved. However, this does not establish the required outcome: origin request count drops under a multi-edge cache miss test while freshness remains correct.

The dominant query wait events can be linked to the observed transaction latency. However, this does not establish the required outcome: origin request count drops under a multi-edge cache miss test while freshness remains correct.

On-premises DNS has no forwarding path into the VPC's Route 53 Resolver. The stated evidence instead indicates: Management-account-only operations were mistaken for necessary daily centralized security administration.

Individual accounts use drifting custom schedules that do not match central backup policy. The stated evidence instead indicates: Management-account-only operations were mistaken for necessary daily centralized security administration.

Each business unit manually maintains duplicative IAM users in workload accounts. The stated evidence instead indicates: Management-account-only operations were mistaken for necessary daily centralized security administration.

This action targets a different technical need: A legacy reporting ETL cluster requires durable raw data sharing and easier scale-out queries across departments. It does not replace either required solution in A or B. A shared governed object-storage lake decouples data retention from individual processing engines; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An AWS Enterprise Support research customer needs to migrate tens of terabytes from a remote site with unreliable network links and can bring storage to a nearby AWS transfer facility. It does not replace either required solution in A or B. AWS Data Transfer Terminal allows eligible Enterprise Support customers to bring storage to an AWS transfer site; AWS Snowball Edge is no longer available to new customers; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A legacy billing system runs nightly ETL and downstream consumers need near-real-time invoice changes. It does not replace either required solution in A or B. CDC-based event distribution can modernize delayed batch data propagation; verify the two stated requirements independently rather than accepting an unrelated change.

Records use ordinary simple routing without failover health awareness. The stated evidence instead indicates: Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO.

No event archive exists to replay notifications that failed during downstream processing. The stated evidence instead indicates: Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO.

The destination bucket is present but replication cannot use the destination KMS key. The stated evidence instead indicates: Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO.

Misses from different edge caches repeatedly burden the same origin. The stated evidence instead indicates: Engineers scale CPU without analyzing database lock waits or expensive SQL.

On-demand initialization latency is not addressed for the critical invocation path. The stated evidence instead indicates: Engineers scale CPU without analyzing database lock waits or expensive SQL.

Untracked imperative orchestration repeats previous side effects after transient failures. The stated evidence instead indicates: Engineers scale CPU without analyzing database lock waits or expensive SQL.

This action targets a different technical need: A product releases the same service to two Regions and must require a compliance approval before the second Region goes live. It does not replace either required solution in A or B. Multi-Region pipelines can enforce explicit promotion and approval boundaries; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Unpredictably accessed objects are retained for a year, but no reliable access-frequency segmentation is known. It does not replace either required solution in A or B. S3 Intelligent-Tiering can move eligible objects among access tiers based on access frequency; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A public API has repeated abusive requests from a single source network but normal distributed traffic should continue. It does not replace either required solution in A or B. WAF rate-based rules can limit excessive HTTP request patterns by aggregation key; verify the two stated requirements independently rather than accepting an unrelated change.