Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

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 platform team deploys the same baseline IAM roles and configuration stacks into 70 governed member accounts. It does not replace either required solution in A or B. CloudFormation StackSets manages stack instances across accounts and Regions from a controlled template; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A central security team needs automated detections for unusual cross-account API activity and suspected credential misuse. It does not replace either required solution in A or B. GuardDuty consumes AWS data sources to identify suspicious behavior and report findings; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A large S3 estate has unknown replication, storage-class, and lifecycle patterns that drive storage expense. It does not replace either required solution in A or B. S3 Storage Lens supports visibility into storage activity and efficiency metrics; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Two acquired subsidiaries have overlapping RFC1918 VPC CIDRs but must exchange traffic with a shared integration endpoint. It does not replace either required solution in A or B. Overlapping address spaces require translation or service-level isolation rather than simple routed peering; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Compliance requires protected organization-wide API activity logs to flow into a centralized security account with controlled deletion. It does not replace either required solution in A or B. AWS Organizations trails centralize multi-account CloudTrail logging when storage access is secured; verify the two stated requirements independently rather than accepting an unrelated change.

Every backup copy resides in the same administration boundary as the threatened workloads. The stated evidence instead indicates: 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 stated evidence instead indicates: Savings recommendations exist in separate consoles and are double counted in spreadsheets.

Summary monthly bills lack the resource-level usage detail needed for chargeback. The stated evidence instead indicates: Savings recommendations exist in separate consoles and are double counted in spreadsheets.

Always-on monolith capacity is required merely to handle infrequent independent endpoints. The specific problem here is that licensing constraints were omitted until after destination EC2 instances were chosen.

Migration tasks are tracked in separate team documents with no common portfolio state. The specific problem here is that licensing constraints were omitted until after destination EC2 instances were chosen.

Application lists omit runtime call dependencies and produce broken split-wave migrations. The specific problem here is that licensing constraints were omitted until after destination EC2 instances were chosen.

Separate analysts query approved lake datasets without direct access to the legacy ETL host. However, this does not establish the required outcome: kubernetes manifests and controllers operate within approved permissions and the control plane is managed.

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

New capability traffic can be rolled back while untouched monolith endpoints remain functional. However, this does not establish the required outcome: kubernetes manifests and controllers operate within approved permissions and the control plane is managed.

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 Kinesis stream has adequate shard write capacity but multiple consumers compete for read throughput and fall behind. It does not replace either required solution in A or B. Kinesis enhanced fan-out provides dedicated consumer read throughput within service limits; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Two Regions are deployed but customer requests stay routed to the failed primary endpoint indefinitely. It does not replace either required solution in A or B. DNS failover needs a health-signal and routing policy that actually switches answers; verify the two stated requirements independently rather than accepting an unrelated change.

Migration tasks are tracked in separate team documents with no common portfolio state. The stated evidence instead indicates: Partners are forced to replace SFTP clients with AWS SDK calls without business approval.

Complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration. The stated evidence instead indicates: Partners are forced to replace SFTP clients with AWS SDK calls without business approval.

Traffic was switched to the container environment before dependent services and probes were verified. The stated evidence instead indicates: Partners are forced to replace SFTP clients with AWS SDK calls without business approval.

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: a deliberately noncompliant bucket triggers the configured corrective control and audit records.

Release decisions reference tracked error rate and latency burn rather than raw instance uptime alone. However, this does not establish the required outcome: a deliberately noncompliant bucket triggers the configured corrective control and audit records.

Identified buckets show smaller unnecessary version and multipart storage after retention-safe cleanup. However, this does not establish the required outcome: a deliberately noncompliant bucket triggers the configured corrective control and audit records.

Individual IAM users were being created per account instead of using centralized workforce federation. The specific problem here is that local identity permissions were incorrectly treated as overriding organizational guardrails.

Individual Security Hub instances were not centrally delegated or aggregated. The specific problem here is that local identity permissions were incorrectly treated as overriding organizational guardrails.

The backup Region exists but DNS routing never changes after primary endpoint failure. The specific problem here is that local identity permissions were incorrectly treated as overriding organizational guardrails.

Previous-month charges were presented as accurate forecasts for an expanded future footprint. The specific problem here is that rI purchases are evaluated only in the purchasing account without considering shared billing treatment.

Individual Security Hub instances were not centrally delegated or aggregated. The specific problem here is that rI purchases are evaluated only in the purchasing account without considering shared billing treatment.

Static budgets cannot explain or detect each atypical spend pattern promptly. The specific problem here is that rI purchases are evaluated only in the purchasing account without considering shared billing treatment.

Untracked imperative orchestration repeats previous side effects after transient failures. The specific problem here is that dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Capacity commitments are purchased solely from forecast without checking historical eligible use. The specific problem here is that dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.

Unattached volumes are treated as free merely because they are not mounted. The specific problem here is that dormant storage versions and partial uploads accumulate without inventory or lifecycle governance.