Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: Many workload VPCs need access to a privately published service without opening routing to the provider's whole VPC. It does not replace either required solution in A or B. AWS PrivateLink exposes a selected service to consumers without full network-to-network reachability; 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: Dozens of overprovisioned EC2 instances need evidence-based CPU and memory sizing recommendations before changing families. It does not replace either required solution in A or B. Compute Optimizer uses resource metrics and recommendations but must be checked against workload SLOs; verify the two stated requirements independently rather than accepting an unrelated change.

Employees sign in using enterprise identities and receive only the mapped roles in assigned accounts. However, this does not establish the required outcome: a noncompliant test bucket is flagged and the remediation removes its unauthorized public exposure.

Every enrolled account produces expected trail events in the security account and workloads cannot delete retained logs. However, this does not establish the required outcome: a noncompliant test bucket is flagged and the remediation removes its unauthorized public exposure.

Writes in either Region replicate to the other and conflict handling matches the business design. However, this does not establish the required outcome: a noncompliant test bucket is flagged and the remediation removes its unauthorized public exposure.

Logs identify blocked and counted requests by rule so false positives can be evaluated. However, this does not establish the required outcome: chosen sizes meet memory and peak latency needs while reducing wasteful instance spending.

Tested gp3 configuration meets IO SLOs at lower monthly storage and provisioned-performance cost. However, this does not establish the required outcome: chosen sizes meet memory and peak latency needs while reducing wasteful instance spending.

Finance reports one adjusted opportunity per overlapping recommendation source. However, this does not establish the required outcome: chosen sizes meet memory and peak latency needs while reducing wasteful instance spending.

Every reporting query was sent to the cluster writer endpoint despite available readers. The specific problem here is that fixed EC2 capacity is provisioned 24/7 despite infrequent invocation.

Storage capacity was fixed without safe growth management under variable data requirements. The specific problem here is that fixed EC2 capacity is provisioned 24/7 despite infrequent invocation.

The workload uses only on-demand capacity despite safe restart or checkpoint semantics. The specific problem here is that fixed EC2 capacity is provisioned 24/7 despite infrequent invocation.

Independent release scripts lack enforceable promotion ordering and approval evidence. The stated evidence instead indicates: The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability.

The destination bucket is present but replication cannot use the destination KMS key. The stated evidence instead indicates: The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability.

Each team independently patches hand-built machine images without reproducible validation. The stated evidence instead indicates: The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability.

Small traffic shares move to the new stack first; an error alarm redirects traffic to the proven stack. However, this does not establish the required outcome: actual eligible usage receives commitment coverage while variable spikes remain flexible.

The API meets latency SLOs under bursts and incurs low idle compute spend without permanently allocated hosts. However, this does not establish the required outcome: actual eligible usage receives commitment coverage while variable spikes remain flexible.

Worker count falls during light load and rises when queue age approaches the delivery deadline. However, this does not establish the required outcome: actual eligible usage receives commitment coverage while variable spikes remain flexible.

No archive or retention mechanism was configured before the subscriber outage. The stated evidence instead indicates: Individual IAM users were being created per account instead of using centralized workforce federation.

Resource policies were never checked for access beyond the organization's trust boundary. The stated evidence instead indicates: Individual IAM users were being created per account instead of using centralized workforce federation.

The remote principal has S3 object access but lacks required key-policy and IAM decrypt permission. The stated evidence instead indicates: Individual IAM users were being created per account instead of using centralized workforce federation.

This action targets a different technical need: External trading partners depend on SFTP interfaces, but the receiving application will store files in S3. It does not replace either required solution in A or B. AWS Transfer Family exposes managed file-transfer protocols to supported AWS storage; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An ecommerce backend repeatedly recomputes expensive reads for product listings that change infrequently. It does not replace either required solution in A or B. Correct cache placement and invalidation reduce repeated work without violating freshness needs; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Branch offices retain file shares locally but need backup and tiered cloud-backed storage without replacing every client. It does not replace either required solution in A or B. Storage Gateway helps bridge supported on-premises storage protocols to AWS-backed storage; verify the two stated requirements independently rather than accepting an unrelated change.

New accounts are assembled by ad hoc scripts with inconsistent security baselines. The specific problem here is that savings recommendations exist in separate consoles and are double counted in spreadsheets.

Instances were resized from average CPU alone despite memory or traffic constraints. The specific problem here is that savings recommendations exist in separate consoles and are double counted in spreadsheets.

Previous-month charges were presented as accurate forecasts for an expanded future footprint. The specific problem here is that savings recommendations exist in separate consoles and are double counted in spreadsheets.

Metrics and logs are not organized into actionable per-service operational signals. The specific problem here is that service-specific Health notifications are not routed into incident processes.

Role policies retain privileges indefinitely without evidence about actual service usage. The specific problem here is that service-specific Health notifications are not routed into incident processes.

Console edits accumulate because no one compares deployed state with infrastructure definitions. The specific problem here is that service-specific Health notifications are not routed into incident processes.

This action targets a different technical need: A corporate SOC needs one prioritized security findings view across enabled security services and Regions. It does not replace either required solution in A or B. Security Hub consolidates security posture and findings from participating services; 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: 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.