Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Fixed EC2 capacity is provisioned 24/7 despite infrequent invocation. The specific problem here is that console-created infrastructure diverged from versioned architecture definitions.

The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability. The specific problem here is that console-created infrastructure diverged from versioned architecture definitions.

Independent release scripts lack enforceable promotion ordering and approval evidence. The specific problem here is that console-created infrastructure diverged from versioned architecture definitions.

Each workload has justified retire, retain, relocate, rehost, replatform, repurchase or refactor decision. However, this does not establish the required outcome: isolated handlers scale according to request demand and meet p95 latency and authorization targets.

Kubernetes manifests and controllers operate within approved permissions and the control plane is managed. However, this does not establish the required outcome: isolated handlers scale according to request demand and meet p95 latency and authorization targets.

Local clients retain supported file access while selected data is persisted to eligible AWS storage. However, this does not establish the required outcome: isolated handlers scale according to request demand and meet p95 latency and authorization targets.

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: Hundreds of EC2 hosts need scheduled patch windows with evidence of patch compliance and approved maintenance boundaries. It does not replace either required solution in A or B. Systems Manager supports fleet patching with centralized baselines and maintenance windows; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A database team purchased oversized io2 EBS performance when measured throughput is far below its actual needs. It does not replace either required solution in A or B. EBS volume-class selection should follow measured IO and durability requirements; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A Route 53 failover policy must move users between two independent public endpoints when the primary application fails. It does not replace either required solution in A or B. DNS health-based failover changes record responses, but clients may cache prior results; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A shared API must protect downstream capacity during a request spike without losing monitoring of throttled clients. It does not replace either required solution in A or B. API Gateway throttle controls bound request rates but callers should handle 429 responses; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A Kinesis data stream has increasing write throttling because producers exceed the capacity of its current shard configuration. It does not replace either required solution in A or B. Kinesis stream performance depends on provisioned or on-demand capacity and balanced partition keys; verify the two stated requirements independently rather than accepting an unrelated change.

Each team independently patches hand-built machine images without reproducible validation. The stated evidence instead indicates: In-place overwriting of every production instance removed the healthy comparison environment.

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.

Console-created infrastructure diverged from versioned architecture definitions. The stated evidence instead indicates: In-place overwriting of every production instance removed the healthy comparison environment.

Summary monthly bills lack the resource-level usage detail needed for chargeback. The stated evidence instead indicates: Teams have only aggregate bills and cannot locate the source of inefficient storage usage.

Backup images exist but no continuously replicated recovery environment or launch plan is configured. The stated evidence instead indicates: Teams have only aggregate bills and cannot locate the source of inefficient storage usage.

Resource tags were never activated as billing cost allocation dimensions. The stated evidence instead indicates: Teams have only aggregate bills and cannot locate the source of inefficient storage usage.

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

Patch application is manual and lacks consistent baseline selection and change evidence. The stated evidence instead indicates: Engineers measure host utilization but not the outcomes experienced by users.

Availability claims rest only on architecture diagrams, not controlled chaos evidence. The stated evidence instead indicates: Engineers measure host utilization but not the outcomes experienced by users.

No event archive exists to replay notifications that failed during downstream processing. The stated evidence instead indicates: Unbounded request bursts overload backends because no gateway rate protection is configured.

The service relies solely on application code with no rate-based edge filtering. The stated evidence instead indicates: Unbounded request bursts overload backends because no gateway rate protection is configured.

Instance capacity is pinned to one zone with no automated target recovery. The stated evidence instead indicates: Unbounded request bursts overload backends because no gateway rate protection is configured.

This action targets a different technical need: A revenue-critical public endpoint requires proactive DDoS response coordination and protected eligible application resources. It does not replace either required solution in A or B. Shield Advanced adds advanced DDoS protection and response support for supported resources; verify the two stated requirements independently rather than accepting an unrelated change.

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: An order orchestration needs safe retry handling for transient service failures without rerunning completed prior steps. It does not replace either required solution in A or B. Step Functions supports explicit state-level retry and error handling but side effects still require idempotency; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A company wants to identify IAM permissions that have not been used recently before removing high-risk privileges. It does not replace either required solution in A or B. Last-accessed data informs least-privilege reviews but does not prove a permission is universally unnecessary; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Production maintenance requires an explicit approval and tracked change record before automation updates EC2 systems. It does not replace either required solution in A or B. Controlled automation separates approval from execution and preserves traceability; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A platform service incurs shared transfer charges that cannot be assigned to consuming product teams. It does not replace either required solution in A or B. CUR data and explicit allocation logic improve auditable cost attribution; verify the two stated requirements independently rather than accepting an unrelated change.

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.