Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Engineers scale CPU without analyzing database lock waits or expensive SQL. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Unattached volumes are treated as free merely because they are not mounted. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Workload service calls repeatedly cross paid network boundaries without quantified need. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Read-only analytical traffic saturates the production database's single writable instance. The stated evidence instead indicates: Every read request traverses the backing DynamoDB service despite highly reusable cacheable data.

Stream shard limits or skewed partition keys cannot handle incoming record throughput. The stated evidence instead indicates: Every read request traverses the backing DynamoDB service despite highly reusable cacheable data.

Unbounded request bursts overload backends because no gateway rate protection is configured. The stated evidence instead indicates: Every read request traverses the backing DynamoDB service despite highly reusable cacheable data.

Homegrown scripts do not handle incremental transfer, scheduling and verification consistently. The stated evidence instead indicates: Partners are forced to replace SFTP clients with AWS SDK calls without business approval.

All consumers wait for a nightly export despite a near-real-time freshness requirement. The stated evidence instead indicates: Partners are forced to replace SFTP clients with AWS SDK calls without business approval.

The migration plan assumes a new AWS Snowball Edge device can still be ordered even though new-customer ordering is unavailable. The stated evidence instead indicates: Partners are forced to replace SFTP clients with AWS SDK calls without business approval.

Ordinary regional endpoints offer neither the requested global anycast entry point nor accelerator health steering. The stated evidence instead indicates: Static budgets cannot explain or detect each atypical spend pattern promptly.

Instances were resized from average CPU alone despite memory or traffic constraints. The stated evidence instead indicates: Static budgets cannot explain or detect each atypical spend pattern promptly.

On-demand usage was left wholly uncommitted despite predictable baseline compute consumption. The stated evidence instead indicates: Static budgets cannot explain or detect each atypical spend pattern promptly.

Burst replay avoids throttling while partition-level demand remains within supported constraints. However, this does not establish the required outcome: the dominant query wait events can be linked to the observed transaction latency.

Cold-start spikes fall for provisioned requests and concurrency utilization stays within budget. However, this does not establish the required outcome: the dominant query wait events can be linked to the observed transaction latency.

New instances become healthy before major traffic shift and rollback restores the previous code path. However, this does not establish the required outcome: the dominant query wait events can be linked to the observed transaction latency.

The architecture assumes that Transit Gateway peering automatically propagates interregional routes. The stated evidence instead indicates: Separate point-to-point VPC peering connections lack transitive routing and are difficult to govern at scale.

The team relies exclusively on retrospective end-of-month billing statements. The stated evidence instead indicates: Separate point-to-point VPC peering connections lack transitive routing and are difficult to govern at scale.

On-premises DNS has no forwarding path into the VPC's Route 53 Resolver. The stated evidence instead indicates: Separate point-to-point VPC peering connections lack transitive routing and are difficult to govern at scale.

Queries from on-premises resolvers return the expected private-zone records through inbound endpoint addresses. However, this does not establish the required outcome: clients retain accelerator anycast IPs and are directed to a healthy regional endpoint when one Region fails.

Participant-owned permitted resources deploy into the shared subnet while networking account retains network ownership. However, this does not establish the required outcome: clients retain accelerator anycast IPs and are directed to a healthy regional endpoint when one Region fails.

Both circuits carry permitted private routes, and a deliberate single-circuit outage retains connectivity. However, this does not establish the required outcome: clients retain accelerator anycast IPs and are directed to a healthy regional endpoint when one Region fails.

The service relies solely on application code with no rate-based edge filtering. The specific problem here is that iAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

Traffic bypasses inspection endpoints, so rules exist but are never reached. The specific problem here is that iAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

Records use ordinary simple routing without failover health awareness. The specific problem here is that iAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

A pilot demonstrates the chosen mainframe transformation path and acceptable business results. However, this does not establish the required outcome: destination rows converge with source changes and validated CDC lag allows the final switchover.

Invoice updates arrive at consumers within the required lag and replay does not duplicate side effects. However, this does not establish the required outcome: destination rows converge with source changes and validated CDC lag allows the final switchover.

Partners connect over SFTP and transferred objects appear in assigned bucket prefixes. However, this does not establish the required outcome: destination rows converge with source changes and validated CDC lag allows the final switchover.

This action targets a different technical need: A Kinesis stream has adequate shard write capacity but multiple consumers compete for read throughput and fall behind. It does not replace either required solution in A or B. Kinesis enhanced fan-out provides dedicated consumer read throughput within service limits; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A global network has rising cross-AZ and inter-Region transfer bills despite healthy compute utilization. It does not replace either required solution in A or B. Placement and traffic pattern matter to data transfer costs as much as raw compute prices; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Production maintenance requires an explicit approval and tracked change record before automation updates EC2 systems. It does not replace either required solution in A or B. Controlled automation separates approval from execution and preserves traceability; verify the two stated requirements independently rather than accepting an unrelated change.

Static IAM user access keys were embedded in the external CI configuration. The stated evidence instead indicates: The service relies solely on application code with no rate-based edge filtering.

The function's unqualified ARN always invokes latest code for all users, bypassing version routing. The stated evidence instead indicates: The service relies solely on application code with no rate-based edge filtering.

Traffic bypasses inspection endpoints, so rules exist but are never reached. The stated evidence instead indicates: The service relies solely on application code with no rate-based edge filtering.