Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: An organization needs central inspection of east-west traffic from multiple spoke VPCs without asymmetric return flows. It does not replace either required solution in A or B. Stateful network inspection requires symmetric paths through the selected inspection appliance; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A central networking account must share an existing Transit Gateway with application accounts without duplicating it. It does not replace either required solution in A or B. AWS RAM can share supported resources while ownership remains in a central account; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Dozens of overprovisioned EC2 instances need evidence-based CPU and memory sizing recommendations before changing families. It does not replace either required solution in A or B. Compute Optimizer uses resource metrics and recommendations but must be checked against workload SLOs; verify the two stated requirements independently rather than accepting an unrelated change.

A one-time export leaves days of writes uncopied before final deployment. The specific problem here is that all consumers wait for a nightly export despite a near-real-time freshness requirement.

Licensing constraints were omitted until after destination EC2 instances were chosen. The specific problem here is that all consumers wait for a nightly export despite a near-real-time freshness requirement.

Shared data and internal method calls prevent independent deployment and scale. The specific problem here is that all consumers wait for a nightly export despite a near-real-time freshness requirement.

Every backup copy resides in the same administration boundary as the threatened workloads. The stated evidence instead indicates: All service replicas were scheduled in one zone despite multi-AZ infrastructure.

Static budgets cannot explain or detect each atypical spend pattern promptly. The stated evidence instead indicates: All service replicas were scheduled in one zone despite multi-AZ infrastructure.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The stated evidence instead indicates: All service replicas were scheduled in one zone despite multi-AZ infrastructure.

Findings remain siloed in local account consoles and cannot be triaged centrally. The specific problem here is that metrics and logs are not organized into actionable per-service operational signals.

Config findings are left as unactioned notifications while risky drift remains exposed. The specific problem here is that metrics and logs are not organized into actionable per-service operational signals.

Uncorrelated logs hide where the end-to-end latency accumulates. The specific problem here is that metrics and logs are not organized into actionable per-service operational signals.

Destination rows converge with source changes and validated CDC lag allows the final switchover. However, this does not establish the required outcome: new EKS pods pass readiness and regression tests before a controlled traffic cutover.

Separate analysts query approved lake datasets without direct access to the legacy ETL host. However, this does not establish the required outcome: new EKS pods pass readiness and regression tests before a controlled traffic cutover.

Eligible file changes are transferred and verified by a scheduled DataSync task. However, this does not establish the required outcome: new EKS pods pass readiness and regression tests before a controlled traffic cutover.

Basic infrastructure availability controls were mistaken for managed advanced DDoS response workflow. The stated evidence instead indicates: Service API traffic depends on public egress or an unintended NAT route despite a private-access requirement.

Static IAM user access keys were embedded in the external CI configuration. The stated evidence instead indicates: Service API traffic depends on public egress or an unintended NAT route despite a private-access requirement.

The destination bucket is present but replication cannot use the destination KMS key. The stated evidence instead indicates: Service API traffic depends on public egress or an unintended NAT route despite a private-access requirement.

The delegated administrator can manage enrolled member security coverage within its supported scope. However, this does not establish the required outcome: eligible accounts create scheduled recovery points according to policies and restores are tested.

Central compliance dashboards include resource findings from configured participating accounts and Regions. However, this does not establish the required outcome: eligible accounts create scheduled recovery points according to policies and restores are tested.

Newly created and eligible changed objects arrive in the destination bucket with expected encryption. However, this does not establish the required outcome: eligible accounts create scheduled recovery points according to policies and restores are tested.

Local instance disks are wrongly used as a shared durable POSIX file system. The stated evidence instead indicates: Application reliability still depends on one unmanaged database host and manual restores.

Shared data and internal method calls prevent independent deployment and scale. The stated evidence instead indicates: Application reliability still depends on one unmanaged database host and manual restores.

Tight synchronous coupling propagates a noncritical downstream failure to the primary transaction. The stated evidence instead indicates: Application reliability still depends on one unmanaged database host and manual restores.

This action targets a different technical need: Cloud infrastructure is built manually for each test environment and nobody knows which resources can be reproduced. It does not replace either required solution in A or B. Infrastructure as code supports repeatability, reviews and automated lifecycle controls; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A company must perform recurring secure file synchronization from on-premises NAS into Amazon S3 with minimal custom scripting. It does not replace either required solution in A or B. AWS DataSync automates supported file and object movement with verification features; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A corporation has hundreds of interdependent on-premises services and cannot establish which databases must move together. It does not replace either required solution in A or B. Dependency mapping reduces migration risk by revealing the actual application interaction graph; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A legacy reporting ETL cluster requires durable raw data sharing and easier scale-out queries across departments. It does not replace either required solution in A or B. A shared governed object-storage lake decouples data retention from individual processing engines; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Cloud infrastructure is built manually for each test environment and nobody knows which resources can be reproduced. It does not replace either required solution in A or B. Infrastructure as code supports repeatability, reviews and automated lifecycle controls; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A global enterprise wants a portfolio-level view of application migrations, owners, blockers and cutover states. It does not replace either required solution in A or B. A centralized migration tracking layer supports coordination across application teams; 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 product catalog on DynamoDB receives many repeated eventually consistent key lookups and requires microsecond cache responses. It does not replace either required solution in A or B. DAX offers managed in-memory caching for eligible DynamoDB read workloads; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A queue-backed worker fleet is underloaded overnight but still runs a fixed large number of instances. It does not replace either required solution in A or B. Queue-driven scaling aligns paid worker capacity with outstanding workload; verify the two stated requirements independently rather than accepting an unrelated change.