Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

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

Administrators run sensitive maintenance scripts with no enforced approval or trail. The stated evidence instead indicates: Health checks use an unrelated always-200 endpoint that does not reflect the service readiness.

Kubernetes deployment treats process startup as adequate evidence of request readiness. The stated evidence instead indicates: Health checks use an unrelated always-200 endpoint that does not reflect the service readiness.

All accounts share one indiscriminate service-control policy despite different risk profiles. The stated evidence instead indicates: Events remain confined to local account buses because cross-account bus authorization is absent.

Management-account-only operations were mistaken for necessary daily centralized security administration. The stated evidence instead indicates: Events remain confined to local account buses because cross-account bus authorization is absent.

Synchronous request-to-database coupling loses or rejects work whenever the database is unavailable. The stated evidence instead indicates: Events remain confined to local account buses because cross-account bus authorization is absent.

This action targets a different technical need: An S3 bucket is repeatedly made public and security wants prompt correction beyond simply generating findings. It does not replace either required solution in A or B. Config rules can invoke automations for selected remediable configuration noncompliance; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Finance collects optimizer suggestions from Compute Optimizer, Trusted Advisor and cost dashboards but counts the same recommendation more than once. It does not replace either required solution in A or B. Consolidated savings recommendations should not be summed blindly across sources; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A DynamoDB application requires recovery from accidental writes to an earlier point within a month. It does not replace either required solution in A or B. DynamoDB PITR restores to a selected point within its available recovery window; verify the two stated requirements independently rather than accepting an unrelated change.

Static budgets cannot explain or detect each atypical spend pattern promptly. The stated evidence instead indicates: Instances were resized from average CPU alone despite memory or traffic constraints.

No archive or retention mechanism was configured before the subscriber outage. The stated evidence instead indicates: Instances were resized from average CPU alone despite memory or traffic constraints.

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.

Premium IOPS are maintained without evidence of workload needing them. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Teams purchase more RIs independently without measuring existing shared coverage. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Console edits accumulate because no one compares deployed state with infrastructure definitions. The stated evidence instead indicates: Dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Migration tasks are tracked in separate team documents with no common portfolio state. The stated evidence instead indicates: Replicating table data alone does not translate incompatible source SQL constructs.

Mainframe batch and transaction semantics were treated as if they were ordinary Linux workloads. The stated evidence instead indicates: Replicating table data alone does not translate incompatible source SQL constructs.

Complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration. The stated evidence instead indicates: Replicating table data alone does not translate incompatible source SQL constructs.

Eligible compute charges reflect the planned commitment discount and remaining coverage is visible. However, this does not establish the required outcome: proposed architecture cost estimates can be traced to entered quantities and forecast assumptions.

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: proposed architecture cost estimates can be traced to entered quantities and forecast assumptions.

Finance sees prioritized savings opportunities and can distinguish overlapping cost recommendations. However, this does not establish the required outcome: proposed architecture cost estimates can be traced to entered quantities and forecast assumptions.

Compliance reports show applied baselines and chosen hosts patched only during approved windows. However, this does not establish the required outcome: cross-account access findings identify external principals and clear only when permissions are corrected.

The actor, source and changed policy action appear in audit events from the affected account. However, this does not establish the required outcome: cross-account access findings identify external principals and clear only when permissions are corrected.

Security Hub centrally displays eligible standardized findings with source context preserved. However, this does not establish the required outcome: cross-account access findings identify external principals and clear only when permissions are corrected.

Previous-month charges were presented as accurate forecasts for an expanded future footprint. The stated evidence instead indicates: Summary monthly bills lack the resource-level usage detail needed for chargeback.

Each application team is provisioning its own disconnected backbone gateway. The stated evidence instead indicates: Summary monthly bills lack the resource-level usage detail needed for chargeback.

The team relies exclusively on retrospective end-of-month billing statements. The stated evidence instead indicates: Summary monthly bills lack the resource-level usage detail needed for chargeback.

This action targets a different technical need: A Lambda-backed API team wants to expose only ten percent of traffic to a new function revision before promoting it. It does not replace either required solution in A or B. Lambda aliases support weighted traffic between published versions with monitored promotion; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A compliance dataset is rarely accessed after 90 days but must remain recoverable with several-hour retrieval tolerance. It does not replace either required solution in A or B. Lifecycle transitions reduce storage expense only if retrieval and minimum-duration constraints fit; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A noncritical archive service has a 24-hour RTO and may restore its configuration and data from protected backups. It does not replace either required solution in A or B. Backup-and-restore DR suits longer RTO targets when restore execution is practiced; verify the two stated requirements independently rather than accepting an unrelated change.

Consumer instances reach only the approved PrivateLink service while unrelated provider subnets remain unreachable. However, this does not establish the required outcome: eligible compute charges reflect the planned commitment discount and remaining coverage is visible.

Dashboards identify targeted buckets with abnormal storage patterns and lifecycle candidates. However, this does not establish the required outcome: eligible compute charges reflect the planned commitment discount and remaining coverage is visible.

Tested resized instances meet p95 latency goals while recommended savings are observed. However, this does not establish the required outcome: eligible compute charges reflect the planned commitment discount and remaining coverage is visible.