Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: A product releases the same service to two Regions and must require a compliance approval before the second Region goes live. It does not replace either required solution in A or B. Multi-Region pipelines can enforce explicit promotion and approval boundaries; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Unpredictably accessed objects are retained for a year, but no reliable access-frequency segmentation is known. It does not replace either required solution in A or B. S3 Intelligent-Tiering can move eligible objects among access tiers based on access frequency; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A public API has repeated abusive requests from a single source network but normal distributed traffic should continue. It does not replace either required solution in A or B. WAF rate-based rules can limit excessive HTTP request patterns by aggregation key; verify the two stated requirements independently rather than accepting an unrelated change.

Static worker capacity ignores observable demand while processing latency varies. The stated evidence instead indicates: The CDN forwards every request to origin due to ineffective cache keys or caching headers.

The workload uses only on-demand capacity despite safe restart or checkpoint semantics. The stated evidence instead indicates: The CDN forwards every request to origin due to ineffective cache keys or caching headers.

A single active Region was incorrectly advertised as having near-zero recovery time. The stated evidence instead indicates: The CDN forwards every request to origin due to ineffective cache keys or caching headers.

This action targets a different technical need: A multi-account organization must prevent member accounts from disabling mandatory CloudTrail trails even when local administrators hold broad IAM policies. It does not replace either required solution in A or B. Service control policies set permission ceilings for member account principals and cannot grant access themselves; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Legal and nonproduction workloads require different organizational guardrails but must share central billing. It does not replace either required solution in A or B. Organizational units help assign governance boundaries to related member accounts; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Operations needs one centralized queue of cost optimization recommendations from multiple AWS services. It does not replace either required solution in A or B. Cost Optimization Hub consolidates and de-duplicates supported AWS cost recommendations; verify the two stated requirements independently rather than accepting an unrelated change.

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: Network administrators must manage a shared subnet centrally while application accounts place their own resources in it. It does not replace either required solution in A or B. VPC sharing separates network ownership from application resource ownership; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Several accounts have steady EC2 and Fargate spend and need a commitment that applies to qualifying compute usage flexibly. It does not replace either required solution in A or B. Compute Savings Plans apply eligible usage discounts across supported services and configurations; verify the two stated requirements independently rather than accepting an unrelated change.

One-time offline export cannot satisfy the narrow write-freeze window. The stated evidence instead indicates: Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads.

Tight synchronous coupling propagates a noncritical downstream failure to the primary transaction. The stated evidence instead indicates: Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads.

Application reliability still depends on one unmanaged database host and manual restores. The stated evidence instead indicates: Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads.

The function's unqualified ARN always invokes latest code for all users, bypassing version routing. The stated evidence instead indicates: Each team independently patches hand-built machine images without reproducible validation.

All containers share a single placement failure domain and cannot be rescheduled in time. The stated evidence instead indicates: Each team independently patches hand-built machine images without reproducible validation.

Independent release scripts lack enforceable promotion ordering and approval evidence. The stated evidence instead indicates: Each team independently patches hand-built machine images without reproducible validation.

Application reliability still depends on one unmanaged database host and manual restores. The stated evidence instead indicates: One-time offline export cannot satisfy the narrow write-freeze window.

The migration plan assumes a new AWS Snowball Edge device can still be ordered even though new-customer ordering is unavailable. The stated evidence instead indicates: One-time offline export cannot satisfy the narrow write-freeze window.

Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover. The stated evidence instead indicates: One-time offline export cannot satisfy the narrow write-freeze window.

Every static asset fetch goes to a distant origin instead of the edge cache. The stated evidence instead indicates: The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability.

Console-created infrastructure diverged from versioned architecture definitions. The stated evidence instead indicates: The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability.

Individual account stacks were created manually and drift from the approved baseline. The stated evidence instead indicates: The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability.

This action targets a different technical need: Variable monthly expenses must trigger alerts for unusual spending spikes without predefined per-service thresholds. It does not replace either required solution in A or B. Cost Anomaly Detection learns spending patterns and flags unusual expenditures; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Critical backups must be scheduled consistently across many application accounts and retained by policy. It does not replace either required solution in A or B. Organization backup policies support common baseline definitions but still require functioning target configuration; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A customer database needs a near-real-time cross-Region read replica and an established disaster recovery promotion procedure. It does not replace either required solution in A or B. Aurora Global Database supports low-latency crossregional replication with explicit recovery operations; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A high-throughput session API must share ephemeral session data among multiple application instances without database round trips. It does not replace either required solution in A or B. A shared in-memory cache reduces backend read pressure when expiry and failure behavior are designed; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A read-heavy reporting application needs an up-to-date secondary regional database copy that can be promoted in a disaster. It does not replace either required solution in A or B. Cross-Region read replicas are asynchronous and may require explicit promotion in recovery; 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.

Local activity trails are not consolidated into the audit security boundary. The stated evidence instead indicates: Local Config assessments exist but no aggregation exposes cross-account status.

Public ACM-issued certificates were wrongly assumed to provide a corporate private CA chain. The stated evidence instead indicates: Local Config assessments exist but no aggregation exposes cross-account status.

All accounts share one indiscriminate service-control policy despite different risk profiles. The stated evidence instead indicates: Local Config assessments exist but no aggregation exposes cross-account status.