Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: Service owners cannot separate API traffic incidents from infrastructure incidents across ten microservices. It does not replace either required solution in A or B. Meaningful dashboards align telemetry with system service boundaries and indicators; 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: An EKS service experiences 503 errors during rolling updates because pods accept traffic before dependencies initialize. It does not replace either required solution in A or B. Readiness and graceful termination controls reduce errors during normal rolling changes; verify the two stated requirements independently rather than accepting an unrelated change.

Console edits accumulate because no one compares deployed state with infrastructure definitions. The stated evidence instead indicates: Service-specific Health notifications are not routed into incident processes.

Capacity commitments are purchased solely from forecast without checking historical eligible use. The stated evidence instead indicates: Service-specific Health notifications are not routed into incident processes.

Engineers measure host utilization but not the outcomes experienced by users. The stated evidence instead indicates: Service-specific Health notifications are not routed into incident processes.

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 global static web application experiences high latency because users repeatedly fetch unchanged assets from one Region. It does not replace either required solution in A or B. CloudFront edge caching reduces origin fetches for cacheable content; 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.

A retry resumes the failed state without independently rerunning successful steps and errors are visible in execution history. However, this does not establish the required outcome: deliberately changed parameters are reported as drift and corrected through approved IaC updates.

Logs identify blocked and counted requests by rule so false positives can be evaluated. However, this does not establish the required outcome: deliberately changed parameters are reported as drift and corrected through approved IaC updates.

A deliberately noncompliant bucket triggers the configured corrective control and audit records. However, this does not establish the required outcome: deliberately changed parameters are reported as drift and corrected through approved IaC updates.

IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy. The stated evidence instead indicates: Service API traffic depends on public egress or an unintended NAT route despite a private-access requirement.

A public bucket policy exposes origin objects outside the intended CloudFront access path. The stated evidence instead indicates: Service API traffic depends on public egress or an unintended NAT route despite a private-access requirement.

Unbounded request bursts overload backends because no gateway rate protection is configured. The stated evidence instead indicates: Service API traffic depends on public egress or an unintended NAT route despite a private-access requirement.

This action targets a different technical need: Regulators require consistent detection and correction of publicly accessible S3 buckets across a multi-account organization. It does not replace either required solution in A or B. Organization-level Config rules continuously evaluate configuration and can launch controlled remediations; verify the two stated requirements independently rather than accepting an unrelated change.

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: Two regional Transit Gateways must exchange approved network prefixes without provisioning a separate VPC-to-VPC peering mesh. It does not replace either required solution in A or B. Transit Gateway peering requires explicit routing between the regional gateways; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A platform team learns about upcoming service maintenance only after workloads start failing. It does not replace either required solution in A or B. AWS Health can surface AWS-side events relevant to affected resources and accounts; 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: An incident reviewer needs a timeline of a suspicious IAM policy change made across member accounts. It does not replace either required solution in A or B. CloudTrail API event evidence supports investigation of changes to account control-plane resources; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An ECS fleet is experiencing p99 delays but per-container CPU and memory usage are absent from operational dashboards. It does not replace either required solution in A or B. Container Insights provides enhanced telemetry for container infrastructure; 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.

This action targets a different technical need: A shared S3 estate has ballooning noncurrent versions, incomplete multipart uploads and forgotten small objects. It does not replace either required solution in A or B. S3 analytics and lifecycle rules target recoverable storage waste when retention is respected; verify the two stated requirements independently rather than accepting an unrelated change.

Resource-based trust was not evaluated beyond local IAM identity permission reports. The stated evidence instead indicates: Role policies retain privileges indefinitely without evidence about actual service usage.

Uncorrelated logs hide where the end-to-end latency accumulates. The stated evidence instead indicates: Role policies retain privileges indefinitely without evidence about actual service usage.

Teams confuse key material rotation with replacing the KMS key ID and losing access to old data. The stated evidence instead indicates: Role policies retain privileges indefinitely without evidence about actual service usage.

The abusive source crosses its request threshold and is blocked without blocking allowed sample traffic. However, this does not establish the required outcome: approved flows pass and test policy-violating flows are logged and blocked in both traffic directions.

A regional drill scales warm standby to full capacity within the stated recovery time and data tolerance. However, this does not establish the required outcome: approved flows pass and test policy-violating flows are logged and blocked in both traffic directions.

Cloud instances access approved services privately while disallowed API paths are rejected. However, this does not establish the required outcome: approved flows pass and test policy-violating flows are logged and blocked in both traffic directions.

This action targets a different technical need: A legacy database must meet high transactional availability and can accept conversion to an Aurora-compatible engine. It does not replace either required solution in A or B. Aurora offers managed high availability features for supported relational engines; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A legacy billing system runs nightly ETL and downstream consumers need near-real-time invoice changes. It does not replace either required solution in A or B. CDC-based event distribution can modernize delayed batch data propagation; 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.