Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

No archive or retention mechanism was configured before the subscriber outage. The stated evidence instead indicates: An overly broad assumed-role session is not constrained to the vendor's assigned resources.

Disjoint local-account trails leave central auditors with incomplete visibility. The stated evidence instead indicates: An overly broad assumed-role session is not constrained to the vendor's assigned resources.

Individual IAM users were being created per account instead of using centralized workforce federation. The stated evidence instead indicates: An overly broad assumed-role session is not constrained to the vendor's assigned resources.

Passive regional copies exist without health-driven endpoint selection. The stated evidence instead indicates: Failed notifications disappear because no supported retry and DLQ design is in place.

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

One overbroad bucket-level policy grants both teams access to all data. The stated evidence instead indicates: Failed notifications disappear because no supported retry and DLQ design is in place.

This action targets a different technical need: A shared EFS file system slows a data-processing batch even though compute workers are mostly idle. It does not replace either required solution in A or B. EFS throughput characteristics must match concurrent IO patterns and required sustained rate; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A payment service must block production release if vulnerability and smoke-test gates fail, even though the build itself succeeded. It does not replace either required solution in A or B. Release pipelines should verify deployment risk and acceptance criteria beyond build success; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A rarely used API experiences extreme idle hours and unpredictable spikes, making always-on EC2 capacity uneconomic. It does not replace either required solution in A or B. Serverless consumption models can reduce idle infrastructure charges for intermittent traffic; verify the two stated requirements independently rather than accepting an unrelated change.

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: Operations cannot trace a customer transaction once it crosses more than six loosely coupled services. It does not replace either required solution in A or B. Unified trace context and structured observability improve distributed troubleshooting; 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 organization has a COBOL mainframe workflow that requires staged modernization rather than a blind VM copy. It does not replace either required solution in A or B. Mainframe migrations need purpose-built assessment and conversion or replatform planning; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Operations cannot trace a customer transaction once it crosses more than six loosely coupled services. It does not replace either required solution in A or B. Unified trace context and structured observability improve distributed troubleshooting; 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.

Static budgets cannot explain or detect each atypical spend pattern promptly. The specific problem here is that summary monthly bills lack the resource-level usage detail needed for chargeback.

Per-account one-off inspections do not continuously evaluate drift across accounts. The specific problem here is that summary monthly bills lack the resource-level usage detail needed for chargeback.

Teams have only aggregate bills and cannot locate the source of inefficient storage usage. The specific problem here is that summary monthly bills lack the resource-level usage detail needed for chargeback.

Eligible accounts create scheduled recovery points according to policies and restores are tested. However, this does not establish the required outcome: a controlled threshold breach yields the expected forecast or actual spend notification.

A synthetic or observed unusual cost pattern appears in anomaly alerts with impacted spend drivers. However, this does not establish the required outcome: a controlled threshold breach yields the expected forecast or actual spend notification.

Shared applicable discounts and uncovered on-demand baseline are visible by linked account. However, this does not establish the required outcome: a controlled threshold breach yields the expected forecast or actual spend notification.

This action targets a different technical need: Capacity planners need a monthly cost forecast that reflects a new Region and expected usage growth before deployment. It does not replace either required solution in A or B. Architecture forecasts require explicit usage assumptions rather than extrapolation without design changes; 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.

This action targets a different technical need: A latency-sensitive global TCP application requires fast traffic steering to healthy regional application load balancers using static anycast addresses. It does not replace either required solution in A or B. Global Accelerator provides stable global anycast addresses and network-level endpoint health routing; verify the two stated requirements independently rather than accepting an unrelated change.

Objects remain indefinitely in higher-cost storage despite a proven low-access retention pattern. The stated evidence instead indicates: A single active Region was incorrectly advertised as having near-zero recovery time.

All containers share a single placement failure domain and cannot be rescheduled in time. The stated evidence instead indicates: A single active Region was incorrectly advertised as having near-zero recovery time.

Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO. The stated evidence instead indicates: A single active Region was incorrectly advertised as having near-zero recovery time.

Imperative glue retries all upstream steps and creates duplicate side effects. The stated evidence instead indicates: The service relies solely on application code with no rate-based edge filtering.

Service API traffic depends on public egress or an unintended NAT route despite a private-access requirement. The stated evidence instead indicates: The service relies solely on application code with no rate-based edge filtering.

A static password in deployment parameters cannot be centrally rotated safely. The stated evidence instead indicates: The service relies solely on application code with no rate-based edge filtering.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The stated evidence instead indicates: Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

The backup Region exists but DNS routing never changes after primary endpoint failure. The stated evidence instead indicates: Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.

Individual IAM users were being created per account instead of using centralized workforce federation. The stated evidence instead indicates: Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable.