Examkin

Cloud Concepts

358 questions

All types358Multiple choice180Multiple select178
Question 21Question →

A financial company is redesigning its monolithic on-premises transactional application to run on the AWS Cloud. The development team wants to apply core AWS cloud design principles to improve the application's agility, reduce management overhead, and ensure high availability. Which of the following architectural choices directly implement AWS Cloud design principles? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploying the application servers across multiple Availability Zones behind an Application Load Balancer to ensure the system remains operational if a zone fails.; Defining the infrastructure using AWS CloudFormation templates to easily deploy and terminate temporary environments for testing.

Answer

The correct choices are deploying the application servers across multiple Availability Zones behind an Application Load Balancer, and defining the infrastructure using AWS CloudFormation templates to deploy and terminate temporary environments.
Deploying the application servers across multiple Availability Zones behind an Application Load Balancer directly aligns with the 'design for failure' principle, as it prevents localized outages from bringing down the application. Defining the infrastructure as code using AWS CloudFormation templates implements the 'disposable resources' principle, enabling the team to easily spin up temporary testing environments and tear them down, thereby increasing operational agility.

Step-by-Step Solution

1
Analyze the requirement for improving high availability and reducing management overhead.
Deploying the application across multiple Availability Zones directly addresses high availability by eliminating a single point of failure (implementing 'design for failure').
AWS Infrastructure is designed around Availability Zones to isolate faults, and deploying across multiple zones protects against data center outages.
2
Analyze the requirement for improving agility and managing environments.
Defining the infrastructure as code with AWS CloudFormation templates allows the team to spin up and tear down testing environments on demand (implementing 'disposable resources').
In the cloud, resources are temporary and should be treated as disposable assets to optimize costs and deployment speed.
3
Evaluate and eliminate incorrect options based on cloud design anti-patterns.
Eliminated options involving a single large EC2 instance (monolith/single point of failure), fixed-capacity manual scaling (lack of elasticity), and customer guest OS patching (shared responsibility model mapping error).
These options represent common anti-patterns or misunderstandings of cloud concepts.

Key Concept

AWS Cloud Design Principles (Design for Failure and Disposable Resources)
Question 22Question →

A startup is building a microservices-based financial news application. They run their staging and test environments using automated scripts that create exact copies of production on demand, and then terminate these environments when testing is complete. Additionally, they use Amazon Simple Queue Service (Amazon SQS) to pass messages between their front-end web server and the backend stock analysis engine to ensure that components can scale and fail independently.

Which of the following AWS Cloud design principles are illustrated by these practices? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Loose coupling; Disposable resources

Answer

Loose coupling and Disposable resources are the design principles demonstrated in this scenario.
The system demonstrates loose coupling by using Amazon SQS to buffer and decouple interactions between the front-end and the backend, letting them run independently. It also demonstrates disposable resources by using automated scripts to create and destroy temporary staging and testing environments on demand.

Step-by-Step Solution

1
Analyze the usage of Amazon SQS in the scenario.
SQS acts as a message buffer between the web tier and the analysis engine.
By using a queue, the front-end web server does not need to know details about the backend processing tier, enabling both components to fail or scale independently, demonstrating loose coupling.
2
Analyze the environment management strategy.
Staging and testing environments are automatically created on demand and destroyed afterward.
This exemplifies using disposable resources, where server instances and environments are treated as temporary assets rather than fixed, permanent infrastructure.

Key Concept

Identifying design principles of the AWS Cloud, specifically loose coupling and disposable resources.
Question 23Question →

A healthcare provider plans to migrate its legacy IT infrastructure to the AWS Cloud. The migration team has identified two key workloads for the first phase:
1. An on-premises payroll application that is highly customized and expensive to maintain. The provider decides to decommission it and purchase a modern software-as-a-service (SaaS) payroll solution from a third-party vendor on AWS Marketplace.
2. A patient records database running on a self-managed server. The provider wants to migrate this database to Amazon Relational Database Service (Amazon RDS) to reduce administrative overhead, without making any modifications to the database schema or application code.

Which two of the following migration strategies represent the correct approach for these workloads? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Repurchasing for the payroll application; Replatforming for the patient records database

Answer

The correct migration strategies are repurchasing for the payroll application and replatforming for the patient records database.
Repurchasing is the correct strategy for the payroll application because it involves replacing the legacy system with a commercial SaaS product or package. Replatforming is the correct strategy for the patient records database because the workload is moved to a managed cloud service (Amazon RDS) to achieve operational optimizations without changing the database schema or application architecture.

Step-by-Step Solution

1
Analyze the migration plan for the payroll application.
The application is decommissioned and replaced with a third-party SaaS solution on AWS Marketplace.
This 'drop-and-shop' approach represents the Repurchasing strategy.
2
Analyze the migration plan for the patient records database.
The database is moved to a fully managed database service (Amazon RDS) to reduce operational overhead without changing schema or code.
This optimization ('tinkering') while keeping the core architecture intact represents the Replatforming strategy.

Key Concept

Selecting migration strategies (6 Rs) based on workload requirements and modernization goals.
Estimated Time:1m 30s
Question 24Question →

A retail company is preparing its web application for a major seasonal sales event. To ensure the application remains highly resilient and cost-effective during traffic fluctuations, the IT team wants to follow AWS Cloud architectural design principles. Which of the following options represent key AWS Cloud design principles that should be applied to this workload? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Build independent components that communicate via message queues or APIs to isolate failures.; Scale resource capacity automatically in response to real-time changes in consumer demand.

Answer

Building independent components that communicate via message queues or APIs, and scaling resource capacity automatically in response to real-time changes in consumer demand.
The correct options are building independent components that communicate via message queues or APIs, and scaling resource capacity automatically. These represent the principles of loose coupling and elasticity. Loose coupling isolates component failures so they do not cascade, while elasticity allows the infrastructure to scale dynamically to meet demand, ensuring both reliability and cost-efficiency.

Step-by-Step Solution

1
Analyze the requirements of the retail company's scenario, focusing on resilience and cost-effectiveness during a high-traffic seasonal event.
The architecture must be able to handle variable demand dynamically and prevent a single component's failure from disrupting the entire application.
This establishes that the system requires mechanisms for scaling dynamically and decoupling dependencies.
2
Evaluate the choices to identify which options represent standard AWS Cloud design principles that address these needs.
Building independent components that communicate via APIs or queues (loose coupling) and scaling automatically (elasticity) are selected as correct. Other options describing tight coupling, static sizing, and single monolithic instances are identified as anti-patterns.
To determine the correct architectural principles that match the scenario requirements.

Key Concept

Identify design principles of the AWS Cloud
Estimated Time:1m 0s
Question 25Question →

A healthcare technology company needs to expand its services to international markets. Previously, provisioning new infrastructure in physical colocation facilities took several weeks. By migrating to AWS, the company can now deploy its telehealth application to patients globally in a matter of minutes and spin up new testing environments in seconds to accelerate software release cycles.

Which two benefits of the AWS Cloud does this scenario directly illustrate? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Go global in minutes; Increase speed and agility

Answer

Go global in minutes and Increase speed and agility
The correct options are the benefits that refer to global deployment and agility. Deploying to patients globally in a matter of minutes directly illustrates the ability to go global in minutes, utilizing AWS's global infrastructure. Spinning up testing environments in seconds to accelerate release cycles illustrates the increase in speed and agility by reducing the time required to provision resource environments for developer experimentation.

Step-by-Step Solution

1
Analyze the business scenario and identify key infrastructure activities.
The scenario highlights deploying applications to international patients in minutes and spinning up testing environments in seconds.
This helps map the specific activities to the standard six benefits of the AWS Cloud.
2
Map the rapid global deployment activity to the corresponding AWS Cloud benefit.
Deploying internationally in minutes corresponds to the 'Go global in minutes' benefit.
AWS infrastructure allows developers to deploy applications in multiple regions around the world with just a few clicks.
3
Map the instant environment creation activity to the corresponding AWS Cloud benefit.
Spinning up new testing environments in seconds corresponds to 'Increase speed and agility'.
In a cloud environment, new resources are just a click away, dramatically reducing the time it takes to make those resources available to developers.

Key Concept

Benefits of the AWS Cloud
Estimated Time:1m 30s
Question 26Question →

An IoT startup is redesigning its smart utility grid monitoring application. The application receives millions of periodic sensor events that must be processed, validated, and saved. The team wants to align with AWS Cloud design principles to minimize operational overhead and handle unpredictable traffic spikes without maintaining running servers. Which of the following architectural design choices align with AWS Cloud design principles to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploying Amazon SQS to buffer incoming sensor data and decouple the ingestion tier from the processing tier.; Utilizing AWS Lambda to run processing logic only when events arrive, adhering to the 'services not servers' principle.

Answer

Deploying Amazon SQS to buffer incoming sensor data and decouple the ingestion tier from the processing tier, and utilizing AWS Lambda to run processing logic only when events arrive, adhering to the 'services not servers' principle.
The correct options are using Amazon SQS to buffer incoming sensor data and using AWS Lambda to run processing logic. Implementing Amazon SQS ensures that the system is loosely coupled, allowing the ingestion and processing layers to scale and fail independently. Utilizing AWS Lambda applies the 'services not servers' principle, enabling event-driven scaling without the operational overhead of provisioning or managing virtual servers.

Step-by-Step Solution

1
Analyze the business requirements for minimizing operational overhead and handling unpredictable traffic spikes without maintaining running servers.
Identified that serverless architectures ('services not servers') and asynchronous ingestion ('loose coupling') are required.
This helps match the needs to specific AWS Cloud design principles.
2
Evaluate the architectural options against AWS Cloud design principles.
Determined that Amazon SQS provides loose coupling and AWS Lambda provides a serverless execution environment, while the other options represent anti-patterns like tight coupling and lack of elasticity.
To select the two correct options that align with the AWS Well-Architected framework.

Key Concept

AWS Cloud design principles focus on building scalable, resilient, and efficient systems. Key principles include loose coupling, which reduces interdependencies between components, and 'services not servers', which leverages managed services to reduce operational overhead.
Question 27Question →

TerraGrow Agriculture is planning to migrate its legacy on-premises applications to the AWS Cloud. The company has identified two specific workloads for the first phase:

1. A proprietary crop-yield analysis application that must be moved immediately to AWS with absolutely no modifications to its code or configuration.
2. An on-premises legacy customer relationship management (CRM) database that will be decommissioned and replaced with a modern cloud-based Software-as-a-Service (SaaS) platform.

Which two AWS migration strategies should the company use to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Rehosting; Repurchasing

Answer

Rehosting and Repurchasing
Rehosting and Repurchasing are the correct strategies. Rehosting, often called 'lift-and-shift', moves workloads to AWS without modifying code or configuration, aligning with the crop-yield application requirement. Repurchasing, or 'drop-and-shop', replaces legacy systems with new cloud-native Software-as-a-Service (SaaS) products, matching the CRM replacement requirement.

Step-by-Step Solution

1
Analyze the migration requirements for the first workload (crop-yield analysis application).
The application must be moved quickly with zero changes to code or configuration, which maps to Rehosting (lift-and-shift).
Rehosting involves copying existing servers to AWS without modifications.
2
Analyze the migration requirements for the second workload (legacy CRM database).
The CRM database is being retired in favor of a new SaaS solution, which maps to Repurchasing (drop-and-shop).
Repurchasing involves adopting a different product, typically cloud-hosted SaaS, to replace a legacy system.

Key Concept

AWS Cloud migration strategies (6 Rs)
Estimated Time:1m 30s
Question 28Question →

A retail analytics firm runs monthly batch processing jobs on self-managed physical servers. The volume of data fluctuates significantly each month, leading to frequent job failures due to under-provisioned hardware, or wasted costs from over-provisioned hardware sitting idle. Additionally, the development team has to wait several weeks for the procurement and setup of new hardware whenever they want to test new analytics algorithms.

The firm decides to migrate these workloads to AWS, enabling them to launch test environments in minutes and automatically scale resources to match the workload demand.

Which of the following benefits of the AWS Cloud are directly demonstrated in this scenario? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Increase speed and agility; Stop guessing capacity

Answer

The correct benefits are 'Increase speed and agility' and 'Stop guessing capacity'.
The correct answers are the benefits 'Increase speed and agility' and 'Stop guessing capacity'. The ability to provision resources in minutes rather than waiting weeks for hardware procurement directly represents increased speed and agility. Furthermore, automatically scaling resources to match the exact workload demand instead of under-provisioning or over-provisioning demonstrates the benefit of stopping guessing capacity.

Step-by-Step Solution

1
Analyze the business challenges in the scenario.
The firm struggles with waiting weeks for hardware procurement to test new algorithms, and either under-provisioning (causing failures) or over-provisioning (idle hardware costs).
Understanding the initial problems helps map them to the corresponding AWS Cloud benefits.
2
Map the migration outcomes to the defined benefits of the AWS Cloud.
Launching test environments in minutes maps to 'Increase speed and agility'. Dynamically adjusting resources to match the workload demand maps to 'Stop guessing capacity'.
These outcomes directly resolve the key pain points described in the scenario.

Key Concept

Benefits of the AWS Cloud
Question 29Question →

AeroParts Manufacturing is planning to migrate its on-premises workloads to the AWS Cloud:

* Workload 1: A proprietary inventory forecasting application that runs on a self-managed database. The company wants to move the database to Amazon Relational Database Service (Amazon RDS) to reduce administrative overhead, without changing the application's core code.
* Workload 2: A legacy human resources (HR) application that has high maintenance costs. The company has decided to discard the legacy system and purchase a license for a cloud-based Software-as-a-Service (SaaS) HR platform.

Which migration strategies represent the correct approaches for Workload 1 and Workload 2? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Replatforming for Workload 1; Repurchasing for Workload 2

Answer

Replatforming for Workload 1 and Repurchasing for Workload 2 are the correct migration strategies.
The correct strategies are Replatforming for Workload 1 and Repurchasing for Workload 2. Replatforming involves making slight optimizations to take advantage of cloud platforms, such as migrating a self-managed database to Amazon RDS, without modifying the application's core code. Repurchasing involves transitioning to a different product, typically a Software-as-a-Service (SaaS) model, which matches the action of replacing the legacy HR application with a licensed SaaS platform.

Step-by-Step Solution

1
Analyze the requirements for Workload 1.
Workload 1 involves moving a self-managed database to Amazon RDS (a managed service) without altering the application's core code.
This type of optimization, where minor platform changes are made to leverage cloud benefits without re-architecting, is known as Replatforming.
2
Analyze the requirements for Workload 2.
Workload 2 involves discarding a legacy HR system and moving to a cloud-based SaaS provider.
Replacing a custom or legacy system with a commercially available off-the-shelf SaaS model is known as Repurchasing.

Key Concept

The 6 Rs Migration Strategies (Rehosting, Replatforming, Refactoring, Repurchasing, Retaining, Retiring) define how existing workloads are moved to the AWS Cloud.

Alternative Method

Analyze each workload option against the definitions of the 6 Rs migration strategies to eliminate strategies that do not match the business scenario.
Estimated Time:1m 30s
Question 30Question →

A biomedical research institution occasionally runs high-throughput genomic sequencing workloads that require thousands of compute instances for a few days. Once the analysis is complete, the computational resources are shut down completely. Instead of building an on-premises high-performance computing (HPC) cluster, the institution deploys these workloads on AWS.

Which of the following benefits of the AWS Cloud are directly demonstrated in this scenario? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Stop guessing capacity, as the institution can provision resources dynamically to match workload demands and shut them down when idle.; Increase speed and agility, as researchers can spin up resources in minutes rather than waiting weeks for IT infrastructure procurement.

Answer

The correct answers are the benefits of stopping guessing capacity and increasing speed and agility.
The scenario demonstrates two distinct AWS benefits: 'Stop guessing capacity' and 'Increase speed and agility'. By provisioning instances only when needed and terminating them when the workload is complete, the institution avoids guessing what size HPC cluster they must build. Furthermore, the ability to deploy thousands of instances in minutes rather than spending months procuring physical servers demonstrates speed and agility.

Step-by-Step Solution

1
Analyze the workload characteristics in the scenario.
The sequencing workloads are sporadic and massive, requiring thousands of instances for only a few days and zero resources when idle.
Understanding the usage pattern helps identify which AWS benefits map to these business needs.
2
Evaluate the AWS Cloud benefits against the workload requirements.
Spinning up resources quickly when needed maps to 'Increase speed and agility'. Shutting down instances completely during idle periods maps to 'Stop guessing capacity'.
This matches the requirements of the workload to the defined 6 benefits of AWS Cloud computing.
3
Eliminate the incorrect options based on cloud concepts and best practices.
Shifting OpEx to CapEx, permanently over-provisioning resources, and relying on monolithic architectures contradict cloud principles.
This confirms the two correct choices by validating that the remaining choices represent architectural or financial misconceptions.

Key Concept

Benefits of the AWS Cloud
Estimated Time:1m 30s
Question 31Question →

A healthcare enterprise is migrating its medical image processing pipeline to AWS. The pipeline experiences highly variable demand: it lies idle for hours, then must suddenly process thousands of high-resolution scans within minutes when clinical trials submit data. On-premises, the enterprise had to purchase and maintain a massive high-performance computing cluster sized for peak load, resulting in high idle costs. On AWS, they deploy a serverless architecture that dynamically scales to zero during idle periods and scales out instantly during peak submissions.

To resolve their capacity utilization challenge, which specific AWS Cloud benefit is the enterprise primarily leveraging?

Show answer & explanation

Answer: Stop guessing capacity

Answer

Stop guessing capacity
The correct answer is 'Stop guessing capacity' because this benefit specifically addresses capacity management. By leveraging elasticity to scale resources up and down in response to demand, organizations no longer need to pre-provision and pay for idle resources to support peak loads, nor do they risk performance issues from under-provisioning.

Step-by-Step Solution

1
Analyze the core problem described in the scenario.
The enterprise is dealing with highly variable demand (idle periods vs. sudden bursts) and wants to avoid paying for idle capacity while ensuring performance under peak loads.
This establishes that the primary issue is capacity management and utilization rather than initial resource provisioning speed or bulk unit pricing.
2
Evaluate the technical solution implemented on AWS.
They deploy a serverless architecture that dynamically scales down to zero and scales out instantly based on real-time demand.
This is a direct application of elasticity, which maps to the AWS Cloud benefit of not having to guess capacity needs.
3
Map the technical solution to the official six AWS Cloud benefits.
'Stop guessing capacity' is the benefit that specifically eliminates the need to pre-provision infrastructure for peak loads, preventing either expensive idle resources or capacity constraints.
While 'Trade fixed expense for variable expense' describes the payment model, the direct resolution of the capacity mismatch is described by 'Stop guessing capacity'.

Key Concept

The six benefits of the AWS Cloud, specifically the distinction between financial benefits (CapEx vs OpEx) and operational/technical capacity management (Elasticity / Stop guessing capacity).
Question 32Question →

An enterprise is redesigning a media-processing application to run on AWS. In the legacy architecture, a single, high-capacity virtual machine hosts the queue manager, the processing application, and the media storage. In the new architecture, media files are uploaded directly to Amazon S3, which triggers an AWS Lambda function. This function saves metadata to Amazon DynamoDB and sends a message to an Amazon SQS queue. A group of Amazon EC2 instances in an Auto Scaling group pulls messages from SQS to process the media files. Which set of AWS Cloud design principles does the new architecture most directly implement?

Show answer & explanation

Answer: Loose coupling by using Amazon SQS as an asynchronous buffer, services not servers by replacing the legacy queue and database with managed AWS offerings, and disposable resources by dynamically provisioning and terminating EC2 instances using Auto Scaling.

Answer

Loose coupling by using Amazon SQS as an asynchronous buffer, services not servers by replacing the legacy queue and database with managed AWS offerings, and disposable resources by dynamically provisioning and terminating EC2 instances using Auto Scaling.
The correct option correctly identifies three fundamental AWS Cloud design principles demonstrated in the redesign. Using Amazon SQS creates a decoupled (loosely coupled) boundary between the ingestion and processing tiers. Utilizing managed and serverless offerings like Amazon S3, AWS Lambda, and Amazon DynamoDB demonstrates the 'services not servers' principle, shifting operational responsibility to AWS. Employing Auto Scaling with EC2 instances allows resources to be treated as disposable, spinning up and down to match demand.

Step-by-Step Solution

1
Analyze the legacy architecture to identify anti-patterns.
The legacy system uses a single virtual machine hosting everything, which is a single point of failure (tightly coupled and monolithic).
Understanding the baseline architecture helps identify the specific cloud design principles applied during the redesign.
2
Examine the role of Amazon SQS in the new architecture.
Amazon SQS acts as a buffer between the ingestion layer (Lambda/S3) and the processing layer (EC2).
This shows the implementation of loose coupling, as the front-end and back-end can scale and fail independently without blocking each other.
3
Examine the role of Amazon S3, AWS Lambda, and Amazon DynamoDB.
These are managed or serverless services where AWS handles infrastructure provisioning, scaling, and maintenance.
This implements the 'services not servers' design principle, allowing the organization to focus on application code rather than server management.
4
Examine the role of Amazon EC2 with Auto Scaling.
EC2 instances are launched and terminated automatically based on queue size (demand).
This demonstrates treating resources as disposable rather than permanent, which aligns with elasticity and disposable resources principles.

Key Concept

AWS Cloud Design Principles (Loose Coupling, Services not Servers, Disposable Resources)
Question 33Question →

Veridian Dynamics is planning to migrate its legacy on-premises customer relationship management (CRM) system to the cloud. The company decides to decommission the legacy system and purchase a modern Software as a Service (SaaS) CRM platform from the AWS Marketplace. Which migration strategy does this scenario represent?

Show answer & explanation

Answer: Repurchasing

Answer

Repurchasing
The scenario describes repurchasing, which is a migration strategy where a company decides to replace its existing legacy system by purchasing a Software as a Service (SaaS) solution, often from the AWS Marketplace.

Step-by-Step Solution

1
Analyze the scenario and identify the migration action taken.
The company is replacing its legacy customer relationship management (CRM) software by purchasing a Software as a Service (SaaS) solution.
Determining the migration mechanism (replace vs. shift vs. rewrite) is the first step in classifying the migration strategy.
2
Map the action to one of the 6 Rs of migration strategies.
Purchasing a SaaS solution to replace a legacy workload maps to the Repurchasing strategy.
Repurchasing is defined as moving to a different product, typically a SaaS platform.

Key Concept

Repurchasing migration strategy
Question 34Question →

A biotechnology startup is developing a drug discovery platform that runs heavy genomic sequencing simulations. These workloads run for only a few days each month, requiring hundreds of compute instances, but the platform requires almost no resources for the rest of the month. Additionally, the startup must make the platform available to research teams in both North America and Europe with low latency.

Which of the following benefits of the AWS Cloud directly address this startup's requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Trade capital expense for variable expense; Go global in minutes

Answer

Trading capital expense for variable expense, and going global in minutes are the correct AWS Cloud benefits for this scenario.
The requirement to run heavy workloads only a few days a month without purchasing hardware aligns with the benefit of trading capital expense for variable expense, allowing the company to pay only for the resources they use. The requirement to deploy the platform to users in both North America and Europe with low latency is addressed by the benefit of going global in minutes, which enables rapid multi-region deployment.

Step-by-Step Solution

1
Analyze the business requirements from the scenario.
The startup needs to run high-compute workloads for only a few days a month without buying hardware, and needs to serve global users in North America and Europe with low latency.
Identifying specific requirements helps map them to corresponding cloud benefits.
2
Map the requirement of avoiding upfront hardware costs for periodic workloads to the correct AWS benefit.
This maps to 'trading capital expense for variable expense' since the startup pays only for what they consume.
The startup avoids large upfront CapEx by using variable OpEx.
3
Map the requirement of serving international users with low latency to the correct AWS benefit.
This maps to 'go global in minutes' since resources can be deployed in multiple global AWS Regions rapidly.
AWS infrastructure spanning multiple regions allows deployment close to target users worldwide.

Key Concept

AWS Cloud Benefits (specifically trading capital expense for variable expense, and going global in minutes)
Estimated Time:1m 30s
Question 35Question →

A media company is migrating its sports analytics platform to AWS. The platform experiences intense, unpredictable traffic surges during live sporting events, which last for a few hours, followed by long periods of inactive user traffic. To manage costs, the operations team configures the system to automatically provision additional compute instances as traffic rises, and automatically terminate those instances as soon as the event ends and traffic subsides.

Which AWS Cloud design principle is directly demonstrated by this design, and how does it distinctively differ from scalability?

Show answer & explanation

Answer: Elasticity, which focuses on the dynamic matching of resource supply to fluctuating demand, including the automatic reduction of capacity during low-traffic periods to optimize cost.

Answer

Elasticity, which focuses on the dynamic matching of resource supply to fluctuating demand, including the automatic reduction of capacity during low-traffic periods to optimize cost.
The correct answer is the choice describing elasticity. Elasticity is the design principle that refers to matching resource supply directly to fluctuating demand, enabling automatic resource expansion and contraction to minimize cost. Scalability is the ability to handle increased load but does not focus on shrinking capacity to save costs.

Step-by-Step Solution

1
Analyze the workload pattern.
The platform experiences brief, unpredictable traffic spikes during events, followed by long idle periods.
Understanding traffic patterns is necessary to determine the appropriate resource management strategy.
2
Identify the primary operational and cost goals.
The goal is to automatically add capacity during surges and remove capacity when idle to reduce costs.
Selecting a design principle requires aligning the technical solution with the business goals of cost efficiency and availability.
3
Differentiate between elasticity and scalability.
Elasticity dynamically scales capacity up and down to match demand, while scalability is the ability to scale up/out to handle growth.
This distinction ensures that the correct AWS principle is identified for dynamic contraction of resources.

Key Concept

AWS Cloud design principles focus on elasticity to match resources to demand dynamically, helping to optimize costs compared to traditional, statically provisioned infrastructure.
Question 36Question →

A retail corporation is planning to migrate its transaction processing database to AWS. Currently, the database runs on on-premises proprietary servers that must be replaced every 33 years at a high upfront cost. The servers are sized to handle peak traffic during holiday sales, meaning they run at less than 15%15\% utilization for the remainder of the year. Which of the following actions best demonstrates how the company can leverage AWS cloud economics to resolve their capacity utilization and hardware funding challenges?

Show answer & explanation

Answer: Adopting a pay-as-you-go model with auto-scaling resources that match database capacity to real-time consumer demand, thereby shifting hardware costs to variable operating expenses.

Answer

Adopting a pay-as-you-go model with auto-scaling resources that match database capacity to real-time consumer demand, thereby shifting hardware costs to variable operating expenses.
Adopting a pay-as-you-go model with auto-scaling database resources allows the company to pay only for the capacity they use, transitioning their high upfront physical hardware costs into variable operating expenses (OpEx) while automatically scaling down during off-peak times.

Step-by-Step Solution

1
Analyze the existing infrastructure challenges and requirements.
The retail company has high upfront capital expenses (hardware refresh every three years) and low utilization (under fifteen percent for ten months of the year) due to sizing hardware for peak demand.
Understanding the current financial and operational bottlenecks helps identify the relevant cloud economics solutions.
2
Identify the cloud economics principle that replaces upfront physical hardware purchasing.
Shifting from Capital Expenditures (CapEx) to Operating Expenditures (OpEx) allows paying only for resources used.
This shift addresses the high cost of the periodic physical hardware refresh cycles.
3
Determine the cloud capability needed to solve the low utilization issue.
Elasticity and auto-scaling dynamically match capacity to real-time demand.
Elasticity ensures the company does not pay for idle capacity during off-peak months.
4
Select the strategy that combines both CapEx-to-OpEx shift and elasticity.
Adopting a pay-as-you-go model with auto-scaling database resources.
This strategy eliminates upfront hardware refresh costs while dynamically scaling resources to match consumer demand, optimizing overall costs.

Key Concept

Understand concepts of cloud economics
Question 37Question →

An IoT fleet management company tracks real-time telemetry from thousands of delivery vehicles. The current architecture relies on self-hosted database clusters and monolithic backend servers on Amazon EC2. During peak hours, the servers experience CPU exhaustion, leading to lost data packets, while the database cluster requires manual partitioning and intervention to scale. The company wants to redesign this architecture on AWS to handle unpredictable traffic surges efficiently and minimize administrative overhead.

Which two architectural choices should the company implement to align with AWS cloud design principles? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy Amazon Kinesis Data Streams to ingest vehicle telemetry and AWS Lambda for processing, shifting infrastructure management to managed AWS services.; Store the telemetry data in Amazon DynamoDB with auto-scaling enabled, replacing the self-hosted database cluster to leverage managed services and automatic scaling.

Answer

The correct architectural choices are deploying Amazon Kinesis Data Streams with AWS Lambda for managed ingestion and processing, and storing the data in Amazon DynamoDB with auto-scaling enabled for a fully managed, elastic database layer.
Deploying managed services like Amazon Kinesis Data Streams and AWS Lambda aligns with the 'services not servers' and 'loose coupling' principles by removing the operational burden of server management and decoupling ingestion from processing. Using Amazon DynamoDB with auto-scaling aligns with 'services not servers' and 'elasticity' by automatically scaling database capacity to handle traffic surges without manual intervention.

Step-by-Step Solution

1
Analyze the business and technical constraints: the current architecture has monolithic bottlenecks on EC2 and a self-hosted database requiring manual scaling, and needs to handle unpredictable surges with low overhead.
Identify the target cloud design principles required: 'services not servers' (to reduce administrative overhead), 'loose coupling' (to separate ingestion/processing and prevent packet loss), and 'elasticity' (to dynamically match unpredictable demand).
Understanding the principles ensures incorrect anti-patterns can be filtered out.
2
Evaluate compute and ingestion options against 'services not servers' and 'loose coupling'.
Selecting the combination of Amazon Kinesis Data Streams and AWS Lambda decouples ingestion from processing and leverages serverless managed services.
This removes server management overhead and prevents CPU exhaustion from causing packet loss.
3
Evaluate database options against 'services not servers' and 'elasticity'.
Selecting Amazon DynamoDB with auto-scaling enabled replaces the self-hosted cluster with a managed database that dynamically scales capacity up and down.
This eliminates manual partitioning and aligns resource consumption directly with demand.

Key Concept

AWS Cloud design principles, specifically 'services not servers', 'loose coupling', and 'elasticity'.
Question 38Question →

A retail company plans to migrate its on-premises relational database to AWS. The database currently runs on a self-managed physical server. To reduce operational overhead such as backups and patching, the company decides to migrate the database to Amazon RDS without modifying the database engine or making changes to the application code. Which cloud migration strategy is this company employing?

Show answer & explanation

Answer: Replatforming

Answer

Replatforming is the correct migration strategy because it involves migrating the database to a managed service to reduce operational tasks without changing the database engine or the core application code.
Replatforming is the correct strategy because the company is moving their database to a managed platform (Amazon RDS) to reduce administrative overhead, but they are retaining the same database engine and code, making minimal modifications without re-architecting the application.

Step-by-Step Solution

1
Analyze the company's objective.
The company wants to move a database to AWS, reduce management overhead (patching, backups), and keep the database engine and application code the same.
This establishes the scope of changes: some optimization (using a managed service) is done, but the core architecture remains unchanged.
2
Map the scenario to the 6 Rs migration strategies.
Moving a self-managed database to a fully managed platform (Amazon RDS) without core code modification is known as Replatforming.
This strategy allows the organization to benefit from cloud-managed infrastructure without the cost or complexity of a full redesign.

Key Concept

Cloud Migration Strategies (Replatforming)
Question 39Question →

A logistics company wants to migrate its legacy shipment-tracking application to the AWS Cloud. The primary goal is to complete the migration as quickly as possible to meet an upcoming data center evacuation deadline, without making any modifications to the application code or architecture. Which migration strategy should the company use to meet this requirement?

Show answer & explanation

Answer: Rehosting

Answer

Rehosting
The correct strategy is Rehosting. Rehosting, often referred to as 'lift-and-shift', involves migrating applications from an on-premises environment to AWS virtual machines (Amazon EC2) with no changes to the application code, architecture, or configuration. This makes it the fastest migration method and ideal for urgent data center evacuations.

Step-by-Step Solution

1
Analyze the company's constraints and goals from the scenario.
The company needs to migrate quickly due to a deadline and wants to make zero code or architecture changes.
This establishes the requirements for the migration strategy.
2
Map the zero-change, fast migration requirement to the AWS migration strategies (6 Rs).
Rehosting is identified as the strategy that copies the application to the cloud as-is without code changes.
Rehosting matches the requirement of minimal modification and rapid deployment.

Key Concept

AWS Cloud Migration Strategies (6 Rs)
Estimated Time:45s
Question 40Question →

A retail startup wants to launch a new e-commerce application. Instead of investing heavily in physical servers and building their own data centers before knowing how successful the application will be, they decide to deploy on AWS and pay only for the resources they consume. Which benefit of the AWS Cloud is this startup demonstrating?

Show answer & explanation

Answer: Trading capital expense for variable expense

Answer

Trading capital expense for variable expense
Trading capital expense for variable expense is the correct benefit. By using AWS, the startup avoids capital expenses (CapEx) associated with purchasing and maintaining physical servers. Instead, they pay for computing resources as variable expenses (OpEx) based on actual usage.

Step-by-Step Solution

1
Analyze the business scenario described in the stem.
The startup wants to avoid upfront infrastructure costs and instead pay incrementally based on usage.
This relates to the economic benefits of cloud computing.
2
Match the scenario to the official AWS Cloud benefits.
Paying on-demand for resources instead of investing in physical data centers upfront represents trading capital expenses (CapEx) for variable expenses (OpEx).
To identify which cloud benefit fits paying only for what is consumed without upfront investment.

Key Concept

Trading capital expense for variable expense is a key economic benefit of the AWS Cloud, enabling organizations to pay only for the resources they consume rather than investing heavily in physical data centers and servers upfront.
PreviousPage 2 / 18Next
Cloud Concepts Practice Questions — AWS Certified Cloud Practitioner — Page 2 | Examkin