Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Objects remain indefinitely in higher-cost storage despite a proven low-access retention pattern. The specific problem here is that the workload uses only on-demand capacity despite safe restart or checkpoint semantics.

S3 calls egress through NAT because no supported endpoint route was configured. The specific problem here is that the workload uses only on-demand capacity despite safe restart or checkpoint semantics.

Backup administrators can freely delete critical recovery points despite required immutability. The specific problem here is that the workload uses only on-demand capacity despite safe restart or checkpoint semantics.

A new workload account's API activity appears in the central log bucket and member administrators cannot erase it. However, this does not establish the required outcome: central compliance dashboards include resource findings from configured participating accounts and Regions.

Cost and Usage Reports or Cost Explorer show tagged team spend after activation and reporting delay. However, this does not establish the required outcome: central compliance dashboards include resource findings from configured participating accounts and Regions.

Approved application accounts can create authorized attachments to the centrally owned gateway. However, this does not establish the required outcome: central compliance dashboards include resource findings from configured participating accounts and Regions.

This action targets a different technical need: A multi-AZ production stack has never been tested with a failed Availability Zone during working hours. It does not replace either required solution in A or B. Fault injection validates real system behavior within approved experiment boundaries; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Operations retains detached EBS volumes after instance termination and pays for unused storage for months. It does not replace either required solution in A or B. EBS storage billing continues for allocated volumes until they are deleted or otherwise changed; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A Kinesis stream has adequate shard write capacity but multiple consumers compete for read throughput and fall behind. It does not replace either required solution in A or B. Kinesis enhanced fan-out provides dedicated consumer read throughput within service limits; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Business units need temporary developer access to multiple accounts but not permanent local IAM users. It does not replace either required solution in A or B. Central identity assignments reduce stale credentials and standardize workforce access; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A customer database needs a near-real-time cross-Region read replica and an established disaster recovery promotion procedure. It does not replace either required solution in A or B. Aurora Global Database supports low-latency crossregional replication with explicit recovery operations; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A bucket policy accidentally grants an external AWS account access and the owner needs a provable cross-account finding. It does not replace either required solution in A or B. IAM Access Analyzer analyzes resource-based policies for external access outside the chosen trust zone; verify the two stated requirements independently rather than accepting an unrelated change.

Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover. The stated evidence instead indicates: All assets are scheduled for direct rehost even when some are obsolete or unsuitable.

Migration estimates are based solely on outdated procurement records rather than measured workload behavior. The stated evidence instead indicates: All assets are scheduled for direct rehost even when some are obsolete or unsuitable.

Migration tasks are tracked in separate team documents with no common portfolio state. The stated evidence instead indicates: All assets are scheduled for direct rehost even when some are obsolete or unsuitable.

Health checks use an unrelated always-200 endpoint that does not reflect the service readiness. The stated evidence instead indicates: The application is exposed to one database host or zonal compute failure.

WAF rules are deployed without visibility into which requests they affect. The stated evidence instead indicates: The application is exposed to one database host or zonal compute failure.

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

This action targets a different technical need: Executives request one default migration method for every workload regardless of technical debt or value. It does not replace either required solution in A or B. The 7 Rs decision framework matches migration strategy to application context; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An AWS Enterprise Support research customer needs to migrate tens of terabytes from a remote site with unreliable network links and can bring storage to a nearby AWS transfer facility. It does not replace either required solution in A or B. AWS Data Transfer Terminal allows eligible Enterprise Support customers to bring storage to an AWS transfer site; AWS Snowball Edge is no longer available to new customers; 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.

Teams have only aggregate bills and cannot locate the source of inefficient storage usage. The stated evidence instead indicates: Instances were resized from average CPU alone despite memory or traffic constraints.

Resource tags were never activated as billing cost allocation dimensions. The stated evidence instead indicates: Instances were resized from average CPU alone despite memory or traffic constraints.

Disjoint local-account trails leave central auditors with incomplete visibility. The stated evidence instead indicates: Instances were resized from average CPU alone despite memory or traffic constraints.

Read replica lag is measured and promotion produces a usable independent writer during a DR drill. However, this does not establish the required outcome: the load balancer continues serving from healthy remaining tasks during a forced zone failure.

Failure of one Region does not interrupt healthy remaining regional capacity under synthetic load. However, this does not establish the required outcome: the load balancer continues serving from healthy remaining tasks during a forced zone failure.

Cloud instances access approved services privately while disallowed API paths are rejected. However, this does not establish the required outcome: the load balancer continues serving from healthy remaining tasks during a forced zone failure.

That evidence is associated with a separate architecture requirement: A mission-critical RDS instance is single-AZ and routine maintenance causes extended application downtime. It does not prove that this case was remediated. The relevant observation must be: Load tests show traffic reaches only ready pods and terminating pods finish work before deletion. The associated design principle is: Readiness and graceful termination controls reduce errors during normal rolling changes.

Restored datasets pass consistency and application startup checks within the recovery target. However, this does not establish the required outcome: load tests show traffic reaches only ready pods and terminating pods finish work before deletion.

Origin request count drops under a multi-edge cache miss test while freshness remains correct. However, this does not establish the required outcome: load tests show traffic reaches only ready pods and terminating pods finish work before deletion.

Engineers scale CPU without analyzing database lock waits or expensive SQL. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Unattached volumes are treated as free merely because they are not mounted. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Workload service calls repeatedly cross paid network boundaries without quantified need. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.