Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Read-only analytical traffic saturates the production database's single writable instance. The stated evidence instead indicates: The shared file system's throughput mode or credit availability constrains parallel clients.

Every component must be rebuilt from scratch after failure, despite a tighter RTO. The stated evidence instead indicates: The shared file system's throughput mode or credit availability constrains parallel clients.

Stream shard limits or skewed partition keys cannot handle incoming record throughput. The stated evidence instead indicates: The shared file system's throughput mode or credit availability constrains parallel clients.

Traffic bypasses inspection endpoints, so rules exist but are never reached. The specific problem here is that basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow.

IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy. The specific problem here is that basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow.

All containers share a single placement failure domain and cannot be rescheduled in time. The specific problem here is that basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow.

Ordinary regional endpoints offer neither the requested global anycast entry point nor accelerator health steering. The stated evidence instead indicates: Only source-region S3 versioning is enabled, but no replication rule or role exists.

All service replicas were scheduled in one zone despite multi-AZ infrastructure. The stated evidence instead indicates: Only source-region S3 versioning is enabled, but no replication rule or role exists.

Every backup copy resides in the same administration boundary as the threatened workloads. The stated evidence instead indicates: Only source-region S3 versioning is enabled, but no replication rule or role exists.

Stable compute baseline is paid at on-demand rates without analyzed commitments. The stated evidence instead indicates: The workload uses only on-demand capacity despite safe restart or checkpoint semantics.

Fixed EC2 capacity is provisioned 24/7 despite infrequent invocation. The stated evidence instead indicates: The workload uses only on-demand capacity despite safe restart or checkpoint semantics.

A public bucket policy exposes origin objects outside the intended CloudFront access path. The stated evidence instead indicates: The workload uses only on-demand capacity despite safe restart or checkpoint semantics.

Threat detection remains inconsistently deployed across member accounts and Regions. The specific problem here is that one overbroad bucket-level policy grants both teams access to all data.

Engineers measure host utilization but not the outcomes experienced by users. The specific problem here is that one overbroad bucket-level policy grants both teams access to all data.

Static security policy documents are not technically enforced against resource drift. The specific problem here is that one overbroad bucket-level policy grants both teams access to all data.

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.

All assets are scheduled for direct rehost even when some are obsolete or unsuitable. The stated evidence instead indicates: A one-time export leaves days of writes uncopied before final deployment.

Shared data and internal method calls prevent independent deployment and scale. The stated evidence instead indicates: A one-time export leaves days of writes uncopied before final deployment.

Chosen sizes meet memory and peak latency needs while reducing wasteful instance spending. However, this does not establish the required outcome: a retry resumes the failed state without independently rerunning successful steps and errors are visible in execution history.

An incident view identifies the affected service and response latency rather than just total fleet CPU. However, this does not establish the required outcome: a retry resumes the failed state without independently rerunning successful steps and errors are visible in execution history.

Release decisions reference tracked error rate and latency burn rather than raw instance uptime alone. However, this does not establish the required outcome: a retry resumes the failed state without independently rerunning successful steps and errors are visible in execution history.

Untracked imperative orchestration repeats previous side effects after transient failures. The specific problem here is that teams confuse key material rotation with replacing the KMS key ID and losing access to old data.

Static security policy documents are not technically enforced against resource drift. The specific problem here is that teams confuse key material rotation with replacing the KMS key ID and losing access to old data.

CloudTrail management events are not retained or centrally available for review. The specific problem here is that teams confuse key material rotation with replacing the KMS key ID and losing access to old data.

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.

This action targets a different technical need: A worldwide public application targets near-zero regional failover time and already tolerates multi-Region data conflict semantics. It does not replace either required solution in A or B. Active-active architectures provide immediate regional capacity but require safe multi-Region data behavior; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An operations team must roll out the same hardened EC2 AMI to many accounts with recorded patch and test history. It does not replace either required solution in A or B. EC2 Image Builder automates reproducible image lifecycles with testing and distribution; verify the two stated requirements independently rather than accepting an unrelated change.

Eligible accounts create scheduled recovery points according to policies and restores are tested. However, this does not establish the required outcome: traffic uses translated unique endpoint addresses and return packets reach the original client correctly.

Both circuits carry permitted private routes, and a deliberate single-circuit outage retains connectivity. However, this does not establish the required outcome: traffic uses translated unique endpoint addresses and return packets reach the original client correctly.

Traffic crosses the regional peering attachment only for specifically installed and approved prefixes. However, this does not establish the required outcome: traffic uses translated unique endpoint addresses and return packets reach the original client correctly.

Every reporting query was sent to the cluster writer endpoint despite available readers. The specific problem here is that repeated retries of one failed message prevent useful error isolation and redrive workflow.

The CDN forwards every request to origin due to ineffective cache keys or caching headers. The specific problem here is that repeated retries of one failed message prevent useful error isolation and redrive workflow.

DNS simple routing cannot automatically reflect the application's health. The specific problem here is that repeated retries of one failed message prevent useful error isolation and redrive workflow.