Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: A platform team requires Kubernetes APIs, admission policies and custom controllers while moving a container platform to AWS. It does not replace either required solution in A or B. EKS provides a managed Kubernetes control plane for teams using Kubernetes-native tooling; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A SQL Server estate must migrate to Amazon Aurora PostgreSQL despite vendor-specific T-SQL constructs. It does not replace either required solution in A or B. Heterogeneous database migrations require explicit schema and application compatibility work; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An ecommerce backend repeatedly recomputes expensive reads for product listings that change infrequently. It does not replace either required solution in A or B. Correct cache placement and invalidation reduce repeated work without violating freshness needs; verify the two stated requirements independently rather than accepting an unrelated change.

An approved target design demonstrates residency and encryption enforcement before copying production records. However, this does not establish the required outcome: each workload has justified retire, retain, relocate, rehost, replatform, repurchase or refactor decision.

A tested transfer plan shows enough effective throughput plus integrity checks for the deadline. However, this does not establish the required outcome: each workload has justified retire, retain, relocate, rehost, replatform, repurchase or refactor decision.

A forced downstream failure follows tested compensation logic without duplicating completed orders. However, this does not establish the required outcome: each workload has justified retire, retain, relocate, rehost, replatform, repurchase or refactor decision.

Cloud instances access approved services privately while disallowed API paths are rejected. However, this does not establish the required outcome: a primary health-check failure leads subsequent name resolutions toward the healthy backup Region.

Read replica lag is measured and promotion produces a usable independent writer during a DR drill. However, this does not establish the required outcome: a primary health-check failure leads subsequent name resolutions toward the healthy backup Region.

A restore drill meets the 24-hour recovery target with verified data integrity and access. However, this does not establish the required outcome: a primary health-check failure leads subsequent name resolutions toward the healthy backup Region.

Migration scheduling ignored data classification and jurisdictional control requirements. The stated evidence instead indicates: Repeated uncached database work dominates response latency and compute expense.

A one-time export leaves days of writes uncopied before final deployment. The stated evidence instead indicates: Repeated uncached database work dominates response latency and compute expense.

Workflow state and failure recovery are hidden in fragile custom imperative scripts. The stated evidence instead indicates: Repeated uncached database work dominates response latency and compute expense.

Failed notifications disappear because no supported retry and DLQ design is in place. The stated evidence instead indicates: Snapshot creation is mistaken for proof the application can actually be restored.

The application is exposed to one database host or zonal compute failure. The stated evidence instead indicates: Snapshot creation is mistaken for proof the application can actually be restored.

Capacity planning ignores demand spikes or hot keys that concentrate requests. The stated evidence instead indicates: Snapshot creation is mistaken for proof the application can actually be restored.

Console changes have no reproducible declarative infrastructure state. The stated evidence instead indicates: Local instance disks are wrongly used as a shared durable POSIX file system.

A direct S3 SDK rewrite was imposed on workloads that cannot change their file interface. 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.

All assets are scheduled for direct rehost even when some are obsolete or unsuitable. The specific problem here is that mainframe batch and transaction semantics were treated as if they were ordinary Linux workloads.

Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover. The specific problem here is that mainframe batch and transaction semantics were treated as if they were ordinary Linux workloads.

Replicating table data alone does not translate incompatible source SQL constructs. The specific problem here is that mainframe batch and transaction semantics were treated as if they were ordinary Linux workloads.

CloudTrail management events are not retained or centrally available for review. The specific problem here is that gp2 capacity-linked performance assumptions lead to wasteful storage growth.

Capacity planning ignores demand spikes or hot keys that concentrate requests. The specific problem here is that gp2 capacity-linked performance assumptions lead to wasteful storage growth.

Engineers scale CPU without analyzing database lock waits or expensive SQL. The specific problem here is that gp2 capacity-linked performance assumptions lead to wasteful storage growth.

Repeated uncached database work dominates response latency and compute expense. The specific problem here is that workflow state and failure recovery are hidden in fragile custom imperative scripts.

All analytics jobs depend on a single custom ETL server and its directly attached storage. The specific problem here is that workflow state and failure recovery are hidden in fragile custom imperative scripts.

Shared data and internal method calls prevent independent deployment and scale. The specific problem here is that workflow state and failure recovery are hidden in fragile custom imperative scripts.

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: A large retail monolith has tightly coupled inventory, checkout and customer modules that scale as one deployment. It does not replace either required solution in A or B. Domain-aligned service boundaries require APIs and deliberate data ownership separation; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A legacy data center lacks a trustworthy inventory of server CPU, memory, installed processes and network connections. It does not replace either required solution in A or B. Application discovery captures real workload characteristics needed for migration planning; verify the two stated requirements independently rather than accepting an unrelated change.

On-demand usage was left wholly uncommitted despite predictable baseline compute consumption. The stated evidence instead indicates: Previous-month charges were presented as accurate forecasts for an expanded future footprint.

On-premises DNS has no forwarding path into the VPC's Route 53 Resolver. The stated evidence instead indicates: Previous-month charges were presented as accurate forecasts for an expanded future footprint.

Teams have only aggregate bills and cannot locate the source of inefficient storage usage. The stated evidence instead indicates: Previous-month charges were presented as accurate forecasts for an expanded future footprint.