Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

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.

Every static asset fetch goes to a distant origin instead of the edge cache. The specific problem here is that read-only analytical traffic saturates the production database's single writable instance.

Region-specific public IPs and DNS routing do not provide the needed global anycast transport optimization. The specific problem here is that read-only analytical traffic saturates the production database's single writable instance.

Fixed EC2 capacity is provisioned 24/7 despite infrequent invocation. The specific problem here is that read-only analytical traffic saturates the production database's single writable instance.

This action targets a different technical need: A reporting dashboard overloads a relational database primary with read queries but still requires strongly controlled write ownership. It does not replace either required solution in A or B. RDS read replicas scale read throughput but are asynchronous relative to the primary; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A Route 53 failover policy must move users between two independent public endpoints when the primary application fails. It does not replace either required solution in A or B. DNS health-based failover changes record responses, but clients may cache prior results; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A compliance dataset is rarely accessed after 90 days but must remain recoverable with several-hour retrieval tolerance. It does not replace either required solution in A or B. Lifecycle transitions reduce storage expense only if retrieval and minimum-duration constraints fit; verify the two stated requirements independently rather than accepting an unrelated change.

Untracked imperative orchestration repeats previous side effects after transient failures. The stated evidence instead indicates: Standard short-lived backups cannot recover the exact chosen accidental-update point.

Passive regional copies exist without health-driven endpoint selection. The stated evidence instead indicates: Standard short-lived backups cannot recover the exact chosen accidental-update point.

Kubernetes deployment treats process startup as adequate evidence of request readiness. The stated evidence instead indicates: Standard short-lived backups cannot recover the exact chosen accidental-update point.

An overly broad assumed-role session is not constrained to the vendor's assigned resources. The specific problem here is that resource policies were never checked for access beyond the organization's trust boundary.

Ordinary regional endpoints offer neither the requested global anycast entry point nor accelerator health steering. The specific problem here is that resource policies were never checked for access beyond the organization's trust boundary.

Disjoint local-account trails leave central auditors with incomplete visibility. The specific problem here is that resource policies were never checked for access beyond the organization's trust boundary.

Uncorrelated logs hide where the end-to-end latency accumulates. The specific problem here is that config findings are left as unactioned notifications while risky drift remains exposed.

Shared costs are assigned by arbitrary percentage without service consumption evidence. The specific problem here is that config findings are left as unactioned notifications while risky drift remains exposed.

Untracked imperative orchestration repeats previous side effects after transient failures. The specific problem here is that config findings are left as unactioned notifications while risky drift remains exposed.

Console changes have no reproducible declarative infrastructure state. The stated evidence instead indicates: Separate component logs cannot be correlated to customer transactions.

Workflow state and failure recovery are hidden in fragile custom imperative scripts. The stated evidence instead indicates: Separate component logs cannot be correlated to customer transactions.

Database engine migration was assumed to be a simple homogeneous replication job. The stated evidence instead indicates: Separate component logs cannot be correlated to customer transactions.

This action targets a different technical need: A Kinesis data stream has increasing write throttling because producers exceed the capacity of its current shard configuration. It does not replace either required solution in A or B. Kinesis stream performance depends on provisioned or on-demand capacity and balanced partition keys; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A busy event-routing platform must retain dropped partner events for later controlled replay after a bug fix. It does not replace either required solution in A or B. EventBridge event archives retain matching historical events for later replay; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A central security team needs automated detections for unusual cross-account API activity and suspected credential misuse. It does not replace either required solution in A or B. GuardDuty consumes AWS data sources to identify suspicious behavior and report findings; verify the two stated requirements independently rather than accepting an unrelated change.

The only purpose of a 24/7 server is occasional timer-based work. The stated evidence instead indicates: Shared data and internal method calls prevent independent deployment and scale.

A non-Kubernetes orchestrator was chosen despite strict Kubernetes extension compatibility requirements. The stated evidence instead indicates: Shared data and internal method calls prevent independent deployment and scale.

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

All consumers wait for a nightly export despite a near-real-time freshness requirement. The stated evidence instead indicates: Homegrown scripts do not handle incremental transfer, scheduling and verification consistently.

Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover. The stated evidence instead indicates: Homegrown scripts do not handle incremental transfer, scheduling and verification consistently.

Replicating table data alone does not translate incompatible source SQL constructs. The stated evidence instead indicates: Homegrown scripts do not handle incremental transfer, scheduling and verification consistently.

This action targets a different technical need: Service owners cannot separate API traffic incidents from infrastructure incidents across ten microservices. It does not replace either required solution in A or B. Meaningful dashboards align telemetry with system service boundaries and indicators; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Operations retains detached EBS volumes after instance termination and pays for unused storage for months. It does not replace either required solution in A or B. EBS storage billing continues for allocated volumes until they are deleted or otherwise changed; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An EKS service experiences 503 errors during rolling updates because pods accept traffic before dependencies initialize. It does not replace either required solution in A or B. Readiness and graceful termination controls reduce errors during normal rolling changes; verify the two stated requirements independently rather than accepting an unrelated change.