Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Fixed hot storage is retained for every object because teams cannot forecast access patterns. The stated evidence instead indicates: The workload uses only on-demand capacity despite safe restart or checkpoint semantics.

Fixed EC2 capacity is provisioned 24/7 despite infrequent invocation. The stated evidence instead indicates: The workload uses only on-demand capacity despite safe restart or checkpoint semantics.

DNS simple routing cannot automatically reflect the application's health. The stated evidence instead indicates: The workload uses only on-demand capacity despite safe restart or checkpoint semantics.

Config findings are left as unactioned notifications while risky drift remains exposed. The stated evidence instead indicates: Console edits accumulate because no one compares deployed state with infrastructure definitions.

Passive regional copies exist without health-driven endpoint selection. The stated evidence instead indicates: Console edits accumulate because no one compares deployed state with infrastructure definitions.

Engineers measure host utilization but not the outcomes experienced by users. The stated evidence instead indicates: Console edits accumulate because no one compares deployed state with infrastructure definitions.

Workflow state and failure recovery are hidden in fragile custom imperative scripts. The stated evidence instead indicates: All consumers wait for a nightly export despite a near-real-time freshness requirement.

Database engine migration was assumed to be a simple homogeneous replication job. The stated evidence instead indicates: 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 stated evidence instead indicates: All consumers wait for a nightly export despite a near-real-time freshness requirement.

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: The backup team reports high snapshot completion success but no one has recovered the database from those snapshots. It does not replace either required solution in A or B. Recovery objectives require tested restore outcomes, not merely completed backups; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A shared S3 data lake gives two analytics teams unnecessarily broad bucket access. It does not replace either required solution in A or B. S3 Access Points can support distinct access policies for shared buckets; verify the two stated requirements independently rather than accepting an unrelated change.

Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable. The stated evidence instead indicates: Every backup copy resides in the same administration boundary as the threatened workloads.

The inspection design allows forward and return packets to use different stateful inspection appliances. The stated evidence instead indicates: Every backup copy resides in the same administration boundary as the threatened workloads.

No archive or retention mechanism was configured before the subscriber outage. The stated evidence instead indicates: Every backup copy resides in the same administration boundary as the threatened workloads.

Capacity commitments are purchased solely from forecast without checking historical eligible use. The stated evidence instead indicates: Unattached volumes are treated as free merely because they are not mounted.

Service-specific Health notifications are not routed into incident processes. The stated evidence instead indicates: Unattached volumes are treated as free merely because they are not mounted.

Workload service calls repeatedly cross paid network boundaries without quantified need. The stated evidence instead indicates: Unattached volumes are treated as free merely because they are not mounted.

Static worker capacity ignores observable demand while processing latency varies. The specific problem here is that storage capacity was fixed without safe growth management under variable data requirements.

Stable compute baseline is paid at on-demand rates without analyzed commitments. The specific problem here is that storage capacity was fixed without safe growth management under variable data requirements.

Console-created infrastructure diverged from versioned architecture definitions. The specific problem here is that storage capacity was fixed without safe growth management under variable data requirements.

The migration plan assumes a new AWS Snowball Edge device can still be ordered even though new-customer ordering is unavailable. The specific problem here is that a simple online copy was selected without calculating network capacity and transfer duration.

Database engine migration was assumed to be a simple homogeneous replication job. The specific problem here is that a simple online copy was selected without calculating network capacity and transfer duration.

Licensing constraints were omitted until after destination EC2 instances were chosen. The specific problem here is that a simple online copy was selected without calculating network capacity and transfer duration.

A single Direct Connect circuit creates a site-to-cloud connectivity single point of failure. The specific problem here is that on-premises DNS has no forwarding path into the VPC's Route 53 Resolver.

Separate point-to-point VPC peering connections lack transitive routing and are difficult to govern at scale. The specific problem here is that on-premises DNS has no forwarding path into the VPC's Route 53 Resolver.

The team relies exclusively on retrospective end-of-month billing statements. The specific problem here is that on-premises DNS has no forwarding path into the VPC's Route 53 Resolver.

Traffic bypasses inspection endpoints, so rules exist but are never reached. The stated evidence instead indicates: In-place overwriting of every production instance removed the healthy comparison environment.

Independent release scripts lack enforceable promotion ordering and approval evidence. The stated evidence instead indicates: In-place overwriting of every production instance removed the healthy comparison environment.

A successful compilation is treated as proof that the release is safe and functional. The stated evidence instead indicates: In-place overwriting of every production instance removed the healthy comparison environment.

Backup images exist but no continuously replicated recovery environment or launch plan is configured. The specific problem here is that every backup copy resides in the same administration boundary as the threatened workloads.

All accounts share one indiscriminate service-control policy despite different risk profiles. The specific problem here is that every backup copy resides in the same administration boundary as the threatened workloads.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The specific problem here is that every backup copy resides in the same administration boundary as the threatened workloads.