Practice Exams:

View All

Amazon AWS Solutions Architect Professional SAP-C02 Solution Cost Optimization Pricing Storage Practice Test

Domain 2.6 • 25 original questions

This AWS SAP-C02 AWS Certified Solutions Architect – Professional practice test focuses on solution cost optimization pricing storage tiering and transfer 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

For a healthcare records application at A. Datum Analytics, a hybrid connectivity redesign identifies one priority: choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand while minimizing ongoing operational burden. Which AWS design should the team choose? The current estate includes 23 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their 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
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics

Correct answer: A

Why: Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

Option review:

A: Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while minimizing ongoing operational burden.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while minimizing ongoing operational burden.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while minimizing ongoing operational burden.

Learning point: Use cost and utilization data to rightsize resources, then choose Savings Plans, Reserved Instances, Spot, or On-Demand according to predictability and interruption tolerance. Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 2

Wide World Importers has already validated the surrounding application components. The remaining architecture requirement for its enterprise ERP system is to avoid keeping long-lived infrequently used data in the highest-cost access tier while minimizing ongoing operational burden. Which option is best? The current estate includes 30 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 S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Use measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Select the architecture that meets the declared recovery, security, and budget objectives together, and validate those objectives with monitoring and testing
Use narrowly scoped security groups and network ACLs as required, and use VPC endpoints or PrivateLink for supported private service integrations

Correct answer: A

Why: Storage tiering reduces cost when lifecycle transitions match real access patterns, minimum-storage-duration rules, and retrieval expectations. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

Option review:

A: Storage tiering reduces cost when lifecycle transitions match real access patterns, minimum-storage-duration rules, and retrieval expectations. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while minimizing ongoing operational burden.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while minimizing ongoing operational burden.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while minimizing ongoing operational burden.

Learning point: Use S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements. Storage tiering reduces cost when lifecycle transitions match real access patterns, minimum-storage-duration rules, and retrieval expectations. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 3

While conducting a new workload design, the migration architect at Bellows University needs to model cross-AZ and cross-Region transfer charges before selecting a global architecture while minimizing ongoing operational burden. Which architecture decision best matches the stated constraints? The current estate includes 37 AWS accounts and active workloads in eu-west-1 and eu-central-1. The team wants the most direct architecture decision for this requirement.

Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
Use a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria
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

Correct answer: A

Why: Data-transfer architecture can materially affect cost; expenditure controls and service selection should be designed with traffic flows and business value in mind. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

Option review:

A: Data-transfer architecture can materially affect cost; expenditure controls and service selection should be designed with traffic flows and business value in mind. This directly addresses the primary requirement and remains appropriate while minimizing ongoing operational burden.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture 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 can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while minimizing ongoing operational burden.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while minimizing ongoing operational burden.

Learning point: Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls. Data-transfer architecture can materially affect cost; expenditure controls and service selection should be designed with traffic flows and business value in mind. In this variant, the decision also has to work while minimizing ongoing operational burden.

Question 4

During a cost optimization workshop at Blue Yonder Airlines, the principal solutions architect is designing a customer-facing API. The requirement is to choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand while supporting automated and repeatable deployment. Which architecture is the best fit? The current estate includes 44 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.

Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed 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
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: 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 commitment model for a predictable baseline and preserve on-demand flexibility for variable demand 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 can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of 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 directly addresses the primary requirement and remains appropriate while supporting automated and repeatable deployment.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while supporting automated and repeatable deployment.

Question 5

City Power is documenting its target-state architecture. Which choice most accurately addresses the need to avoid keeping long-lived infrequently used data in the highest-cost access tier while supporting automated and repeatable deployment? The current estate includes 4 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
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 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: A

Option review:

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while supporting automated and repeatable deployment.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier 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 can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while supporting automated and repeatable deployment.

Question 6

A enterprise architect at Proseware Labs is reviewing a enterprise ERP system. The business requires the team to model cross-AZ and cross-Region transfer charges before selecting a global architecture while supporting automated and repeatable deployment. Which design most directly satisfies the requirement? The current estate includes 11 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 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
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
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: 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 model cross-AZ and cross-Region transfer charges before selecting a global architecture 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 model cross-AZ and cross-Region transfer charges before selecting a global architecture 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 directly addresses the primary requirement and remains appropriate while supporting automated and repeatable deployment.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while supporting automated and repeatable deployment.

Question 7

Southridge Video is changing its data lake platform as part of a migration wave planning session. Which AWS approach best enables the team to choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand with an explicit rollback or recovery path if the change fails? The current estate includes 18 AWS accounts and active workloads in eu-west-1 and eu-central-1. Assume all unspecified components already meet their requirements.

Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures
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
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions

Correct answer: C

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of with an explicit rollback or recovery path if the change fails.

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 commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of with an explicit rollback or recovery path if the change fails.

C: Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. This directly addresses the primary requirement and remains appropriate with an explicit rollback or recovery path if the change fails.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of with an explicit rollback or recovery path if the change fails.

Question 8

An architecture board at Woodgrove Bank asks the security architect to avoid keeping long-lived infrequently used data in the highest-cost access tier with an explicit rollback or recovery path if the change fails for a customer-facing API. Which recommendation is most appropriate? The current estate includes 25 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 Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
Use S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Use narrowly scoped security groups and network ACLs as required, and use VPC endpoints or PrivateLink for supported private service integrations
Use a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of with an explicit rollback or recovery path if the change fails.

B: Storage tiering reduces cost when lifecycle transitions match real access patterns, minimum-storage-duration rules, and retrieval expectations. This directly addresses the primary requirement and remains appropriate with an explicit rollback or recovery path if the change fails.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of with an explicit rollback or recovery path if the change fails.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of with an explicit rollback or recovery path if the change fails.

Question 9

For a healthcare records application at Relecloud Systems, a security design review identifies one priority: model cross-AZ and cross-Region transfer charges before selecting a global architecture with an explicit rollback or recovery path if the change fails. Which AWS design should the team choose? The current estate includes 32 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
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
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

Correct answer: B

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of with an explicit rollback or recovery path if the change fails.

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 directly addresses the primary requirement and remains appropriate with an explicit rollback or recovery path if the change fails.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of with an explicit rollback or recovery path if the change fails.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of with an explicit rollback or recovery path if the change fails.

Question 10

A principal architect asks which AWS approach is intended to choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand without introducing an unrelated application rewrite. What is the best answer? The current estate includes 39 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 measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Use S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Use narrowly scoped security groups and network ACLs as required, and use VPC endpoints or PrivateLink for supported private service integrations
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: D

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of without introducing an unrelated application rewrite.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of 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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of without introducing an unrelated application rewrite.

D: Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. This directly addresses the primary requirement and remains appropriate without introducing an unrelated application rewrite.

Question 11

While conducting a production readiness review, the migration architect at Trey Research needs to avoid keeping long-lived infrequently used data in the highest-cost access tier without introducing an unrelated application rewrite. Which architecture decision best matches the stated constraints? The current estate includes 46 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 S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Use measured access patterns and latency/throughput requirements to choose the storage and delivery architecture, then monitor the relevant performance metrics
Use a staged deployment or upgrade plan with explicit change controls, validation gates, and rollback criteria
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:

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 avoid keeping long-lived infrequently used data in the highest-cost access tier 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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of without introducing an unrelated application rewrite.

Question 12

During a architecture review at Northwind Media, the principal solutions architect is designing a customer-facing API. The requirement is to model cross-AZ and cross-Region transfer charges before selecting a global architecture without introducing an unrelated application rewrite. Which architecture is the best fit? The current estate includes 6 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.

Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
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: 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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of without introducing an unrelated application rewrite.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture 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 directly addresses the primary requirement and remains appropriate without introducing an unrelated application rewrite.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of without introducing an unrelated application rewrite.

Question 13

Coho Financial operates a healthcare records application. In a hybrid connectivity redesign, the network architect must choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand while preserving least-privilege administration. Which option should be recommended? The current estate includes 13 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

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
Use service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements

Correct answer: B

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand 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 directly addresses the primary requirement and remains appropriate while preserving least-privilege administration.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand 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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while preserving least-privilege administration.

Question 14

A enterprise architect at Lamna Healthcare is reviewing a enterprise ERP system. The business requires the team to avoid keeping long-lived infrequently used data in the highest-cost access tier while preserving least-privilege administration. Which design most directly satisfies the requirement? The current estate includes 20 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 KMS/service-native encryption and TLS for data protection, with AWS WAF, Shield, and managed security services as appropriate for the threat model
Use narrowly scoped security groups and network ACLs as required, and use VPC endpoints or PrivateLink for supported private service integrations
Select instance families that match resource characteristics, use Auto Scaling where appropriate, and rightsize from observed metrics
Use S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while preserving least-privilege administration.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier 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 can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while preserving least-privilege administration.

D: Storage tiering reduces cost when lifecycle transitions match real access patterns, minimum-storage-duration rules, and retrieval expectations. This directly addresses the primary requirement and remains appropriate while preserving least-privilege administration.

Question 15

Which solution is the strongest match for the following professional-level architecture requirement: model cross-AZ and cross-Region transfer charges before selecting a global architecture while preserving least-privilege administration? The current estate includes 27 AWS accounts and active workloads in eu-west-1 and eu-central-1. The team wants the most direct architecture decision for this requirement.

Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
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
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: A

Option review:

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while preserving least-privilege administration.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture 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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while preserving least-privilege administration.

Question 16

An architecture board at Consolidated Messenger asks the security architect to choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand while keeping the design elastic as demand changes for a customer-facing API. Which recommendation is most appropriate? The current estate includes 34 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 cost and utilization data to rightsize resources, then choose Savings Plans, Reserved Instances, Spot, or On-Demand according to predictability and interruption tolerance
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
Use IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching

Correct answer: A

Option review:

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 commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while keeping the design elastic as demand changes.

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 commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while keeping the design elastic as demand changes.

D: 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 commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while keeping the design elastic as demand changes.

Question 17

For a healthcare records application at Litware Manufacturing, a global expansion project identifies one priority: avoid keeping long-lived infrequently used data in the highest-cost access tier while keeping the design elastic as demand changes. Which AWS design should the team choose? The current estate includes 41 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.

Review and raise service quotas before demand increases, and use the Route 53 routing policy that matches the application traffic requirement
Use narrowly scoped security groups and network ACLs as required, and use VPC endpoints or PrivateLink for supported private service integrations
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

Correct answer: D

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while keeping the design elastic as demand changes.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while keeping the design elastic as demand changes.

Question 18

Humongous Insurance has already validated the surrounding application components. The remaining architecture requirement for its enterprise ERP system is to model cross-AZ and cross-Region transfer charges before selecting a global architecture while keeping the design elastic as demand changes. Which option is best? The current estate includes 48 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 S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements
Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Use KMS/service-native encryption and TLS for data protection, with AWS WAF, Shield, and managed security services as appropriate for the threat model
Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while keeping the design elastic as demand changes.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while keeping the design elastic as demand changes.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture 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 directly addresses the primary requirement and remains appropriate while keeping the design elastic as demand changes.

Question 19

While conducting a migration wave planning session, the migration architect at Tailspin Logistics needs to choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand while using managed services when they satisfy the requirement. Which architecture decision best matches the stated constraints? The current estate includes 8 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
Implement the DR architecture that meets RTO/RPO and run scheduled recovery tests that validate dependencies, data, DNS, and operational procedures
Use Auto Scaling and managed integration services such as SQS, SNS, or Step Functions to create elastic, loosely coupled components
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: 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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while using managed services when they satisfy the requirement.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while using managed services when they satisfy the requirement.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while using managed services when they satisfy the requirement.

D: Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. This directly addresses the primary requirement and remains appropriate while using managed services when they satisfy the requirement.

Question 20

Which AWS architecture principle or service combination best addresses this requirement for Alpine Sports: avoid keeping long-lived infrequently used data in the highest-cost access tier while using managed services when they satisfy the requirement? The current estate includes 15 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.

Prefer the purpose-built managed AWS service that satisfies functional, security, reliability, and performance requirements with less operational ownership
Use infrastructure as code with CloudFormation and an automated CI/CD deployment strategy that supports health checks and rollback
Use managed multi-AZ or multi-Region capabilities according to the failure scope, with tested application and database failover
Use S3 storage classes and lifecycle policies, or equivalent service-native tiering, based on access frequency and retrieval requirements

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while using managed services when they satisfy the requirement.

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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while using managed services when they satisfy the requirement.

C: 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 avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while using managed services when they satisfy the requirement.

Question 21

Adventure Works operates a healthcare records application. In a security design review, the network architect must model cross-AZ and cross-Region transfer charges before selecting a global architecture while using managed services when they satisfy the requirement. Which option should be recommended? The current estate includes 22 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
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 IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while using managed services when they satisfy the requirement.

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 directly addresses the primary requirement and remains appropriate while using managed services when they satisfy the requirement.

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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while using managed services when they satisfy the requirement.

D: 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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while using managed services when they satisfy the requirement.

Question 22

A enterprise architect at VanArsdel Energy is reviewing a enterprise ERP system. The business requires the team to choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand while keeping observability sufficient to validate the result. Which design most directly satisfies the requirement? The current estate includes 29 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.

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 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: 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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while keeping observability sufficient to validate the result.

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand 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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while keeping observability sufficient to validate the result.

D: Rightsizing addresses resource efficiency first; pricing models then reduce the cost of the correctly sized usage pattern. This directly addresses the primary requirement and remains appropriate while keeping observability sufficient to validate the result.

Question 23

Contoso Retail is changing its data lake platform as part of a production readiness review. Which AWS approach best enables the team to avoid keeping long-lived infrequently used data in the highest-cost access tier while keeping observability sufficient to validate the result? The current estate includes 36 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.

Model data transfer paths and managed-service costs with AWS pricing tools, reduce avoidable transfer, and enforce budgets/usage controls
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
Choose the purpose-built database and apply caches, replicas, or buffering according to consistency, query, and latency requirements

Correct answer: B

Option review:

A: 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 avoid keeping long-lived infrequently used data in the highest-cost access tier 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 directly addresses the primary requirement and remains appropriate 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 can be valid in another AWS architecture context, but it does not most directly satisfy the primary requirement to avoid keeping long-lived infrequently used data in the highest-cost access tier under the additional constraint of while keeping observability sufficient to validate the result.

Question 24

An architecture board at Lucerne Publishing asks the security architect to model cross-AZ and cross-Region transfer charges before selecting a global architecture while keeping observability sufficient to validate the result for a customer-facing API. Which recommendation is most appropriate? The current estate includes 43 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 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
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

Correct answer: B

Option review:

A: 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 model cross-AZ and cross-Region transfer charges before selecting a global architecture under the additional constraint of while keeping observability sufficient to validate the result.

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 directly addresses the primary requirement and remains appropriate while keeping observability sufficient to validate the result.

Question 25

Following an acquisition, A. Datum Analytics is rationalizing its healthcare records application. The architecture board documented two acceptance criteria: choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand; and the solution must do so while avoiding a single manual recovery dependency. Which target-state recommendation should the cloud platform architect approve? The current estate includes 3 AWS accounts and active workloads in us-east-1 and eu-west-1. Assume all unspecified components already meet their requirements.

Adopt the appropriate managed AWS service and use Systems Manager or service-native automation for configuration and patching
Use IAM roles or other temporary-credential patterns with least privilege, and automate patch compliance through Systems Manager or managed-service patching
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 service-appropriate data replication, automated backup policies, and centralized monitoring with automated recovery actions

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 choose a commitment model for a predictable baseline and preserve on-demand flexibility for variable demand under the additional constraint of while avoiding a single manual recovery dependency.

B: 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 commitment model for a predictable baseline and preserve on-demand flexibility for variable demand 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: