Practice Exams:

View All

Amazon AWS Solutions Architect Professional SAP-C02 Performance Architecture Storage Compute Practice Test

Domain 2.5 • 25 original questions

This AWS SAP-C02 AWS Certified Solutions Architect – Professional practice test focuses on performance architecture storage compute databases and caching 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

An architecture board at Alpine Sports asks the site reliability architect to select storage and delivery components for a workload with high sequential throughput and globally distributed reads while minimizing ongoing operational burden for a analytics pipeline. Which recommendation is most appropriate? The current estate includes 18 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 measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Use multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms

Correct answer: C

Why: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while minimizing ongoing operational burden.

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while minimizing ongoing operational burden.

C: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

D: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while minimizing ongoing operational burden.

Learning point: Use measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics. Performance architecture should start from access patterns and measurable objectives, not from one default storage service. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 2

For a media processing platform at Adventure Works, a new workload design identifies one priority: remove chronic overprovisioning while retaining headroom for business peaks while minimizing ongoing operational burden. Which AWS design should the team choose? The current estate includes 25 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.

Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Use a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria
Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures

Correct answer: A

Why: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

Option review:

A: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

B: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while minimizing ongoing operational burden.

C: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while minimizing ongoing operational burden.

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while minimizing ongoing operational burden.

Learning point: Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics. Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 3

VanArsdel Energy has already validated the surrounding application components. The remaining architecture requirement for its global web application is to improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads while minimizing ongoing operational burden. Which option is best? The current estate includes 32 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.

Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Use a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria

Correct answer: B

Why: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while minimizing ongoing operational burden.

B: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

C: 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while minimizing ongoing operational burden.

D: 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while minimizing ongoing operational burden.

Learning point: Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements. Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 4

While conducting a global expansion project, the network architect at Contoso Retail needs to select storage and delivery components for a workload with high sequential throughput and globally distributed reads while supporting automated and repeatable deployment. Which architecture decision best matches the stated constraints? The current estate includes 39 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 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
Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions

Correct answer: A

Option review:

A: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This directly addresses the primary requirement and remains appropriate while supporting automated and repeatable deployment.

B: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while supporting automated and repeatable deployment.

C: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while supporting automated and repeatable deployment.

D: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while supporting automated and repeatable deployment.

Question 5

Which AWS architecture principle or service combination best addresses this requirement for Lucerne Publishing: remove chronic overprovisioning while retaining headroom for business peaks while supporting automated and repeatable deployment? The current estate includes 46 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 multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Use measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Use narrowly scoped security groups and network ACLs as required, and use VPC endpoints or PrivateLink for supported private service integrations

Correct answer: B

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while supporting automated and repeatable deployment.

B: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This directly addresses the primary requirement and remains appropriate while supporting automated and repeatable deployment.

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while supporting automated and repeatable deployment.

D: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while supporting automated and repeatable deployment.

Question 6

Datum Analytics operates a media processing platform. In a migration wave planning session, the cloud financial management lead must improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads while supporting automated and repeatable deployment. Which option should be recommended? The current estate includes 6 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.
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Use IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching
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:

A: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This directly addresses the primary requirement and remains appropriate while supporting automated and repeatable deployment.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while supporting automated and repeatable deployment.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while supporting automated and repeatable deployment.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while supporting automated and repeatable deployment.

Question 7

A security architect at Wide World Importers is reviewing a global web application. The business requires the team to select storage and delivery components for a workload with high sequential throughput and globally distributed reads with an explicit rollback or recovery path if the change fails. Which design most directly satisfies the requirement? The current estate includes 13 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 a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria
Select the architecture that meets the declared recovery, security, and budget objectives together, and validate those objectives with monitoring and testing
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

Correct answer: D

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of with an explicit rollback or recovery path if the change fails.

C: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of with an explicit rollback or recovery path if the change fails.

D: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This directly addresses the primary requirement and remains appropriate with an explicit rollback or recovery path if the change fails.

Question 8

Bellows University is changing its order-processing system as part of a security design review. Which AWS approach best enables the team to remove chronic overprovisioning while retaining headroom for business peaks with an explicit rollback or recovery path if the change fails? The current estate includes 20 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

Use multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement

Correct answer: B

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of with an explicit rollback or recovery path if the change fails.

B: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This directly addresses the primary requirement and remains appropriate with an explicit rollback or recovery path if the change fails.

C: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of with an explicit rollback or recovery path if the change fails.

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 can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of with an explicit rollback or recovery path if the change fails.

Question 9

An architecture board at Blue Yonder Airlines asks the site reliability architect to improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads with an explicit rollback or recovery path if the change fails for a analytics pipeline. Which recommendation is most appropriate? The current estate includes 27 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.

Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Use a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria
Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of with an explicit rollback or recovery path if the change fails.

B: 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of with an explicit rollback or recovery path if the change fails.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of with an explicit rollback or recovery path if the change fails.

D: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This directly addresses the primary requirement and remains appropriate with an explicit rollback or recovery path if the change fails.

Question 10

City Power is documenting its target-state architecture. Which choice most accurately addresses the need to select storage and delivery components for a workload with high sequential throughput and globally distributed reads without introducing an unrelated application rewrite? The current estate includes 34 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 cost and utilization data to rightsize resources, then choose Savings Plans, Reserved Instances, Spot, or On-Demand according to predictability and interruption tolerance
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

Correct answer: A

Option review:

A: Performance architecture should start from access patterns and measurable objectives, not from one default storage service. This directly addresses the primary requirement and remains appropriate without introducing an unrelated application rewrite.

B: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of without introducing an unrelated application rewrite.

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads 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 can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of without introducing an unrelated application rewrite.

Question 11

Proseware Labs has already validated the surrounding application components. The remaining architecture requirement for its global web application is to remove chronic overprovisioning while retaining headroom for business peaks without introducing an unrelated application rewrite. Which option is best? The current estate includes 41 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 measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
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 multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of without introducing an unrelated application rewrite.

B: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This directly addresses the primary requirement and remains appropriate without introducing an unrelated application rewrite.

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of without introducing an unrelated application rewrite.

D: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of without introducing an unrelated application rewrite.

Question 12

While conducting a hybrid connectivity redesign, the network architect at Southridge Video needs to improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads without introducing an unrelated application rewrite. Which architecture decision best matches the stated constraints? The current estate includes 48 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.

Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed 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

Correct answer: A

Option review:

A: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This directly addresses the primary requirement and remains appropriate without introducing an unrelated application rewrite.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of without introducing an unrelated application rewrite.

C: 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of without introducing an unrelated application rewrite.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of without introducing an unrelated application rewrite.

Question 13

During a resilience assessment at Woodgrove Bank, the enterprise architect is designing a analytics pipeline. The requirement is to select storage and delivery components for a workload with high sequential throughput and globally distributed reads while preserving least-privilege administration. Which architecture is the best fit? The current estate includes 8 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 Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
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
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

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while preserving least-privilege administration.

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while preserving least-privilege administration.

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while preserving least-privilege administration.

Question 14

Relecloud Systems operates a media processing platform. In a new workload design, the cloud financial management lead must remove chronic overprovisioning while retaining headroom for business peaks while preserving least-privilege administration. Which option should be recommended? The current estate includes 15 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.

Use S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Use cost and utilization data to rightsize resources, then choose Savings Plans, Reserved Instances, Spot, or On-Demand according to predictability and interruption tolerance
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Use elastic stateless tiers with managed queues or events, caching, replicas, and service-specific scaling to decouple bottlenecks and preserve availability

Correct answer: C

Option review:

A: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while preserving least-privilege administration.

B: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while preserving least-privilege administration.

C: Instance families provide different resource profiles; elasticity and rightsizing align capacity to workload behavior instead of static peak estimates. This directly addresses the primary requirement and remains appropriate while preserving least-privilege administration.

D: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while preserving least-privilege administration.

Question 15

A principal architect asks which AWS approach is intended to improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads while preserving least-privilege administration. What is the best answer? The current estate includes 22 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.

Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Adopt the appropriate managed AWS service and use Systems Manager or service-native automation for configuration and 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 service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions

Correct answer: A

Option review:

B: 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while preserving least-privilege administration.

D: 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while preserving least-privilege administration.

Question 16

Trey Research is changing its order-processing system as part of a global expansion project. Which AWS approach best enables the team to select storage and delivery components for a workload with high sequential throughput and globally distributed reads while keeping the design elastic as demand changes? The current estate includes 29 AWS accounts and active workloads in us-east-1 and eu-west-1. The team wants the most direct architecture decision for this requirement.

Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Use cost and utilization data to rightsize resources, then choose Savings Plans, Reserved Instances, Spot, or On-Demand according to predictability and interruption tolerance
Use elastic stateless tiers with managed queues or events, caching, replicas, and service-specific scaling to decouple bottlenecks and preserve availability
Use measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics

Correct answer: D

Option review:

A: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while keeping the design elastic as demand changes.

Question 17

An architecture board at Northwind Media asks the site reliability architect to remove chronic overprovisioning while retaining headroom for business peaks while keeping the design elastic as demand changes for a analytics pipeline. Which recommendation is most appropriate? The current estate includes 36 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 multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms
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
Use a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria

Correct answer: C

Option review:

B: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while keeping the design elastic as demand changes.

D: 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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while keeping the design elastic as demand changes.

Question 18

For a media processing platform at Coho Financial, a migration wave planning session identifies one priority: improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads while keeping the design elastic as demand changes. Which AWS design should the team choose? The current estate includes 43 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 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
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements
Use a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while keeping the design elastic as demand changes.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while keeping the design elastic as demand changes.

C: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This directly addresses the primary requirement and remains appropriate while keeping the design elastic as demand changes.

Question 19

Lamna Healthcare has already validated the surrounding application components. The remaining architecture requirement for its global web application is to select storage and delivery components for a workload with high sequential throughput and globally distributed reads while using managed services when they satisfy the requirement. Which option is best? The current estate includes 3 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 measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Use multi-AZ or multi-Region deployment as required, with health-aware Route 53 or other routing and managed failover mechanisms
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 a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria

Correct answer: A

Option review:

B: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while using managed services when they satisfy the requirement.

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while using managed services when they satisfy the requirement.

D: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while using managed services when they satisfy the requirement.

Question 20

Which solution is the strongest match for the following professional-level architecture requirement: remove chronic overprovisioning while retaining headroom for business peaks while using managed services when they satisfy the requirement? The current estate includes 10 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
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Select the architecture that meets the declared recovery, security, and budget objectives together, and validate those objectives with monitoring and testing
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while using managed services when they satisfy the requirement.

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 remove chronic overprovisioning while retaining headroom for business peaks 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 can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while using managed services when they satisfy the requirement.

Question 21

During a modernization initiative at Consolidated Messenger, the enterprise architect is designing a analytics pipeline. The requirement is to improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads while using managed services when they satisfy the requirement. Which architecture is the best fit? The current estate includes 17 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 cost and utilization data to rightsize resources, then choose Savings Plans, Reserved Instances, Spot, or On-Demand according to predictability and interruption tolerance
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
Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures

Correct answer: C

Option review:

A: 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while using managed services when they satisfy the requirement.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while using managed services when they satisfy the requirement.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while using managed services when they satisfy the requirement.

Question 22

Litware Manufacturing operates a media processing platform. In a production readiness review, the cloud financial management lead must select storage and delivery components for a workload with high sequential throughput and globally distributed reads while keeping observability sufficient to validate the result. Which option should be recommended? The current estate includes 24 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
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
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

Correct answer: A

Option review:

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while keeping observability sufficient to validate the result.

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while keeping observability sufficient to validate the result.

D: 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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while keeping observability sufficient to validate the result.

Question 23

A security architect at Humongous Insurance is reviewing a global web application. The business requires the team to remove chronic overprovisioning while retaining headroom for business peaks while keeping observability sufficient to validate the result. Which design most directly satisfies the requirement? The current estate includes 31 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 IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching
Use S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Adopt the appropriate managed AWS service and use Systems Manager or service-native automation for configuration and patching

Correct answer: C

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while keeping observability sufficient to validate the result.

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while keeping observability sufficient to validate the result.

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 remove chronic overprovisioning while retaining headroom for business peaks under the additional constraint of while keeping observability sufficient to validate the result.

Question 24

Tailspin Logistics is changing its order-processing system as part of a hybrid connectivity redesign. Which AWS approach best enables the team to improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads while keeping observability sufficient to validate the result? The current estate includes 38 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 S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Use elastic stateless tiers with managed queues or events, caching, replicas, and service-specific scaling to decouple bottlenecks and preserve availability
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements

Correct answer: D

Option review:

A: 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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while keeping observability sufficient to validate the result.

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 improve performance with caching, buffering, and read replicas where the workload permits eventual or replicated reads under the additional constraint of while keeping observability sufficient to validate the result.

D: Purpose-built databases and caching patterns improve performance when selected for the actual data model, access pattern, and consistency requirements. This directly addresses the primary requirement and remains appropriate while keeping observability sufficient to validate the result.

Question 25

Following an acquisition, Alpine Sports is rationalizing its analytics pipeline. The architecture board documented two acceptance criteria: select storage and delivery components for a workload with high sequential throughput and globally distributed reads; and the solution must do so while avoiding a single manual recovery dependency. Which target-state recommendation should the site reliability architect approve? The current estate includes 45 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 measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
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
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads under the additional constraint of while avoiding a single manual recovery dependency.

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 select storage and delivery components for a workload with high sequential throughput and globally distributed reads 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: