Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: A department must be notified promptly when monthly spending exceeds its threshold. It does not replace either required solution in A or B. AWS Budgets supports spend targets and notifications on actual or forecasted cost; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A company uses Direct Connect for normal hybrid traffic but needs encrypted emergency connectivity if carrier circuits fail. It does not replace either required solution in A or B. A tested secondary encrypted tunnel path can carry critical traffic while primary private connectivity is unavailable; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A vendor assumes a role into an AWS account and must be restricted to one project's S3 prefix for that session only. It does not replace either required solution in A or B. Session policies intersect with role permissions and can reduce privileges for one temporary session; verify the two stated requirements independently rather than accepting an unrelated change.

Overlapping network prefixes make ordinary VPC peering route selection ambiguous. The stated evidence instead indicates: The architecture assumes that Transit Gateway peering automatically propagates interregional routes.

Separate point-to-point VPC peering connections lack transitive routing and are difficult to govern at scale. The stated evidence instead indicates: The architecture assumes that Transit Gateway peering automatically propagates interregional routes.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The stated evidence instead indicates: The architecture assumes that Transit Gateway peering automatically propagates interregional routes.

Shared costs are assigned by arbitrary percentage without service consumption evidence. The stated evidence instead indicates: Capacity commitments are purchased solely from forecast without checking historical eligible use.

Workload service calls repeatedly cross paid network boundaries without quantified need. The stated evidence instead indicates: Capacity commitments are purchased solely from forecast without checking historical eligible use.

Capacity planning ignores demand spikes or hot keys that concentrate requests. The stated evidence instead indicates: Capacity commitments are purchased solely from forecast without checking historical eligible use.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The specific problem here is that a single-Region DynamoDB table cannot accept the required local writes after that Region fails.

Resource tags were never activated as billing cost allocation dimensions. The specific problem here is that a single-Region DynamoDB table cannot accept the required local writes after that Region fails.

A single-Region Aurora cluster lacks a suitable crossregional disaster recovery target. The specific problem here is that a single-Region DynamoDB table cannot accept the required local writes after that Region fails.

A simulated Direct Connect failure moves approved routes to VPN tunnels and restore reverses route preference. However, this does not establish the required outcome: the delegated administrator can manage enrolled member security coverage within its supported scope.

Approved application accounts can create authorized attachments to the centrally owned gateway. However, this does not establish the required outcome: the delegated administrator can manage enrolled member security coverage within its supported scope.

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: the delegated administrator can manage enrolled member security coverage within its supported scope.

Shared per-shard read throughput is divided among too many polling consumers. The stated evidence instead indicates: Cluster compute totals are misleading because the needed task resources are not schedulable.

Workload service calls repeatedly cross paid network boundaries without quantified need. The stated evidence instead indicates: Cluster compute totals are misleading because the needed task resources are not schedulable.

On-demand initialization latency is not addressed for the critical invocation path. The stated evidence instead indicates: Cluster compute totals are misleading because the needed task resources are not schedulable.

All consumers wait for a nightly export despite a near-real-time freshness requirement. The specific problem here is that a non-Kubernetes orchestrator was chosen despite strict Kubernetes extension compatibility requirements.

All analytics jobs depend on a single custom ETL server and its directly attached storage. The specific problem here is that a non-Kubernetes orchestrator was chosen despite strict Kubernetes extension compatibility requirements.

Application reliability still depends on one unmanaged database host and manual restores. The specific problem here is that a non-Kubernetes orchestrator was chosen despite strict Kubernetes extension compatibility requirements.

Migration estimates are based solely on outdated procurement records rather than measured workload behavior. The specific problem here is that source virtualization format was mistaken for a guarantee of target runtime compatibility.

An all-at-once replacement has unacceptable outage and rollback risk. The specific problem here is that source virtualization format was mistaken for a guarantee of target runtime compatibility.

Migration scheduling ignored data classification and jurisdictional control requirements. The specific problem here is that source virtualization format was mistaken for a guarantee of target runtime compatibility.

All consumers wait for a nightly export despite a near-real-time freshness requirement. The stated evidence instead indicates: The only purpose of a 24/7 server is occasional timer-based work.

A one-time export leaves days of writes uncopied before final deployment. The stated evidence instead indicates: The only purpose of a 24/7 server is occasional timer-based work.

Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads. The stated evidence instead indicates: The only purpose of a 24/7 server is occasional timer-based work.

Teams purchase more RIs independently without measuring existing shared coverage. The specific problem here is that shared costs are assigned by arbitrary percentage without service consumption evidence.

Static security policy documents are not technically enforced against resource drift. The specific problem here is that shared costs are assigned by arbitrary percentage without service consumption evidence.

Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance. The specific problem here is that shared costs are assigned by arbitrary percentage without service consumption evidence.

This action targets a different technical need: Two Regions are deployed but customer requests stay routed to the failed primary endpoint indefinitely. It does not replace either required solution in A or B. DNS failover needs a health-signal and routing policy that actually switches answers; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A transactional RDS instance becomes slow under concurrency and the team needs to distinguish SQL waits from CPU pressure. It does not replace either required solution in A or B. Database performance diagnostics should identify the specific bottleneck before scaling; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: The security team manages GuardDuty separately in 50 accounts and misses newly created member accounts. It does not replace either required solution in A or B. Central GuardDuty administration supports ongoing multi-account detection enrollment; verify the two stated requirements independently rather than accepting an unrelated change.