Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: A shared EFS file system slows a data-processing batch even though compute workers are mostly idle. It does not replace either required solution in A or B. EFS throughput characteristics must match concurrent IO patterns and required sustained rate; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A high-traffic EC2 service must release a risky version while keeping a rapid rollback path and without terminating all healthy targets at once. It does not replace either required solution in A or B. Blue-green deployment separates old and new environments to support safe traffic shifting; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Large fault-tolerant batch analytics jobs can be interrupted and resumed while the team pays full on-demand prices. It does not replace either required solution in A or B. Spot Instances optimize interruptible capacity costs when jobs tolerate reclaim events; verify the two stated requirements independently rather than accepting an unrelated change.

Revoking a staff member's assignment removes their delegated access without per-account user deletion. However, this does not establish the required outcome: consumer instances reach only the approved PrivateLink service while unrelated provider subnets remain unreachable.

Traffic uses translated unique endpoint addresses and return packets reach the original client correctly. However, this does not establish the required outcome: consumer instances reach only the approved PrivateLink service while unrelated provider subnets remain unreachable.

A simulated Direct Connect failure moves approved routes to VPN tunnels and restore reverses route preference. However, this does not establish the required outcome: consumer instances reach only the approved PrivateLink service while unrelated provider subnets remain unreachable.

This action targets a different technical need: Several accounts have steady EC2 and Fargate spend and need a commitment that applies to qualifying compute usage flexibly. It does not replace either required solution in A or B. Compute Savings Plans apply eligible usage discounts across supported services and configurations; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Many workload VPCs need access to a privately published service without opening routing to the provider's whole VPC. It does not replace either required solution in A or B. AWS PrivateLink exposes a selected service to consumers without full network-to-network reachability; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A startup expects to grow from five accounts to 100 and needs baseline account vending and preventive guardrails. It does not replace either required solution in A or B. AWS Control Tower provides managed landing-zone governance and standardized account provisioning; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Regulators require consistent detection and correction of publicly accessible S3 buckets across a multi-account organization. It does not replace either required solution in A or B. Organization-level Config rules continuously evaluate configuration and can launch controlled remediations; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Order processing must survive transient database outages without permanently losing accepted incoming work. It does not replace either required solution in A or B. Durable queues decouple intake availability from downstream processing failures; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A large S3 estate has unknown replication, storage-class, and lifecycle patterns that drive storage expense. It does not replace either required solution in A or B. S3 Storage Lens supports visibility into storage activity and efficiency metrics; verify the two stated requirements independently rather than accepting an unrelated change.

Resource tags were never activated as billing cost allocation dimensions. The specific problem here is that previous-month charges were presented as accurate forecasts for an expanded future footprint.

Instances were resized from average CPU alone despite memory or traffic constraints. The specific problem here is that previous-month charges were presented as accurate forecasts for an expanded future footprint.

A broad VPC peering link was used where a service-scoped private access path was needed. The specific problem here is that previous-month charges were presented as accurate forecasts for an expanded future footprint.

Public ACM-issued certificates were wrongly assumed to provide a corporate private CA chain. The specific problem here is that an overly broad assumed-role session is not constrained to the vendor's assigned resources.

Disjoint local-account trails leave central auditors with incomplete visibility. The specific problem here is that an overly broad assumed-role session is not constrained to the vendor's assigned resources.

Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable. The specific problem here is that an overly broad assumed-role session is not constrained to the vendor's assigned resources.

No event archive exists to replay notifications that failed during downstream processing. The stated evidence instead indicates: Instance capacity is pinned to one zone with no automated target recovery.

Individual account stacks were created manually and drift from the approved baseline. The stated evidence instead indicates: Instance capacity is pinned to one zone with no automated target recovery.

Unbounded request bursts overload backends because no gateway rate protection is configured. The stated evidence instead indicates: Instance capacity is pinned to one zone with no automated target recovery.

Traffic was switched to the container environment before dependent services and probes were verified. The stated evidence instead indicates: Replicating table data alone does not translate incompatible source SQL constructs.

Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover. The stated evidence instead indicates: Replicating table data alone does not translate incompatible source SQL constructs.

Source virtualization format was mistaken for a guarantee of target runtime compatibility. The stated evidence instead indicates: Replicating table data alone does not translate incompatible source SQL constructs.

Source virtualization format was mistaken for a guarantee of target runtime compatibility. The stated evidence instead indicates: An all-at-once replacement has unacceptable outage and rollback risk.

All consumers wait for a nightly export despite a near-real-time freshness requirement. The stated evidence instead indicates: An all-at-once replacement has unacceptable outage and rollback risk.

Separate component logs cannot be correlated to customer transactions. The stated evidence instead indicates: An all-at-once replacement has unacceptable outage and rollback risk.

Failed security or smoke tests prevent production deployment while passing builds can be promoted. However, this does not establish the required outcome: identical input configurations yield reviewed deployment changes and detectable drift rather than ad hoc resources.

Cache hit ratio increases and p95 download latency improves across distant test locations. However, this does not establish the required outcome: identical input configurations yield reviewed deployment changes and detectable drift rather than ad hoc resources.

Requests switch to the replacement environment only after health tests pass, and rollback returns traffic to old targets. However, this does not establish the required outcome: identical input configurations yield reviewed deployment changes and detectable drift rather than ad hoc resources.

Resource tags were never activated as billing cost allocation dimensions. The stated evidence instead indicates: Disjoint local-account trails leave central auditors with incomplete visibility.

The remote principal has S3 object access but lacks required key-policy and IAM decrypt permission. The stated evidence instead indicates: Disjoint local-account trails leave central auditors with incomplete visibility.

Individual Security Hub instances were not centrally delegated or aggregated. The stated evidence instead indicates: Disjoint local-account trails leave central auditors with incomplete visibility.