Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Revoking a staff member's assignment removes their delegated access without per-account user deletion. However, this does not establish the required outcome: finance can reconcile detailed usage line items to accounts and cost categories.

Tested resized instances meet p95 latency goals while recommended savings are observed. However, this does not establish the required outcome: finance can reconcile detailed usage line items to accounts and cost categories.

Eligible compute charges reflect the planned commitment discount and remaining coverage is visible. However, this does not establish the required outcome: finance can reconcile detailed usage line items to accounts and cost categories.

Individual Security Hub instances were not centrally delegated or aggregated. The stated evidence instead indicates: Per-account one-off inspections do not continuously evaluate drift across accounts.

A single-Region DynamoDB table cannot accept the required local writes after that Region fails. The stated evidence instead indicates: Per-account one-off inspections do not continuously evaluate drift across accounts.

Individual IAM users were being created per account instead of using centralized workforce federation. The stated evidence instead indicates: Per-account one-off inspections do not continuously evaluate drift across accounts.

A seeded supported suspicious event generates a finding and the delegated administrator can triage it. However, this does not establish the required outcome: cloud instances access approved services privately while disallowed API paths are rejected.

Failure of one Region does not interrupt healthy remaining regional capacity under synthetic load. However, this does not establish the required outcome: cloud instances access approved services privately while disallowed API paths are rejected.

CloudFront retrieves approved objects while direct anonymous S3 URLs are rejected. However, this does not establish the required outcome: cloud instances access approved services privately while disallowed API paths are rejected.

Findings remain siloed in local account consoles and cannot be triaged centrally. The stated evidence instead indicates: CloudTrail management events are not retained or centrally available for review.

Resource-based trust was not evaluated beyond local IAM identity permission reports. The stated evidence instead indicates: CloudTrail management events are not retained or centrally available for review.

Standard short-lived backups cannot recover the exact chosen accidental-update point. The stated evidence instead indicates: CloudTrail management events are not retained or centrally available for review.

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.

This action targets a different technical need: An engineer repeatedly leaves management ports publicly accessible despite a configuration guardrail document. It does not replace either required solution in A or B. AWS Config checks configuration changes against evaluable rules and supports managed remediation actions; 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.

A fresh environment can be recreated from code with predictable parameters and drift checks. However, this does not establish the required outcome: inventory changes can deploy without forcing unrelated checkout and customer workflows through full regression.

Vendor-certified testing proves that the appliance runs on the selected target or requires retain/replace decision. However, this does not establish the required outcome: inventory changes can deploy without forcing unrelated checkout and customer workflows through full regression.

Source and destination data reconcile, CDC lag reaches the target and switching endpoints remains reversible. However, this does not establish the required outcome: inventory changes can deploy without forcing unrelated checkout and customer workflows through full regression.

No archive or retention mechanism was configured before the subscriber outage. The specific problem here is that all service replicas were scheduled in one zone despite multi-AZ infrastructure.

Resource policies were never checked for access beyond the organization's trust boundary. The specific problem here is that all service replicas were scheduled in one zone despite multi-AZ infrastructure.

Backup images exist but no continuously replicated recovery environment or launch plan is configured. The specific problem here is that all service replicas were scheduled in one zone despite multi-AZ infrastructure.

Excess requests return expected throttling responses while permitted traffic continues under peak simulation. However, this does not establish the required outcome: events captured during the fault can be replayed to a corrected consumer after recovery.

A poison message goes to the DLQ after configured attempts while valid following messages proceed. However, this does not establish the required outcome: events captured during the fault can be replayed to a corrected consumer after recovery.

The load balancer continues serving from healthy remaining tasks during a forced zone failure. However, this does not establish the required outcome: events captured during the fault can be replayed to a corrected consumer after recovery.

Separate VPC copies and peering links were created instead of sharing centrally governed subnets. The stated evidence instead indicates: Overlapping network prefixes make ordinary VPC peering route selection ambiguous.

The architecture assumes that Transit Gateway peering automatically propagates interregional routes. The stated evidence instead indicates: Overlapping network prefixes make ordinary VPC peering route selection ambiguous.

The inspection design allows forward and return packets to use different stateful inspection appliances. The stated evidence instead indicates: Overlapping network prefixes make ordinary VPC peering route selection ambiguous.

All assets are scheduled for direct rehost even when some are obsolete or unsuitable. The stated evidence instead indicates: Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads.

Developers assume SQS has identical JMS or broker feature semantics to the source stack. The stated evidence instead indicates: Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads.

All analytics jobs depend on a single custom ETL server and its directly attached storage. The stated evidence instead indicates: Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads.

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.