Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

The remote principal has S3 object access but lacks required key-policy and IAM decrypt permission. The stated evidence instead indicates: Individual IAM users were being created per account instead of using centralized workforce federation.

Public ACM-issued certificates were wrongly assumed to provide a corporate private CA chain. The stated evidence instead indicates: Individual IAM users were being created per account instead of using centralized workforce federation.

Backup images exist but no continuously replicated recovery environment or launch plan is configured. The stated evidence instead indicates: Individual IAM users were being created per account instead of using centralized workforce federation.

Mainframe batch and transaction semantics were treated as if they were ordinary Linux workloads. The stated evidence instead indicates: Migration estimates are based solely on outdated procurement records rather than measured workload behavior.

Migration scheduling ignored data classification and jurisdictional control requirements. The stated evidence instead indicates: Migration estimates are based solely on outdated procurement records rather than measured workload behavior.

Licensing constraints were omitted until after destination EC2 instances were chosen. The stated evidence instead indicates: Migration estimates are based solely on outdated procurement records rather than measured workload behavior.

Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover. The stated evidence instead indicates: Local instance disks are wrongly used as a shared durable POSIX file system.

Always-on monolith capacity is required merely to handle infrequent independent endpoints. The stated evidence instead indicates: Local instance disks are wrongly used as a shared durable POSIX file system.

All analytics jobs depend on a single custom ETL server and its directly attached storage. The stated evidence instead indicates: Local instance disks are wrongly used as a shared durable POSIX file system.

Hot session lookups avoid repeated database queries and failure recovery preserves acceptable service behavior. However, this does not establish the required outcome: cache hit ratio increases and p95 download latency improves across distant test locations.

P95 latency and unit costs improve in a representative arm64 canary with all native libraries working. However, this does not establish the required outcome: cache hit ratio increases and p95 download latency improves across distant test locations.

A rotation completes, the application authenticates with the new value, and old credentials are not exposed. However, this does not establish the required outcome: cache hit ratio increases and p95 download latency improves across distant test locations.

Security Hub centrally displays eligible standardized findings with source context preserved. However, this does not establish the required outcome: new cryptographic material is used when rotation occurs while previously encrypted data remains decryptable.

The stack tolerates the injected zonal fault and stop alarms terminate experiments as planned. However, this does not establish the required outcome: new cryptographic material is used when rotation occurs while previously encrypted data remains decryptable.

Existing and new participating accounts report eligible findings to the delegated administrator. However, this does not establish the required outcome: new cryptographic material is used when rotation occurs while previously encrypted data remains decryptable.

Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable. The specific problem here is that the backup Region exists but DNS routing never changes after primary endpoint failure.

Each business unit manually maintains duplicative IAM users in workload accounts. The specific problem here is that the backup Region exists but DNS routing never changes after primary endpoint failure.

No archive or retention mechanism was configured before the subscriber outage. The specific problem here is that the backup Region exists but DNS routing never changes after primary endpoint failure.

Shared costs are assigned by arbitrary percentage without service consumption evidence. The specific problem here is that potential savings from the same infrastructure change are double counted in separate reports.

Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance. The specific problem here is that potential savings from the same infrastructure change are double counted in separate reports.

Metrics and logs are not organized into actionable per-service operational signals. The specific problem here is that potential savings from the same infrastructure change are double counted in separate reports.

Unbounded request bursts overload backends because no gateway rate protection is configured. The stated evidence instead indicates: Objects remain indefinitely in higher-cost storage despite a proven low-access retention pattern.

S3 calls egress through NAT because no supported endpoint route was configured. The stated evidence instead indicates: Objects remain indefinitely in higher-cost storage despite a proven low-access retention pattern.

Storage capacity was fixed without safe growth management under variable data requirements. The stated evidence instead indicates: Objects remain indefinitely in higher-cost storage despite a proven low-access retention pattern.

Engineers scale CPU without analyzing database lock waits or expensive SQL. The stated evidence instead indicates: Capacity planning ignores demand spikes or hot keys that concentrate requests.

One overbroad bucket-level policy grants both teams access to all data. The stated evidence instead indicates: Capacity planning ignores demand spikes or hot keys that concentrate requests.

Gp2 capacity-linked performance assumptions lead to wasteful storage growth. The stated evidence instead indicates: Capacity planning ignores demand spikes or hot keys that concentrate requests.

The shared file system's throughput mode or credit availability constrains parallel clients. The specific problem here is that stream shard limits or skewed partition keys cannot handle incoming record throughput.

Storage capacity was fixed without safe growth management under variable data requirements. The specific problem here is that stream shard limits or skewed partition keys cannot handle incoming record throughput.

Instance-local caches cannot share consistent ephemeral state across horizontally scaled hosts. The specific problem here is that stream shard limits or skewed partition keys cannot handle incoming record throughput.

Instances were resized from average CPU alone despite memory or traffic constraints. The specific problem here is that static budgets cannot explain or detect each atypical spend pattern promptly.

Each application team is provisioning its own disconnected backbone gateway. The specific problem here is that static budgets cannot explain or detect each atypical spend pattern promptly.

Resource tags were never activated as billing cost allocation dimensions. The specific problem here is that static budgets cannot explain or detect each atypical spend pattern promptly.