Practice Exams:

View All

Amazon AWS Solutions Architect Professional SAP-C02 Reliability Improvement Replication Scaling Practice Test

Domain 3.4 • 25 original questions

This AWS SAP-C02 AWS Certified Solutions Architect – Professional practice test focuses on reliability improvement replication scaling single points of failure and quotas through original architecture scenarios aligned to the current AWS Certification exam guide. Use the full ExamSnap SAP-C02 collection for practice across all four content domains. For broader exam preparation, review the Amazon AWS Certified Solutions Architect – Professional SAP-C02 Exam Dumps page.

Instructions: Select the best answer for each question. Review the explanation after answering; each distractor includes a reason it is not the best choice for that scenario.

Question 1

A principal solutions architect at Wide World Importers is reviewing a global web application. The business requires the team to find and remove a single NAT instance, database node, or appliance that can fail the whole workload while using measurable evidence before and after remediation. Which design most directly satisfies the requirement? The current estate includes 48 AWS accounts and active workloads in us-east-1 and us-west-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Benchmark candidate instance families or scaling designs under representative load, then rightsize using observed CPU, memory, network, and storage characteristics
Use centralized CloudWatch observability with actionable alarms and event-driven or Systems Manager automation for known remediation paths
Use Systems Manager or service-native configuration automation, and run controlled failure scenarios to validate recovery procedures

Correct answer: A

Why: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while using measurable evidence before and after remediation.

Option review:

A: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while using measurable evidence before and after remediation.

B: Rightsizing and high-performance compute choices should be validated against real workload characteristics and performance objectives. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while using measurable evidence before and after remediation.

C: Monitoring should produce useful signals and, where safe, trigger repeatable remediation instead of relying on manual observation of every component. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while using measurable evidence before and after remediation.

D: Configuration automation reduces drift, while failure exercises reveal gaps in monitoring, dependencies, and operational recovery knowledge. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while using measurable evidence before and after remediation.

Learning point: Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain. Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. In this variant, the decision also has to work while using measurable evidence before and after remediation.

Question 2

Bellows University is changing its order-processing system as part of a security design review. Which AWS approach best enables the team to enable self-healing replicas and scaling based on measured demand while using measurable evidence before and after remediation? The current estate includes 8 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

Use Cost and Usage Reports or equivalent detailed billing data with cost-allocation tags, Budgets, and alarms to analyze transfer charges and assign ownership
Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity
Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it
Use Systems Manager or service-native configuration automation, and run controlled failure scenarios to validate recovery procedures

Correct answer: B

Why: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This directly addresses the primary requirement and remains appropriate while using measurable evidence before and after remediation.

Option review:

A: Granular billing data, allocation tags, and alerts provide the visibility needed to explain spend and drive accountable cost remediation. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while using measurable evidence before and after remediation.

B: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This directly addresses the primary requirement and remains appropriate while using measurable evidence before and after remediation.

C: Automation is most valuable for well-understood recurring actions when it remains observable, controlled, and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while using measurable evidence before and after remediation.

D: Configuration automation reduces drift, while failure exercises reveal gaps in monitoring, dependencies, and operational recovery knowledge. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while using measurable evidence before and after remediation.

Learning point: Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity. Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. In this variant, the decision also has to work while using measurable evidence before and after remediation.

Question 3

An architecture board at Blue Yonder Airlines asks the enterprise architect to verify that a recovery Region can actually launch the required capacity during an outage while using measurable evidence before and after remediation for a analytics pipeline. Which recommendation is most appropriate? The current estate includes 15 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. Prefer an AWS-managed capability when it meets the requirements with less operational overhead.

Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Store secrets in Secrets Manager or Parameter Store as appropriate, enforce least privilege, and review access against data sensitivity and regulatory requirements
Use the AWS global delivery or managed service that matches the workload protocol and access pattern, such as CloudFront for cacheable content or Global Accelerator for network-path optimization
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment

Correct answer: D

Why: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate while using measurable evidence before and after remediation.

Option review:

A: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while using measurable evidence before and after remediation.

B: Secret management and least privilege reduce credential exposure and unnecessary authority, especially for regulated or sensitive workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while using measurable evidence before and after remediation.

C: AWS global and managed services can improve latency and reduce operational burden when selected for the application protocol and caching or routing model. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while using measurable evidence before and after remediation.

D: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate while using measurable evidence before and after remediation.

Learning point: Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment. A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. In this variant, the decision also has to work while using measurable evidence before and after remediation.

Question 4

For a media processing platform at City Power, a production readiness review identifies one priority: find and remove a single NAT instance, database node, or appliance that can fail the whole workload without making unrelated architecture changes. Which AWS design should the team choose? The current estate includes 22 AWS accounts and active workloads in eu-west-1 and eu-central-1. The team wants the most direct architecture decision for this requirement.

Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Use Cost Explorer, Compute Optimizer, Trusted Advisor, and service inventory data to identify idle or overprovisioned resources, then remove or rightsize them safely
Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment

Correct answer: A

Option review:

B: Cost optimization begins by measuring utilization and identifying resources whose size or existence is not justified by workload demand. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of without making unrelated architecture changes.

C: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of without making unrelated architecture changes.

D: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of without making unrelated architecture changes.

Question 5

A principal architect asks which AWS approach is intended to enable self-healing replicas and scaling based on measured demand without making unrelated architecture changes. What is the best answer? The current estate includes 29 AWS accounts and active workloads in us-east-1 and us-west-2. The design must preserve security and auditability while meeting the stated objective.

Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it
Perform a structured Well-Architected-style review using operational telemetry, security findings, and reliability evidence, then prioritize risks by business impact
Use CloudTrail and AWS security/configuration services for traceability and findings, with AWS Config/EventBridge/automation for controlled remediation
Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity

Correct answer: D

Option review:

A: Automation is most valuable for well-understood recurring actions when it remains observable, controlled, and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of without making unrelated architecture changes.

B: Continuous improvement is most effective when recommendations are grounded in measurable risk and workload evidence across multiple architectural dimensions. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of without making unrelated architecture changes.

C: Traceability, centralized findings, and safe automation help teams detect policy drift and reduce time to remediate recurring security issues. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of without making unrelated architecture changes.

D: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This directly addresses the primary requirement and remains appropriate without making unrelated architecture changes.

Question 6

While conducting a hybrid connectivity redesign, the cloud platform architect at Southridge Video needs to verify that a recovery Region can actually launch the required capacity during an outage without making unrelated architecture changes. Which architecture decision best matches the stated constraints? The current estate includes 36 AWS accounts and active workloads in us-east-1 and eu-west-1. Select the option that satisfies the requirement with the fewest unnecessary moving parts.

Analyze the stable post-rightsizing usage baseline, then purchase the commitment model that matches flexibility and term requirements
Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Store secrets in Secrets Manager or Parameter Store as appropriate, enforce least privilege, and review access against data sensitivity and regulatory requirements
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment

Correct answer: D

Option review:

A: Commitments are most effective after rightsizing and when the organization understands which usage is predictably sustained. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of without making unrelated architecture changes.

B: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of without making unrelated architecture changes.

C: Secret management and least privilege reduce credential exposure and unnecessary authority, especially for regulated or sensitive workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of without making unrelated architecture changes.

D: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate without making unrelated architecture changes.

Question 7

During a resilience assessment at Woodgrove Bank, the site reliability architect is designing a analytics pipeline. The requirement is to find and remove a single NAT instance, database node, or appliance that can fail the whole workload while preserving the workload service objective during the improvement. Which architecture is the best fit? The current estate includes 43 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Use Systems Manager or service-native configuration automation, and run controlled failure scenarios to validate recovery procedures
Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Use Cost Explorer, Compute Optimizer, Trusted Advisor, and service inventory data to identify idle or overprovisioned resources, then remove or rightsize them safely
Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it

Correct answer: B

Why: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while preserving the workload service objective during the improvement.

Option review:

A: Configuration automation reduces drift, while failure exercises reveal gaps in monitoring, dependencies, and operational recovery knowledge. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while preserving the workload service objective during the improvement.

B: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while preserving the workload service objective during the improvement.

C: Cost optimization begins by measuring utilization and identifying resources whose size or existence is not justified by workload demand. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while preserving the workload service objective during the improvement.

D: Automation is most valuable for well-understood recurring actions when it remains observable, controlled, and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while preserving the workload service objective during the improvement.

Learning point: Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain. Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. In this variant, the decision also has to work while preserving the workload service objective during the improvement.

Question 8

Relecloud Systems operates a media processing platform. In a new workload design, the migration architect must enable self-healing replicas and scaling based on measured demand while preserving the workload service objective during the improvement. Which option should be recommended? The current estate includes 3 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.

Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it
Use Systems Manager or service-native configuration automation, and run controlled failure scenarios to validate recovery procedures
Use Cost and Usage Reports or equivalent detailed billing data with cost-allocation tags, Budgets, and alarms to analyze transfer charges and assign ownership
Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity

Correct answer: D

Why: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This directly addresses the primary requirement and remains appropriate while preserving the workload service objective during the improvement.

Option review:

B: Configuration automation reduces drift, while failure exercises reveal gaps in monitoring, dependencies, and operational recovery knowledge. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while preserving the workload service objective during the improvement.

C: Granular billing data, allocation tags, and alerts provide the visibility needed to explain spend and drive accountable cost remediation. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while preserving the workload service objective during the improvement.

Learning point: Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity. Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. In this variant, the decision also has to work while preserving the workload service objective during the improvement.

Question 9

A principal solutions architect at Fabrikam Health is reviewing a global web application. The business requires the team to verify that a recovery Region can actually launch the required capacity during an outage while preserving the workload service objective during the improvement. Which design most directly satisfies the requirement? The current estate includes 10 AWS accounts and active workloads in us-east-1 and us-west-2. Prefer an AWS-managed capability when it meets the requirements with less operational overhead.

Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it
Use Cost Explorer, Compute Optimizer, Trusted Advisor, and service inventory data to identify idle or overprovisioned resources, then remove or rightsize them safely
Store secrets in Secrets Manager or Parameter Store as appropriate, enforce least privilege, and review access against data sensitivity and regulatory requirements
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment

Correct answer: D

Why: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate while preserving the workload service objective during the improvement.

Option review:

A: Automation is most valuable for well-understood recurring actions when it remains observable, controlled, and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while preserving the workload service objective during the improvement.

B: Cost optimization begins by measuring utilization and identifying resources whose size or existence is not justified by workload demand. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while preserving the workload service objective during the improvement.

D: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate while preserving the workload service objective during the improvement.

Learning point: Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment. A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. In this variant, the decision also has to work while preserving the workload service objective during the improvement.

Question 10

Which solution is the strongest match for the following professional-level architecture requirement: find and remove a single NAT instance, database node, or appliance that can fail the whole workload with a staged validation path before full rollout? The current estate includes 17 AWS accounts and active workloads in us-east-1 and eu-west-1. The team wants the most direct architecture decision for this requirement.

Analyze the stable post-rightsizing usage baseline, then purchase the commitment model that matches flexibility and term requirements
Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Use Systems Manager Patch Manager or managed-service patching and policy-based backup services with compliance reporting and restore validation
Use centralized CloudWatch observability with actionable alarms and event-driven or Systems Manager automation for known remediation paths

Correct answer: B

Option review:

A: Commitments are most effective after rightsizing and when the organization understands which usage is predictably sustained. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of with a staged validation path before full rollout.

C: Patching and backups need defined schedules, scope, compliance evidence, isolation, and testing to be dependable security controls. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of with a staged validation path before full rollout.

D: Monitoring should produce useful signals and, where safe, trigger repeatable remediation instead of relying on manual observation of every component. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of with a staged validation path before full rollout.

Question 11

An architecture board at Northwind Media asks the enterprise architect to enable self-healing replicas and scaling based on measured demand with a staged validation path before full rollout for a analytics pipeline. Which recommendation is most appropriate? The current estate includes 24 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. The design must preserve security and auditability while meeting the stated objective.

Benchmark candidate instance families or scaling designs under representative load, then rightsize using observed CPU, memory, network, and storage characteristics
Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it
Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity
Perform a structured Well-Architected-style review using operational telemetry, security findings, and reliability evidence, then prioritize risks by business impact

Correct answer: C

Option review:

A: Rightsizing and high-performance compute choices should be validated against real workload characteristics and performance objectives. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of with a staged validation path before full rollout.

B: Automation is most valuable for well-understood recurring actions when it remains observable, controlled, and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of with a staged validation path before full rollout.

C: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This directly addresses the primary requirement and remains appropriate with a staged validation path before full rollout.

D: Continuous improvement is most effective when recommendations are grounded in measurable risk and workload evidence across multiple architectural dimensions. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of with a staged validation path before full rollout.

Question 12

For a media processing platform at Coho Financial, a migration wave planning session identifies one priority: verify that a recovery Region can actually launch the required capacity during an outage with a staged validation path before full rollout. Which AWS design should the team choose? The current estate includes 31 AWS accounts and active workloads in eu-west-1 and eu-central-1. Select the option that satisfies the requirement with the fewest unnecessary moving parts.

Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment
Adopt a deployment strategy with health checks, progressive exposure, and automated rollback that matches the application and capacity constraints
Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it
Use Systems Manager or service-native configuration automation, and run controlled failure scenarios to validate recovery procedures

Correct answer: A

Option review:

A: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate with a staged validation path before full rollout.

B: Deployment improvements should reduce blast radius and make unhealthy releases detectable and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of with a staged validation path before full rollout.

C: Automation is most valuable for well-understood recurring actions when it remains observable, controlled, and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of with a staged validation path before full rollout.

D: Configuration automation reduces drift, while failure exercises reveal gaps in monitoring, dependencies, and operational recovery knowledge. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of with a staged validation path before full rollout.

Question 13

Lamna Healthcare has already validated the surrounding application components. The remaining architecture requirement for its global web application is to find and remove a single NAT instance, database node, or appliance that can fail the whole workload while reducing repetitive manual operations. Which option is best? The current estate includes 38 AWS accounts and active workloads in us-east-1 and us-west-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Define measurable KPIs/SLOs, instrument the relevant components, and use CloudWatch or service metrics to isolate the actual bottleneck before changing architecture
Use centralized CloudWatch observability with actionable alarms and event-driven or Systems Manager automation for known remediation paths
Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it

Correct answer: C

Option review:

A: Performance work should start with measurable objectives and evidence so remediation targets the limiting component rather than the most visible one. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while reducing repetitive manual operations.

B: Monitoring should produce useful signals and, where safe, trigger repeatable remediation instead of relying on manual observation of every component. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while reducing repetitive manual operations.

C: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while reducing repetitive manual operations.

Question 14

While conducting a security design review, the cloud platform architect at Fourth Coffee needs to enable self-healing replicas and scaling based on measured demand while reducing repetitive manual operations. Which architecture decision best matches the stated constraints? The current estate includes 45 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity
Perform a structured Well-Architected-style review using operational telemetry, security findings, and reliability evidence, then prioritize risks by business impact
Test changes against performance and cost objectives using representative traffic, then adopt only changes that preserve required service levels
Use Systems Manager Patch Manager or managed-service patching and policy-based backup services with compliance reporting and restore validation

Correct answer: A

Option review:

A: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This directly addresses the primary requirement and remains appropriate while reducing repetitive manual operations.

C: Optimization should be validated against the workload objectives so savings or speed improvements do not create new reliability or performance problems. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while reducing repetitive manual operations.

D: Patching and backups need defined schedules, scope, compliance evidence, isolation, and testing to be dependable security controls. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while reducing repetitive manual operations.

Question 15

Which AWS architecture principle or service combination best addresses this requirement for Consolidated Messenger: verify that a recovery Region can actually launch the required capacity during an outage while reducing repetitive manual operations? The current estate includes 5 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. Prefer an AWS-managed capability when it meets the requirements with less operational overhead.

Use the AWS global delivery or managed service that matches the workload protocol and access pattern, such as CloudFront for cacheable content or Global Accelerator for network-path optimization
Use CloudTrail and AWS security/configuration services for traceability and findings, with AWS Config/EventBridge/automation for controlled remediation
Store secrets in Secrets Manager or Parameter Store as appropriate, enforce least privilege, and review access against data sensitivity and regulatory requirements
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment

Correct answer: D

Option review:

A: AWS global and managed services can improve latency and reduce operational burden when selected for the application protocol and caching or routing model. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while reducing repetitive manual operations.

B: Traceability, centralized findings, and safe automation help teams detect policy drift and reduce time to remediate recurring security issues. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while reducing repetitive manual operations.

Question 16

Litware Manufacturing operates a media processing platform. In a production readiness review, the migration architect must find and remove a single NAT instance, database node, or appliance that can fail the whole workload while retaining AWS-native traceability for the change. Which option should be recommended? The current estate includes 12 AWS accounts and active workloads in eu-west-1 and eu-central-1. The team wants the most direct architecture decision for this requirement.

Use Cost Explorer, Compute Optimizer, Trusted Advisor, and service inventory data to identify idle or overprovisioned resources, then remove or rightsize them safely
Use event-driven monitoring and approved automation runbooks for repeatable remediations, with logging, guardrails, and human approval where risk requires it
Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Adopt a deployment strategy with health checks, progressive exposure, and automated rollback that matches the application and capacity constraints

Correct answer: C

Option review:

A: Cost optimization begins by measuring utilization and identifying resources whose size or existence is not justified by workload demand. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while retaining AWS-native traceability for the change.

B: Automation is most valuable for well-understood recurring actions when it remains observable, controlled, and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while retaining AWS-native traceability for the change.

D: Deployment improvements should reduce blast radius and make unhealthy releases detectable and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while retaining AWS-native traceability for the change.

Question 17

A principal solutions architect at Humongous Insurance is reviewing a global web application. The business requires the team to enable self-healing replicas and scaling based on measured demand while retaining AWS-native traceability for the change. Which design most directly satisfies the requirement? The current estate includes 19 AWS accounts and active workloads in us-east-1 and us-west-2. The design must preserve security and auditability while meeting the stated objective.

Use Systems Manager Patch Manager or managed-service patching and policy-based backup services with compliance reporting and restore validation
Adopt a deployment strategy with health checks, progressive exposure, and automated rollback that matches the application and capacity constraints
Use the AWS global delivery or managed service that matches the workload protocol and access pattern, such as CloudFront for cacheable content or Global Accelerator for network-path optimization
Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity

Correct answer: D

Option review:

A: Patching and backups need defined schedules, scope, compliance evidence, isolation, and testing to be dependable security controls. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while retaining AWS-native traceability for the change.

B: Deployment improvements should reduce blast radius and make unhealthy releases detectable and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while retaining AWS-native traceability for the change.

C: AWS global and managed services can improve latency and reduce operational burden when selected for the application protocol and caching or routing model. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while retaining AWS-native traceability for the change.

Question 18

Tailspin Logistics is changing its order-processing system as part of a hybrid connectivity redesign. Which AWS approach best enables the team to verify that a recovery Region can actually launch the required capacity during an outage while retaining AWS-native traceability for the change? The current estate includes 26 AWS accounts and active workloads in us-east-1 and eu-west-1. Select the option that satisfies the requirement with the fewest unnecessary moving parts.

Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity
Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Benchmark candidate instance families or scaling designs under representative load, then rightsize using observed CPU, memory, network, and storage characteristics
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment

Correct answer: D

Option review:

A: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while retaining AWS-native traceability for the change.

C: Rightsizing and high-performance compute choices should be validated against real workload characteristics and performance objectives. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while retaining AWS-native traceability for the change.

Question 19

An architecture board at Alpine Sports asks the enterprise architect to find and remove a single NAT instance, database node, or appliance that can fail the whole workload while prioritizing the highest-risk bottleneck first for a analytics pipeline. Which recommendation is most appropriate? The current estate includes 33 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Benchmark candidate instance families or scaling designs under representative load, then rightsize using observed CPU, memory, network, and storage characteristics
Analyze the stable post-rightsizing usage baseline, then purchase the commitment model that matches flexibility and term requirements
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment

Correct answer: A

Option review:

C: Commitments are most effective after rightsizing and when the organization understands which usage is predictably sustained. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while prioritizing the highest-risk bottleneck first.

Question 20

Adventure Works is documenting its target-state architecture. Which choice most accurately addresses the need to enable self-healing replicas and scaling based on measured demand while prioritizing the highest-risk bottleneck first? The current estate includes 40 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.

Use Systems Manager or service-native configuration automation, and run controlled failure scenarios to validate recovery procedures
Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity
Analyze the stable post-rightsizing usage baseline, then purchase the commitment model that matches flexibility and term requirements

Correct answer: C

Option review:

A: Configuration automation reduces drift, while failure exercises reveal gaps in monitoring, dependencies, and operational recovery knowledge. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while prioritizing the highest-risk bottleneck first.

B: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while prioritizing the highest-risk bottleneck first.

D: Commitments are most effective after rightsizing and when the organization understands which usage is predictably sustained. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while prioritizing the highest-risk bottleneck first.

Question 21

VanArsdel Energy has already validated the surrounding application components. The remaining architecture requirement for its global web application is to verify that a recovery Region can actually launch the required capacity during an outage while prioritizing the highest-risk bottleneck first. Which option is best? The current estate includes 47 AWS accounts and active workloads in us-east-1 and us-west-2. Prefer an AWS-managed capability when it meets the requirements with less operational overhead.

Use Cost and Usage Reports or equivalent detailed billing data with cost-allocation tags, Budgets, and alarms to analyze transfer charges and assign ownership
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment
Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity
Analyze the stable post-rightsizing usage baseline, then purchase the commitment model that matches flexibility and term requirements

Correct answer: B

Option review:

A: Granular billing data, allocation tags, and alerts provide the visibility needed to explain spend and drive accountable cost remediation. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while prioritizing the highest-risk bottleneck first.

B: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate while prioritizing the highest-risk bottleneck first.

C: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while prioritizing the highest-risk bottleneck first.

D: Commitments are most effective after rightsizing and when the organization understands which usage is predictably sustained. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while prioritizing the highest-risk bottleneck first.

Question 22

While conducting a global expansion project, the cloud platform architect at Contoso Retail needs to find and remove a single NAT instance, database node, or appliance that can fail the whole workload while keeping rollback practical if the change regresses the workload. Which architecture decision best matches the stated constraints? The current estate includes 7 AWS accounts and active workloads in us-east-1 and eu-west-1. The team wants the most direct architecture decision for this requirement.

Use Systems Manager or service-native configuration automation, and run controlled failure scenarios to validate recovery procedures
Use Cost Explorer, Compute Optimizer, Trusted Advisor, and service inventory data to identify idle or overprovisioned resources, then remove or rightsize them safely
Store secrets in Secrets Manager or Parameter Store as appropriate, enforce least privilege, and review access against data sensitivity and regulatory requirements
Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain

Correct answer: D

Why: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while keeping rollback practical if the change regresses the workload.

Option review:

A: Configuration automation reduces drift, while failure exercises reveal gaps in monitoring, dependencies, and operational recovery knowledge. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while keeping rollback practical if the change regresses the workload.

C: Secret management and least privilege reduce credential exposure and unnecessary authority, especially for regulated or sensitive workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while keeping rollback practical if the change regresses the workload.

D: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while keeping rollback practical if the change regresses the workload.

Learning point: Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain. Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. In this variant, the decision also has to work while keeping rollback practical if the change regresses the workload.

Question 23

During a multi-account governance review at Lucerne Publishing, the site reliability architect is designing a analytics pipeline. The requirement is to enable self-healing replicas and scaling based on measured demand while keeping rollback practical if the change regresses the workload. Which architecture is the best fit? The current estate includes 14 AWS accounts and active workloads in ap-southeast-1 and ap-southeast-2. The design must preserve security and auditability while meeting the stated objective.

Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity
Perform a structured Well-Architected-style review using operational telemetry, security findings, and reliability evidence, then prioritize risks by business impact
Use the AWS global delivery or managed service that matches the workload protocol and access pattern, such as CloudFront for cacheable content or Global Accelerator for network-path optimization
Use Systems Manager or service-native configuration automation, and run controlled failure scenarios to validate recovery procedures

Correct answer: A

Why: Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. This directly addresses the primary requirement and remains appropriate while keeping rollback practical if the change regresses the workload.

Option review:

C: AWS global and managed services can improve latency and reduce operational burden when selected for the application protocol and caching or routing model. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while keeping rollback practical if the change regresses the workload.

D: Configuration automation reduces drift, while failure exercises reveal gaps in monitoring, dependencies, and operational recovery knowledge. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to enable self-healing replicas and scaling based on measured demand under the additional constraint of while keeping rollback practical if the change regresses the workload.

Learning point: Use observed growth trends to add replication, load balancing, and Auto Scaling or managed elastic features that can replace failed capacity. Growth planning should combine replication and elastic scaling so the system maintains capacity and recovers automatically as demand changes. In this variant, the decision also has to work while keeping rollback practical if the change regresses the workload.

Question 24

Datum Analytics operates a media processing platform. In a migration wave planning session, the migration architect must verify that a recovery Region can actually launch the required capacity during an outage while keeping rollback practical if the change regresses the workload. Which option should be recommended? The current estate includes 21 AWS accounts and active workloads in eu-west-1 and eu-central-1. Select the option that satisfies the requirement with the fewest unnecessary moving parts.
Store secrets in Secrets Manager or Parameter Store as appropriate, enforce least privilege, and review access against data sensitivity and regulatory requirements
Use CloudTrail and AWS security/configuration services for traceability and findings, with AWS Config/EventBridge/automation for controlled remediation
Use Cost and Usage Reports or equivalent detailed billing data with cost-allocation tags, Budgets, and alarms to analyze transfer charges and assign ownership
Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment

Correct answer: D

Why: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate while keeping rollback practical if the change regresses the workload.

Option review:

A: Secret management and least privilege reduce credential exposure and unnecessary authority, especially for regulated or sensitive workloads. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while keeping rollback practical if the change regresses the workload.

C: Granular billing data, allocation tags, and alerts provide the visibility needed to explain spend and drive accountable cost remediation. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to verify that a recovery Region can actually launch the required capacity during an outage under the additional constraint of while keeping rollback practical if the change regresses the workload.

D: A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. This directly addresses the primary requirement and remains appropriate while keeping rollback practical if the change regresses the workload.

Learning point: Treat service quotas as reliability dependencies: monitor headroom, request increases early, and test recovery capacity in the target environment. A redundant design is not reliable if quotas prevent it from scaling or failing over when needed. In this variant, the decision also has to work while keeping rollback practical if the change regresses the workload.

Question 25

Following an acquisition, Wide World Importers is rationalizing its global web application. The architecture board documented two acceptance criteria: find and remove a single NAT instance, database node, or appliance that can fail the whole workload; and the solution must do so while basing the recommendation on observed utilization or telemetry. Which target-state recommendation should the principal solutions architect approve? The current estate includes 28 AWS accounts and active workloads in us-east-1 and us-west-2. Choose the option that best meets the stated constraints without introducing an unrelated redesign.

Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain
Benchmark candidate instance families or scaling designs under representative load, then rightsize using observed CPU, memory, network, and storage characteristics
Use Systems Manager Patch Manager or managed-service patching and policy-based backup services with compliance reporting and restore validation
Perform a structured Well-Architected-style review using operational telemetry, security findings, and reliability evidence, then prioritize risks by business impact

Correct answer: A

Why: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while basing the recommendation on observed utilization or telemetry.

Option review:

A: Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. This directly addresses the primary requirement and remains appropriate while basing the recommendation on observed utilization or telemetry.

B: Rightsizing and high-performance compute choices should be validated against real workload characteristics and performance objectives. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while basing the recommendation on observed utilization or telemetry.

D: Continuous improvement is most effective when recommendations are grounded in measurable risk and workload evidence across multiple architectural dimensions. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to find and remove a single NAT instance, database node, or appliance that can fail the whole workload under the additional constraint of while basing the recommendation on observed utilization or telemetry.

Learning point: Identify each required component that lacks redundancy and replace or redesign it with multi-AZ, managed HA, or redundant paths appropriate to the failure domain. Reliability improves when critical single points of failure are removed and failover mechanisms match the intended failure scope. In this variant, the decision also has to work while basing the recommendation on observed utilization or telemetry.

Question 1

Question 2

Question 3

Question 4

Question 5

Question 6

Question 7

Question 8

Question 9

Question 10

Question 11

Question 12

Question 13

Question 14

Question 15

Question 16

Question 17

Question 18

Question 19

Question 20

Question 21

Question 22

Question 23

Question 24

Question 25

Related posts: