Practice Exams:

View All

Amazon AWS Solutions Architect Professional SAP-C02 Highly Available Multi-AZ Designs Loose Practice Test

Domain 2.4 • 25 original questions

This AWS SAP-C02 AWS Certified Solutions Architect – Professional practice test focuses on highly available multi-az designs loose coupling and dns 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

Fourth Coffee is changing its payment platform as part of a new workload design. Which AWS approach best enables the team to design application and database failover so a component outage does not require manual rebuilds while minimizing ongoing operational burden? The current estate includes 13 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.

Use IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching
Use KMS/service-native encryption and TLS for data protection, with AWS WAF, Shield, and managed security services as appropriate for the threat model
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover
Use measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics

Correct answer: C

Why: Reliability depends on matching redundancy to the required failure domain and using managed failover where it reduces operational risk. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

Option review:

A: Temporary scoped credentials reduce secret exposure, and automated patch workflows improve compliance without expanding application privileges. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while minimizing ongoing operational burden.

B: Encryption protects confidentiality, while AWS WAF, Shield, and related managed services mitigate web and network attacks at scale. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while minimizing ongoing operational burden.

C: Reliability depends on matching redundancy to the required failure domain and using managed failover where it reduces operational risk. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

D: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while minimizing ongoing operational burden.

Learning point: Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover. Reliability depends on matching redundancy to the required failure domain and using managed failover where it reduces operational risk. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 2

An architecture board at Consolidated Messenger asks the principal solutions architect to absorb burst traffic without tightly coupling request producers to slow downstream workers while minimizing ongoing operational burden for a IoT ingestion service. Which recommendation is most appropriate? The current estate includes 20 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.

Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Use KMS/service-native encryption and TLS for data protection, with AWS WAF, Shield, and managed security services as appropriate for the threat model

Correct answer: C

Why: Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

Option review:

A: Capacity planning must include service quotas, and Route 53 routing policies should be selected based on health, latency, geography, or other stated routing goals. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while minimizing ongoing operational burden.

B: Data-transfer architecture can materially affect cost; expenditure controls and service selection should be designed with traffic flows and business value in mind. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while minimizing ongoing operational burden.

C: Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

D: Encryption protects confidentiality, while AWS WAF, Shield, and related managed services mitigate web and network attacks at scale. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while minimizing ongoing operational burden.

Learning point: Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components. Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 3

For a batch settlement service at Litware Manufacturing, a global expansion project identifies one priority: choose a DNS routing policy that aligns traffic placement with a global availability design while minimizing ongoing operational burden. Which AWS design should the team choose? The current estate includes 27 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements

Correct answer: C

Why: Capacity planning must include service quotas, and Route 53 routing policies should be selected based on health, latency, geography, or other stated routing goals. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

Option review:

A: Versioned infrastructure and automated deployment pipelines reduce drift and make failed changes repeatable and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while minimizing ongoing operational burden.

B: Replication supports continuity, backups protect against logical loss, and monitoring/automation reduce detection and recovery time for common failures. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while minimizing ongoing operational burden.

C: Capacity planning must include service quotas, and Route 53 routing policies should be selected based on health, latency, geography, or other stated routing goals. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

D: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while minimizing ongoing operational burden.

Learning point: Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement. Capacity planning must include service quotas, and Route 53 routing policies should be selected based on health, latency, geography, or other stated routing goals. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 4

Humongous Insurance has already validated the surrounding application components. The remaining architecture requirement for its machine learning inference service is to design application and database failover so a component outage does not require manual rebuilds while supporting automated and repeatable deployment. Which option is best? The current estate includes 34 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.

Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover
Use cost and utilization data to rightsize resources, then choose Savings Plans, Reserved Instances, Spot, or On-Demand according to predictability and interruption tolerance
Adopt the appropriate managed AWS service and use Systems Manager or service-native automation for configuration and patching

Correct answer: B

Option review:

A: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while supporting automated and repeatable deployment.

B: Reliability depends on matching redundancy to the required failure domain and using managed failover where it reduces operational risk. This directly addresses the primary requirement and remains appropriate while supporting automated and repeatable deployment.

C: Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while supporting automated and repeatable deployment.

D: Managed services and Systems Manager can reduce custom infrastructure administration while keeping configuration and operational tasks repeatable and auditable. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while supporting automated and repeatable deployment.

Question 5

Which solution is the strongest match for the following professional-level architecture requirement: absorb burst traffic without tightly coupling request producers to slow downstream workers while supporting automated and repeatable deployment? The current estate includes 41 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 measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Adopt the appropriate managed AWS service and use Systems Manager or service-native automation for configuration and patching
Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures

Correct answer: B

Option review:

A: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while supporting automated and repeatable deployment.

B: Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. This directly addresses the primary requirement and remains appropriate while supporting automated and repeatable deployment.

C: Managed services and Systems Manager can reduce custom infrastructure administration while keeping configuration and operational tasks repeatable and auditable. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while supporting automated and repeatable deployment.

D: A continuity design is incomplete until failover and restore procedures are tested and measured against business recovery objectives. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while supporting automated and repeatable deployment.

Question 6

During a post-incident architecture review at Alpine Sports, the security architect is designing a IoT ingestion service. The requirement is to choose a DNS routing policy that aligns traffic placement with a global availability design while supporting automated and repeatable deployment. Which architecture is the best fit? The current estate includes 48 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 multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement

Correct answer: D

Option review:

A: AWS global and regional infrastructure plus health-aware routing can preserve application availability when a location or component fails. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while supporting automated and repeatable deployment.

B: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while supporting automated and repeatable deployment.

C: Data-transfer architecture can materially affect cost; expenditure controls and service selection should be designed with traffic flows and business value in mind. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while supporting automated and repeatable deployment.

D: Capacity planning must include service quotas, and Route 53 routing policies should be selected based on health, latency, geography, or other stated routing goals. This directly addresses the primary requirement and remains appropriate while supporting automated and repeatable deployment.

Question 7

Adventure Works operates a batch settlement service. In a security design review, the cloud platform architect must design application and database failover so a component outage does not require manual rebuilds with an explicit rollback or recovery path if the change fails. Which option should be recommended? The current estate includes 8 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 a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover
Select the architecture that meets the declared recovery, security, and budget objectives together, and validate those objectives with monitoring and testing

Correct answer: C

Option review:

A: Professional architectures should treat upgrades as controlled changes with measurable entry, success, and rollback conditions. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of with an explicit rollback or recovery path if the change fails.

B: Replication supports continuity, backups protect against logical loss, and monitoring/automation reduce detection and recovery time for common failures. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of with an explicit rollback or recovery path if the change fails.

D: AWS Well-Architected decisions should balance reliability, security, operational excellence, performance efficiency, and cost instead of optimizing a single pillar in isolation. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of with an explicit rollback or recovery path if the change fails.

Question 8

A site reliability architect at VanArsdel Energy is reviewing a machine learning inference service. The business requires the team to absorb burst traffic without tightly coupling request producers to slow downstream workers with an explicit rollback or recovery path if the change fails. Which design most directly satisfies the requirement? The current estate includes 15 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.

Adopt the appropriate managed AWS service and use Systems Manager or service-native automation for configuration and patching
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures
Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback

Correct answer: B

Option review:

A: Managed services and Systems Manager can reduce custom infrastructure administration while keeping configuration and operational tasks repeatable and auditable. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of with an explicit rollback or recovery path if the change fails.

B: Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. This directly addresses the primary requirement and remains appropriate with an explicit rollback or recovery path if the change fails.

C: A continuity design is incomplete until failover and restore procedures are tested and measured against business recovery objectives. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of with an explicit rollback or recovery path if the change fails.

D: Versioned infrastructure and automated deployment pipelines reduce drift and make failed changes repeatable and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of with an explicit rollback or recovery path if the change fails.

Question 9

Contoso Retail is changing its payment platform as part of a production readiness review. Which AWS approach best enables the team to choose a DNS routing policy that aligns traffic placement with a global availability design with an explicit rollback or recovery path if the change fails? The current estate includes 22 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.

Use IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement
Use measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements

Correct answer: B

Option review:

A: Temporary scoped credentials reduce secret exposure, and automated patch workflows improve compliance without expanding application privileges. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of with an explicit rollback or recovery path if the change fails.

B: Capacity planning must include service quotas, and Route 53 routing policies should be selected based on health, latency, geography, or other stated routing goals. This directly addresses the primary requirement and remains appropriate with an explicit rollback or recovery path if the change fails.

C: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of with an explicit rollback or recovery path if the change fails.

Question 10

Which AWS architecture principle or service combination best addresses this requirement for Lucerne Publishing: design application and database failover so a component outage does not require manual rebuilds without introducing an unrelated application rewrite? The current estate includes 29 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 managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover
Use narrowly scoped security groups and network ACLs as required, and use VPC endpoints or PrivateLink for supported private service integrations
Select the architecture that meets the declared recovery, security, and budget objectives together, and validate those objectives with monitoring and testing
Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership

Correct answer: A

Option review:

A: Reliability depends on matching redundancy to the required failure domain and using managed failover where it reduces operational risk. This directly addresses the primary requirement and remains appropriate without introducing an unrelated application rewrite.

B: Security groups and NACLs control network flows at different layers, while VPC endpoints avoid unnecessary public paths to supported services. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of without introducing an unrelated application rewrite.

C: AWS Well-Architected decisions should balance reliability, security, operational excellence, performance efficiency, and cost instead of optimizing a single pillar in isolation. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of without introducing an unrelated application rewrite.

D: Managed-service adoption is valuable when it reduces undifferentiated operations without violating control, performance, or portability requirements. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of without introducing an unrelated application rewrite.

Question 11

For a batch settlement service at A. Datum Analytics, a hybrid connectivity redesign identifies one priority: absorb burst traffic without tightly coupling request producers to slow downstream workers without introducing an unrelated application rewrite. Which AWS design should the team choose? The current estate includes 36 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 multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms
Use elastic stateless tiers with managed queues or events, caching, replicas, and service-specific scaling to decouple bottlenecks and preserve availability
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components

Correct answer: D

Option review:

A: AWS global and regional infrastructure plus health-aware routing can preserve application availability when a location or component fails. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of without introducing an unrelated application rewrite.

B: Professional solution design combines multiple patterns so capacity, failure, and latency are isolated rather than propagated across the stack. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of without introducing an unrelated application rewrite.

C: Replication supports continuity, backups protect against logical loss, and monitoring/automation reduce detection and recovery time for common failures. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of without introducing an unrelated application rewrite.

D: Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. This directly addresses the primary requirement and remains appropriate without introducing an unrelated application rewrite.

Question 12

Wide World Importers has already validated the surrounding application components. The remaining architecture requirement for its machine learning inference service is to choose a DNS routing policy that aligns traffic placement with a global availability design without introducing an unrelated application rewrite. Which option is best? The current estate includes 43 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 infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Select the architecture that meets the declared recovery, security, and budget objectives together, and validate those objectives with monitoring and testing
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement

Correct answer: D

Option review:

B: Managed-service adoption is valuable when it reduces undifferentiated operations without violating control, performance, or portability requirements. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of without introducing an unrelated application rewrite.

C: AWS Well-Architected decisions should balance reliability, security, operational excellence, performance efficiency, and cost instead of optimizing a single pillar in isolation. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of without introducing an unrelated application rewrite.

D: Capacity planning must include service quotas, and Route 53 routing policies should be selected based on health, latency, geography, or other stated routing goals. This directly addresses the primary requirement and remains appropriate without introducing an unrelated application rewrite.

Question 13

While conducting a new workload design, the cloud financial management lead at Bellows University needs to design application and database failover so a component outage does not require manual rebuilds while preserving least-privilege administration. Which architecture decision best matches the stated constraints? The current estate includes 3 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.

Adopt the appropriate managed AWS service and use Systems Manager or service-native automation for configuration and patching
Use S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements

Correct answer: C

Option review:

A: Managed services and Systems Manager can reduce custom infrastructure administration while keeping configuration and operational tasks repeatable and auditable. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while preserving least-privilege administration.

B: Storage tiering reduces cost when lifecycle transitions match real access patterns, minimum-storage-duration rules, and retrieval expectations. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while preserving least-privilege administration.

D: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while preserving least-privilege administration.

Question 14

During a cost optimization workshop at Blue Yonder Airlines, the security architect is designing a IoT ingestion service. The requirement is to absorb burst traffic without tightly coupling request producers to slow downstream workers while preserving least-privilege administration. Which architecture is the best fit? The current estate includes 10 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.

Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Use IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching
Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback

Correct answer: A

Option review:

A: Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. This directly addresses the primary requirement and remains appropriate while preserving least-privilege administration.

B: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while preserving least-privilege administration.

C: Temporary scoped credentials reduce secret exposure, and automated patch workflows improve compliance without expanding application privileges. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while preserving least-privilege administration.

Question 15

City Power is documenting its target-state architecture. Which choice most accurately addresses the need to choose a DNS routing policy that aligns traffic placement with a global availability design while preserving least-privilege administration? The current estate includes 17 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement
Use KMS/service-native encryption and TLS for data protection, with AWS WAF, Shield, and managed security services as appropriate for the threat model
Use cost and utilization data to rightsize resources, then choose Savings Plans, Reserved Instances, Spot, or On-Demand according to predictability and interruption tolerance

Correct answer: B

Option review:

A: Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while preserving least-privilege administration.

C: Encryption protects confidentiality, while AWS WAF, Shield, and related managed services mitigate web and network attacks at scale. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while preserving least-privilege administration.

D: Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while preserving least-privilege administration.

Question 16

A site reliability architect at Proseware Labs is reviewing a machine learning inference service. The business requires the team to design application and database failover so a component outage does not require manual rebuilds while keeping the design elastic as demand changes. Which design most directly satisfies the requirement? The current estate includes 24 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 managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover
Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures
Use elastic stateless tiers with managed queues or events, caching, replicas, and service-specific scaling to decouple bottlenecks and preserve availability
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls

Correct answer: A

Option review:

B: A continuity design is incomplete until failover and restore procedures are tested and measured against business recovery objectives. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while keeping the design elastic as demand changes.

C: Professional solution design combines multiple patterns so capacity, failure, and latency are isolated rather than propagated across the stack. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while keeping the design elastic as demand changes.

D: Data-transfer architecture can materially affect cost; expenditure controls and service selection should be designed with traffic flows and business value in mind. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while keeping the design elastic as demand changes.

Question 17

Southridge Video is changing its payment platform as part of a migration wave planning session. Which AWS approach best enables the team to absorb burst traffic without tightly coupling request producers to slow downstream workers while keeping the design elastic as demand changes? The current estate includes 31 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 infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements

Correct answer: C

Option review:

A: Versioned infrastructure and automated deployment pipelines reduce drift and make failed changes repeatable and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while keeping the design elastic as demand changes.

D: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while keeping the design elastic as demand changes.

Question 18

An architecture board at Woodgrove Bank asks the principal solutions architect to choose a DNS routing policy that aligns traffic placement with a global availability design while keeping the design elastic as demand changes for a IoT ingestion service. Which recommendation is most appropriate? The current estate includes 38 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 a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement
Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback

Correct answer: C

Option review:

A: Professional architectures should treat upgrades as controlled changes with measurable entry, success, and rollback conditions. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while keeping the design elastic as demand changes.

B: Reliability depends on matching redundancy to the required failure domain and using managed failover where it reduces operational risk. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while keeping the design elastic as demand changes.

D: Versioned infrastructure and automated deployment pipelines reduce drift and make failed changes repeatable and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while keeping the design elastic as demand changes.

Question 19

For a batch settlement service at Relecloud Systems, a security design review identifies one priority: design application and database failover so a component outage does not require manual rebuilds while using managed services when they satisfy the requirement. Which AWS design should the team choose? The current estate includes 45 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.

Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Use narrowly scoped security groups and network ACLs as required, and use VPC endpoints or PrivateLink for supported private service integrations
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover

Correct answer: D

Option review:

A: A continuity design is incomplete until failover and restore procedures are tested and measured against business recovery objectives. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while using managed services when they satisfy the requirement.

B: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while using managed services when they satisfy the requirement.

C: Security groups and NACLs control network flows at different layers, while VPC endpoints avoid unnecessary public paths to supported services. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while using managed services when they satisfy the requirement.

D: Reliability depends on matching redundancy to the required failure domain and using managed failover where it reduces operational risk. This directly addresses the primary requirement and remains appropriate while using managed services when they satisfy the requirement.

Question 20

A principal architect asks which AWS approach is intended to absorb burst traffic without tightly coupling request producers to slow downstream workers while using managed services when they satisfy the requirement. What is the best answer? The current estate includes 5 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 KMS/service-native encryption and TLS for data protection, with AWS WAF, Shield, and managed security services as appropriate for the threat model
Select the architecture that meets the declared recovery, security, and budget objectives together, and validate those objectives with monitoring and testing
Use IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components

Correct answer: D

Option review:

A: Encryption protects confidentiality, while AWS WAF, Shield, and related managed services mitigate web and network attacks at scale. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while using managed services when they satisfy the requirement.

B: AWS Well-Architected decisions should balance reliability, security, operational excellence, performance efficiency, and cost instead of optimizing a single pillar in isolation. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while using managed services when they satisfy the requirement.

D: Elastic scaling and asynchronous decoupling reduce cascading failures and allow components to recover or scale independently. This directly addresses the primary requirement and remains appropriate while using managed services when they satisfy the requirement.

Question 21

While conducting a production readiness review, the cloud financial management lead at Trey Research needs to choose a DNS routing policy that aligns traffic placement with a global availability design while using managed services when they satisfy the requirement. Which architecture decision best matches the stated constraints? The current estate includes 12 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.

Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Use measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement

Correct answer: D

Option review:

B: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while using managed services when they satisfy the requirement.

C: Versioned infrastructure and automated deployment pipelines reduce drift and make failed changes repeatable and reversible. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while using managed services when they satisfy the requirement.

Question 22

During a architecture review at Northwind Media, the security architect is designing a IoT ingestion service. The requirement is to design application and database failover so a component outage does not require manual rebuilds while keeping observability sufficient to validate the result. Which architecture is the best fit? The current estate includes 19 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.

Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures
Use elastic stateless tiers with managed queues or events, caching, replicas, and service-specific scaling to decouple bottlenecks and preserve availability
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover

Correct answer: D

Option review:

A: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while keeping observability sufficient to validate the result.

D: Reliability depends on matching redundancy to the required failure domain and using managed failover where it reduces operational risk. This directly addresses the primary requirement and remains appropriate while keeping observability sufficient to validate the result.

Question 23

Coho Financial operates a batch settlement service. In a hybrid connectivity redesign, the cloud platform architect must absorb burst traffic without tightly coupling request producers to slow downstream workers while keeping observability sufficient to validate the result. Which option should be recommended? The current estate includes 26 AWS accounts and active workloads in us-east-1 and eu-west-1. The team wants the most direct architecture decision for this requirement.

Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics

Correct answer: C

Option review:

D: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to absorb burst traffic without tightly coupling request producers to slow downstream workers under the additional constraint of while keeping observability sufficient to validate the result.

Question 24

A site reliability architect at Lamna Healthcare is reviewing a machine learning inference service. The business requires the team to choose a DNS routing policy that aligns traffic placement with a global availability design while keeping observability sufficient to validate the result. Which design most directly satisfies the requirement? The current estate includes 33 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 infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions
Use multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement

Correct answer: D

Option review:

C: AWS global and regional infrastructure plus health-aware routing can preserve application availability when a location or component fails. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a DNS routing policy that aligns traffic placement with a global availability design under the additional constraint of while keeping observability sufficient to validate the result.

Question 25

Following an acquisition, Fourth Coffee is rationalizing its payment platform. The architecture board documented two acceptance criteria: design application and database failover so a component outage does not require manual rebuilds; and the solution must do so while avoiding a single manual recovery dependency. Which target-state recommendation should the migration architect approve? The current estate includes 40 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.

Use multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms
Use elastic stateless tiers with managed queues or events, caching, replicas, and service-specific scaling to decouple bottlenecks and preserve availability
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover

Correct answer: D

Option review:

A: AWS global and regional infrastructure plus health-aware routing can preserve application availability when a location or component fails. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while avoiding a single manual recovery dependency.

B: Professional solution design combines multiple patterns so capacity, failure, and latency are isolated rather than propagated across the stack. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while avoiding a single manual recovery dependency.

C: Replication supports continuity, backups protect against logical loss, and monitoring/automation reduce detection and recovery time for common failures. This can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to design application and database failover so a component outage does not require manual rebuilds under the additional constraint of while avoiding a single manual recovery dependency.

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: