Examkin

Cloud Concepts

358 questions

All types358Multiple choice180Multiple select178
Question 161Question →

EcoHarvest Co-op, a regional agricultural cooperative, is planning to migrate its operations to the AWS Cloud. During the application discovery phase, the IT team decides to decommission their legacy, on-premises billing application and replace it with a commercial Software-as-a-Service (SaaS) billing solution. Which migration strategy does this decision represent?

Show answer & explanation

Answer: Repurchasing

Answer

Repurchasing
The correct answer is Repurchasing. This migration strategy, sometimes called 'drop-and-shop', involves retiring an existing legacy application and replacing it with a new product, typically a Software-as-a-Service (SaaS) platform, or buying a different license.

Step-by-Step Solution

1
Analyze the migration scenario details.
The scenario describes a company decommissioning their legacy billing application and replacing it with a commercial Software-as-a-Service (SaaS) billing solution.
Identifying key actions like replacing legacy software with a SaaS model is essential to mapping the migration to the correct 6 Rs strategy.
2
Evaluate the 6 Rs migration strategies against the identified action.
Replacing a system with a different product (typically SaaS) is the definition of the Repurchasing strategy.
This confirms that the strategy is Repurchasing rather than Rehosting, Replatforming, or Refactoring.

Key Concept

AWS Cloud Migration Strategies (6 Rs)
Question 162Question →

A global smart agriculture company collects telemetry data from soil sensors deployed in various fields. The volume of data fluctuates significantly, peaking during harvest seasons and dropping to near zero during winter. The company is migrating its data processing workload from an on-premises data center to the AWS Cloud. Which two of the following describe the primary cloud economic advantages of this migration?

Select all that apply

Show answer & explanation

Answer: Shifting from a capital expense (CapEx) model of purchasing physical hardware to a variable operating expense (OpEx) model.; Leveraging cloud elasticity to scale resources down during the off-season, preventing costs associated with idle capacity.

Answer

Shifting from a capital expense (CapEx) model of purchasing physical hardware to a variable operating expense (OpEx) model, and leveraging cloud elasticity to scale resources down during the off-season, preventing costs associated with idle capacity.
The correct options represent core cloud economic advantages. The transition from capital expenses to operating expenses allows a business to pay only for the resources consumed rather than investing upfront in depreciating physical hardware. Furthermore, leveraging elasticity allows the system to scale down during low-activity periods (winter), preventing wasted expenditure on idle server capacity.

Step-by-Step Solution

1
Analyze the workload characteristics described in the scenario.
The workload has highly seasonal and fluctuating demand (high peak during harvests, low during winter).
Understanding the usage pattern helps identify the financial benefits of scaling resources dynamically.
2
Evaluate the financial shift in cloud computing.
On-premises requires upfront Capital Expenses (CapEx) for peak capacity, whereas AWS uses variable Operating Expenses (OpEx).
This identifies the economic advantage of trading fixed capital costs for variable operational costs.
3
Apply the concept of elasticity to the fluctuating demand.
AWS resources can scale down when demand is low (winter) and scale up when demand is high (harvest).
This explains how the cost benefit of elasticity prevents paying for idle resources.

Key Concept

Understand concepts of cloud economics including CapEx vs OpEx and the cost benefits of elasticity.
Estimated Time:2m 0s
Question 163Question →

An agricultural analytics company processes soil sensor telemetry data from farms across North America. The data volume increases tenfold during the spring planting season but drops to near zero during the winter months. By migrating to AWS, the company dynamically adjusts its computing resources to match the seasonal demand, avoiding the need to purchase infrastructure based on peak workload projections. Which benefit of the AWS Cloud does this scenario demonstrate?

Show answer & explanation

Answer: Stop guessing capacity

Answer

Stop guessing capacity
The correct answer is the option stating 'Stop guessing capacity'. In traditional IT, organizations must estimate and pay for peak capacity to avoid outages during busy periods, leading to idle resources during off-peak times. AWS eliminates this issue by allowing resources to scale dynamically as needed.

Step-by-Step Solution

1
Analyze the company's problem of fluctuating seasonal demand and the desire to avoid purchasing infrastructure based on peak predictions.
Identify that the issue stems from having to predict and provision hardware capacity in advance.
Determining capacity requirements in advance often leads to either wasted resource expenses or service outages.
2
Match the solution of dynamically scaling resources to the defined AWS Cloud benefits.
The capability to adjust resources to match actual demand dynamically corresponds to the benefit of 'Stop guessing capacity'.
AWS allows businesses to scale resources on-demand, eliminating the need to guess and pay for peak infrastructure capacity.

Key Concept

Define the benefits of the AWS Cloud
Estimated Time:1m 0s
Question 164Question →

Apex Realty Group is migrating its IT infrastructure to the AWS Cloud. The migration team has decided to move its legacy customer-facing web portal directly to Amazon EC2 instances without modifying any code. Additionally, they plan to migrate their relational database to Amazon Relational Database Service (Amazon RDS) to minimize database administration effort while keeping the application's underlying code unchanged. Which two of the following migration strategies are being utilized by Apex Realty Group?

Select all that apply

Show answer & explanation

Answer: Rehosting; Replatforming

Answer

Rehosting and Replatforming
Rehosting is correct because moving the legacy customer-facing web portal to Amazon EC2 without code changes is a classic lift-and-shift. Replatforming is correct because moving the database to a managed service like Amazon RDS to reduce management overhead while keeping the core code intact is a lift-tinker-and-shift.

Step-by-Step Solution

1
Analyze the web portal migration
The web portal is moved to Amazon EC2 with zero code changes, which corresponds directly to the Rehosting strategy.
Identifying that no modifications are made to the code indicates a pure lift-and-shift (Rehosting).
2
Analyze the database migration
The database is moved to Amazon RDS to reduce management overhead without changing the core architecture, which corresponds directly to the Replatforming strategy.
Switching from self-managed database infrastructure to a managed service (Amazon RDS) without altering core application logic represents a lift-tinker-and-shift (Replatforming).

Key Concept

Cloud migration strategies (6 Rs)
Question 165Question →

An engineering firm designs and tests wind turbine prototypes using computational fluid dynamics (CFD) simulations. Historically, their on-premises computing clusters sat idle during design-drafting phases, yet became heavily bottlenecked with long job queues during testing phases. By migrating these workloads to AWS, they can spin up hundreds of virtual cores on demand to run simulations in parallel, and immediately terminate them when the runs complete. Which AWS Cloud benefit is directly demonstrated by resolving this specific challenge of idle hardware and queue delays?

Show answer & explanation

Answer: Stop guessing capacity

Answer

Stop guessing capacity
The correct answer is 'Stop guessing capacity'. The scenario highlights the classic dilemma of capacity planning: having idle resources during low-demand periods (over-provisioning) and queue bottlenecks during peak periods (under-provisioning). AWS solves this by allowing resources to scale up and down dynamically as needed, meaning organizations no longer need to forecast capacity beforehand.

Step-by-Step Solution

1
Analyze the business problem in the scenario: the engineering firm experiences periods of idle resources (over-provisioning) and periods of queue delays (under-provisioning) due to static infrastructure capacity constraints.
Identified that the core challenge is related to predicting and matching infrastructure capacity to fluctuating simulation workloads.
Understanding the operational bottleneck is the first step in mapping it to the correct cloud benefit.
2
Evaluate how migrating to AWS resolves this challenge: the firm can dynamically spin up resources on demand and terminate them immediately when finished.
AWS allows the firm to scale capacity up and down within minutes, eliminating the need to pre-allocate fixed hardware.
This shows how dynamic cloud elasticity solves the traditional capacity forecasting problem.
3
Map this solution to the six official AWS Cloud benefits defined in the AWS Certified Cloud Practitioner curriculum.
The ability to dynamically scale resources to match demand and eliminate the issues of idle hardware or capacity limits maps directly to 'Stop guessing capacity'.
Official AWS documentation defines 'Stop guessing capacity' as eliminating the need to make capacity decisions prior to deploying applications, preventing sitting on idle resources or dealing with limited capacity.

Key Concept

AWS Cloud Benefit: Stop guessing capacity
Question 166Question →

A startup is building a new mobile application backend. The development team wants to focus entirely on writing application code without the operational overhead of provisioning, patching, or managing virtual servers. Which AWS Cloud design principle is best demonstrated by choosing managed services like AWS Lambda and Amazon DynamoDB for this architecture?

Show answer & explanation

Answer: Services, not servers

Answer

Services, not servers
The principle of 'Services, not servers' recommends using AWS managed services to eliminate the need for customers to manage, patch, and provision virtual servers. By choosing managed offerings like AWS Lambda (serverless compute) and Amazon DynamoDB (serverless database), developers can focus entirely on application logic while AWS handles the underlying infrastructure.

Step-by-Step Solution

1
Analyze the requirements in the scenario.
The team wants to avoid provisioning, patching, and managing virtual servers, opting instead for managed services.
This helps identify which AWS design principle removes server management overhead.
2
Compare the scenario details with AWS Cloud design principles.
Using serverless and managed services like AWS Lambda and Amazon DynamoDB aligns directly with the principle of using services instead of managing servers.
This confirms the correct architectural principle being applied.

Key Concept

Services, not servers
Question 167Question →

A software-as-a-service (SaaS) startup is launching a new application on AWS. The workload is expected to be highly variable, with unpredictable traffic spikes throughout the day. The startup's Chief Financial Officer (CFO) wants to minimize up-front infrastructure costs and ensure that the company only pays for the compute resources it actually consumes. Which of the following strategies aligns with AWS cloud economics to meet the CFO's requirements?

Show answer & explanation

Answer: Deploying the application using an elastic architecture that automatically scales resources in response to demand, converting fixed capital expenses (CapEx) into variable operating expenses (OpEx).

Answer

Deploying the application using an elastic architecture that automatically scales resources in response to demand, converting fixed capital expenses (CapEx) into variable operating expenses (OpEx).
The strategy of deploying an elastic architecture that scales dynamically based on real-time demand allows the startup to pay only for the resources they consume. This represents a shift from capital expenses (CapEx) to variable operating expenses (OpEx), which is a key concept of cloud economics.

Step-by-Step Solution

1
Identify the CFO's financial constraints and requirements.
The CFO wants to minimize up-front infrastructure costs (avoid CapEx) and pay only for consumed capacity (leverage variable costs/elasticity).
This defines the target economic criteria to evaluate the options.
2
Analyze the economic impact of static vs. elastic architectures in the cloud.
An elastic architecture scales resources down when demand is low, preventing charges for idle capacity and representing a variable operating expense (OpEx).
This determines how elasticity affects TCO.
3
Evaluate the billing and operational characteristics of the options.
Only the option utilizing an elastic architecture to transition from CapEx to OpEx satisfies both the avoidance of up-front costs and the dynamic matching of capacity to demand.
This confirms the correct choice based on cloud economic principles.

Key Concept

Shifting capital expenses (CapEx) to operating expenses (OpEx) through elasticity
Question 168Question →

EduPath Learning, an online education provider, is migrating its systems to the AWS Cloud. The migration team has decided on the following actions:

1. The relational database for the student portal will be moved to Amazon RDS for PostgreSQL to take advantage of automated patching and backups, without changing the application logic.
2. A legacy system used for processing legacy course credits, which is planned for decommissioning next year, will be kept on-premises in its current state for now.

Which two of the following migration strategies are represented by these decisions?

Select all that apply

Show answer & explanation

Answer: Replatforming; Retaining

Answer

Replatforming and Retaining
Replatforming represents the decision to move the database to Amazon RDS to benefit from managed services without modifying the core application code. Retaining represents the decision to keep the legacy billing system on-premises in its current state until it is decommissioned.

Step-by-Step Solution

1
Analyze the first decision: migrating the database to Amazon RDS for PostgreSQL without changing application logic to leverage managed backups.
This is Replatforming (lift-tinker-and-shift) because the database is optimized for cloud management without code changes.
Identifying the characteristics of migrating to a managed service like RDS matches the Replatforming strategy.
2
Analyze the second decision: keeping the legacy course-credits system on-premises in its current state because it is scheduled to be retired.
This is Retaining because the workload is kept on-premises as-is during the migration process.
Identifying that keeping a workload on-premises during migration fits the Retaining strategy.

Key Concept

AWS Cloud Migration Strategies (6 Rs)
Estimated Time:1m 30s
Question 169Question →

A retail pharmacy chain is launching a digital prescription delivery platform. The company wants to deploy its application without predicting how many users will register in the first week, avoiding the risk of under-provisioning servers. Additionally, they want to focus their engineering talent on writing software features rather than managing physical server racks and hypervisors. Which of the following AWS Cloud benefits directly align with these goals? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Stop guessing capacity; Stop spending money running and maintaining data centers

Answer

The correct answers are 'Stop guessing capacity' and 'Stop spending money running and maintaining data centers'.
The correct benefits are 'Stop guessing capacity' and 'Stop spending money running and maintaining data centers'. 'Stop guessing capacity' allows the business to launch without predicting first-week user registrations, eliminating the risk of under-provisioning. 'Stop spending money running and maintaining data centers' allows engineers to focus on software features rather than managing infrastructure layers.

Step-by-Step Solution

1
Analyze the company's requirement to launch without predicting registration numbers and avoid under-provisioning.
Identify that this requirement maps directly to the benefit of not needing to pre-determine infrastructure size, which is defined as 'Stop guessing capacity'.
This benefit allows scaling resources dynamically in response to actual demand rather than making upfront capacity assumptions.
2
Analyze the requirement to focus engineering talent on software features rather than managing physical server racks and hypervisors.
Identify that this requirement maps directly to offloading infrastructure management to AWS, which is defined as 'Stop spending money running and maintaining data centers'.
By eliminating rack maintenance, power, cooling, and hypervisor management, engineering resources are freed up to focus on business-differentiating features.

Key Concept

The 6 Advantages of Cloud Computing (AWS Cloud Benefits)
Question 170Question →

An online organic grocery startup is planning to migrate its operations to the AWS Cloud. The startup wants to stop managing physical server infrastructure and quickly expand its delivery booking system to customers across Europe and Asia with minimal latency. Which of the following benefits of the AWS Cloud directly align with these goals? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Stop spending money running and maintaining data centers; Go global in minutes

Answer

The correct benefits are stopping spending money running and maintaining data centers, and going global in minutes.
The correct options are stopping spending money running and maintaining data centers, which removes the burden of infrastructure management, and going global in minutes, which allows rapid deployment across multiple geographical regions to reduce latency.

Step-by-Step Solution

1
Analyze the business requirements of the startup.
The startup needs to eliminate physical infrastructure management costs and deploy services in Europe and Asia with low latency.
Understanding the customer's business requirements helps map them to specific cloud benefits.
2
Identify the AWS benefit that maps to eliminating server maintenance costs.
The benefit is 'Stop spending money running and maintaining data centers.'
AWS manages physical data centers, allowing customers to redirect resources to core business tasks.
3
Identify the AWS benefit that maps to deploying services to global users with low latency.
The benefit is 'Go global in minutes.'
AWS global infrastructure allows deployment across multiple global Regions rapidly.

Key Concept

Benefits of the AWS Cloud
Question 171Question →

A satellite imagery analytics company processes massive volumes of earth observation data. The processing workload is highly variable, spiking dramatically after major weather events when customers request urgent assessments, while remaining idle during normal operations. Historically, the company maintained a large on-premises server cluster to handle peak demands, resulting in low average resource utilization. Which of the following AWS Cloud benefits directly address this organization's challenges? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Stop guessing capacity; Stop spending money running and maintaining data centers

Answer

The correct benefits are stopping guessing capacity and stopping spending money running and maintaining data centers.
The correct answers are the benefits of stopping guessing capacity and stopping spending money running and maintaining data centers. The satellite imagery company's workload is highly variable, meaning that scaling resources dynamically (stopping guessing capacity) prevents low utilization. Additionally, eliminating physical server clusters removes the financial and operational burden of managing their own data center facility.

Step-by-Step Solution

1
Analyze the organization's business and technical challenge.
The company has highly variable workloads (spiking after weather events, idle during normal operations) and historically paid high costs to maintain physical on-premises servers that had low average utilization.
This establishes that the challenges relate to capacity management, resource utilization, and physical data center overhead.
2
Evaluate the option regarding capacity management.
The benefit of 'stopping guessing capacity' allows them to dynamically scale up during spikes and down during idle times, directly solving the utilization issue.
It eliminates the need to pre-provision infrastructure for maximum potential load.
3
Evaluate the option regarding physical infrastructure maintenance.
The benefit of 'stopping spending money running and maintaining data centers' allows the company to eliminate the overhead of managing physical server clusters.
This shifts the focus and budget from keeping physical hardware running to analyzing satellite data.
4
Confirm the remaining options are incorrect.
The options proposing trading variable costs for capital costs, using monolithic architectures, or using static provisioning represent common cloud misconceptions.
AWS encourages trading capital expenses for variable expenses, using loosely coupled designs, and leveraging dynamic elasticity.

Key Concept

Benefits of the AWS Cloud
Question 172Question →

A startup is designing a collaborative document editing platform on AWS. The development team wants to minimize the operational effort required to manage database infrastructure. They also want to ensure that testing environments can be spun up quickly for developers and completely destroyed when no longer needed to optimize costs.

Which of the following architectural decisions align with the AWS Cloud design principles of 'services not servers' and 'disposable resources'? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Using AWS CloudFormation to define infrastructure as code, enabling testing environments to be deployed programmatically and terminated when testing is complete; Storing application metadata and user session state in Amazon DynamoDB instead of running a self-managed database cluster on virtual servers

Answer

The correct architectural decisions are using AWS CloudFormation to define infrastructure as code for dynamic environment creation and termination, and using Amazon DynamoDB for metadata storage to replace self-managed servers.
The correct options are using AWS CloudFormation for automated environment provisioning and destruction, and storing metadata in Amazon DynamoDB. AWS CloudFormation enables infrastructure as code, which directly implements the 'disposable resources' principle by allowing environments to be created and destroyed dynamically. Storing data in Amazon DynamoDB implements the 'services not servers' principle by leveraging a fully managed, serverless database service that eliminates the need to provision, patch, or maintain virtual servers.

Step-by-Step Solution

1
Identify the requirements of the scenario.
The startup wants to minimize database infrastructure management effort (suggesting 'services not servers') and dynamically create and destroy testing environments (suggesting 'disposable resources').
To narrow down the options that align with these specific target principles.
2
Evaluate the option regarding database management.
Choosing Amazon DynamoDB instead of self-hosted database clusters on EC2 aligns with 'services not servers' by utilizing a managed service.
DynamoDB is fully managed, eliminating the need to manage database servers.
3
Evaluate the option regarding testing environments.
Using AWS CloudFormation to programmatically spin up and tear down environments aligns with 'disposable resources'.
CloudFormation allows resources to be treated as temporary assets that are easily provisioned and terminated.

Key Concept

AWS Cloud design principles focus on scalability, elasticity, loose coupling, disposable resources, and using managed services to reduce operational overhead.
Question 173Question →

A company is migrating its legacy customer booking application to the AWS Cloud. During this process, the development team wants to ensure that a failure in the email notification service does not halt the entire booking system. In addition, the developers want to automatically build temporary staging environments for testing and terminate them as soon as testing is complete. Which of the following AWS Cloud design principles are demonstrated in this scenario? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Loose coupling; Disposable resources

Answer

Loose coupling and Disposable resources
Loose coupling decouples system components to isolate failures and maintain system availability even when one component fails. Disposable resources enable the use of automation to dynamically instantiate and terminate infrastructure components on demand, minimizing waste.

Step-by-Step Solution

1
Analyze the first requirement: ensuring that a failure in the email notification service does not stop the booking system.
This requires decoupling the components so they operate independently, which aligns with the design principle of Loose coupling.
By reducing dependencies between services, the application gains higher fault tolerance.
2
Analyze the second requirement: automatically creating temporary environments for testing and terminating them when done.
This involves using automation to treat environments as temporary, which aligns with the design principle of Disposable resources.
Treating servers as temporary assets rather than permanent hardware optimizes costs and operations.

Key Concept

AWS Cloud design principles recommend decoupling systems (loose coupling) and utilizing automated, temporary infrastructure (disposable resources) to build reliable, cost-effective applications.
Estimated Time:45s
Question 174Question →

A mobile game studio based in London is launching a new multiplayer game. The studio needs to deploy its game backend servers in multiple locations worldwide, specifically near players in North America, Europe, and Asia, to ensure low-latency gameplay. Which AWS Cloud benefit is this studio utilizing by deploying their application across multiple AWS Regions with just a few clicks?

Show answer & explanation

Answer: Go global in minutes

Answer

Go global in minutes
The correct option is 'Go global in minutes'. This benefit represents the ability to deploy applications in multiple AWS Regions around the world with just a few clicks. In this scenario, the game studio is using this capability to place its servers close to players in North America, Europe, and Asia to minimize latency and improve the gaming experience.

Step-by-Step Solution

1
Analyze the scenario requirements
The scenario describes a game studio that needs to deploy backend servers globally (North America, Europe, Asia) to provide low-latency gameplay to users in those regions.
Identifying the core goal (reducing latency globally by deploying across multiple geographic locations) helps map it to the correct AWS Cloud benefit.
2
Match the requirement to the six AWS Cloud benefits
The ability to deploy applications globally across multiple AWS Regions with minimal effort matches the 'Go global in minutes' benefit.
AWS allows quick deployment in multiple Regions globally, which reduces latency for end-users, aligning perfectly with the studio's objective.

Key Concept

Go global in minutes
Question 175Question →

NovaPeak Manufacturing is planning to migrate two of its IT workloads to the AWS Cloud. First, they want to migrate a legacy inventory database to Amazon EC2 without making any architectural or code changes. Second, they plan to replace their on-premises customer relationship management (CRM) software with a cloud-based Software-as-a-Service (SaaS) subscription. Which two cloud migration strategies should NovaPeak Manufacturing select for these workloads? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Rehosting (Lift-and-Shift); Repurchasing (Drop-and-Shop)

Answer

The correct strategies are Rehosting (Lift-and-Shift) and Repurchasing (Drop-and-Shop).
The correct strategies are Rehosting (Lift-and-Shift) and Repurchasing (Drop-and-Shop). Rehosting is correct because moving the legacy database to Amazon EC2 without any changes is a classic lift-and-shift approach. Repurchasing is correct because moving from self-hosted software to a SaaS subscription represents purchasing a new product.

Step-by-Step Solution

1
Analyze the first workload requirement: migrating the legacy database to Amazon EC2 without making any architectural or code changes.
Identify that moving a workload 'as-is' corresponds to the Rehosting (Lift-and-Shift) migration strategy.
This strategy allows organizations to quickly migrate workloads without redesigning the application.
2
Analyze the second workload requirement: replacing the on-premises CRM software with a cloud-based SaaS subscription.
Identify that discarding an existing application to purchase a new product or utility service (like SaaS) corresponds to the Repurchasing (Drop-and-Shop) strategy.
This strategy shifts the business to a different product or platform, often managed by a third-party vendor.

Key Concept

AWS Cloud Migration Strategies (6 Rs)
Question 176Question →

SwiftCargo Logistics is planning to migrate its application portfolio to the AWS Cloud. During the analysis, the migration team identifies an old, duplicate database application that is no longer used by any business unit. The team decides to shut down and decommission this application completely before the migration begins. Which migration strategy is the company applying to this specific application?

Show answer & explanation

Answer: Retiring

Answer

Retiring
The correct strategy is Retiring. In the context of AWS migration strategies (the 6 Rs), Retiring involves identifying applications that are no longer useful or redundant and turning them off completely. This reduces the migration scope, security footprint, and ongoing maintenance costs.

Step-by-Step Solution

1
Analyze the business scenario described in the question.
The scenario describes an application that is no longer used and is being shut down and decommissioned completely.
Understanding the lifecycle status of the application is necessary to map it to the correct AWS migration strategy.
2
Map the action of decommissioning an unneeded application to the 6 Rs migration strategies.
Decommissioning or turning off applications that are no longer needed corresponds to the 'Retire' (or Retiring) migration strategy.
The 'Retire' strategy focuses on identifying redundant or obsolete assets and shutting them down to reduce costs and narrow the migration scope.

Key Concept

AWS Cloud Migration Strategies (6 Rs) - Retiring
Estimated Time:45s
Question 177Question →

A retail company is migrating its e-commerce platform to AWS. The finance department wants to eliminate high upfront capital expenditures for data centers and instead pay for resources only as they are consumed. Simultaneously, the IT operations team wants to avoid the risk of either underprovisioning servers during peak sales events or paying for idle capacity during low-traffic periods. Which of the following benefits of the AWS Cloud directly address these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Trade fixed expense for variable expense; Stop guessing capacity

Answer

The correct benefits are trading fixed expense for variable expense and stopping guessing capacity.
The correct benefits demonstrated in this scenario are trading fixed expense for variable expense and stopping guessing capacity. Trading fixed expense for variable expense allows the company to convert costly upfront hardware investments (capital expenses) into variable operating expenses that match actual usage. Stopping guessing capacity ensures that resources dynamically scale to meet traffic demand, eliminating both service downtime from underprovisioning and financial waste from idle overprovisioned servers.

Step-by-Step Solution

1
Analyze the finance team's need to eliminate upfront capital expenditures for data centers and move to a consumption-based payment model.
This requirement aligns with trading fixed expense for variable expense.
AWS cloud computing turns upfront capital expenses (CapEx) into variable operating expenses (OpEx) where you pay only for what you use.
2
Analyze the IT operations team's need to avoid underprovisioning during peak traffic and overprovisioning during low traffic.
This requirement aligns with stopping guessing capacity.
By using elastic resources on AWS, capacity automatically adjusts to meet demand, removing the need to predict or guess system capacity requirements beforehand.

Key Concept

Define the benefits of the AWS Cloud
Estimated Time:1m 30s
Question 178Question →

A company is migrating its monolithic on-premises order-processing application to AWS. To handle unpredictable traffic spikes, they need to ensure the system is highly resilient to failures, can scale dynamically without human intervention, and prevents database performance bottlenecks from crashing the web frontend. Which of the following architectural strategies on AWS best implements these requirements while avoiding common cloud design anti-patterns?

Show answer & explanation

Answer: Deploy the frontend web servers across multiple Availability Zones within an Auto Scaling group, and use Amazon Simple Queue Service (SQS) to buffer writes to the database.

Answer

Deploy the frontend web servers across multiple Availability Zones within an Auto Scaling group, and use Amazon Simple Queue Service (SQS) to buffer writes to the database.
The correct strategy implements loose coupling by using Amazon SQS to decouple the database writes from the web frontend, designs for failure by deploying the web servers across multiple Availability Zones, and implements elasticity by using an Auto Scaling group to handle dynamic traffic spikes automatically.

Step-by-Step Solution

1
Analyze the resiliency requirement.
To ensure high resilience against failures, the application must be deployed across multiple Availability Zones (AZs) so that if one AZ fails, the others can continue operating.
This implements the 'design for failure' principle.
2
Analyze the scaling requirement.
To scale dynamically without human intervention, an Auto Scaling group should be used to automatically add or remove EC2 instances based on demand.
This implements the 'elasticity' principle, avoiding the anti-pattern of manual scaling.
3
Analyze the database bottleneck and decoupling requirement.
To prevent database bottlenecks from crashing the web frontend, a message queue like Amazon SQS must be introduced to buffer incoming requests and decouple the layers.
This implements the 'loose coupling' principle, ensuring that components are not tightly bound to each other's immediate performance.

Key Concept

AWS Cloud design principles (loose coupling, elasticity, and design for failure)
Question 179Question →

A company is building an online food delivery application on AWS. They want to ensure that if the payment service fails, the restaurant browsing and ordering service remains fully operational. Which AWS Cloud design principle is best demonstrated by this architectural choice?

Show answer & explanation

Answer: Loose coupling

Answer

Loose coupling
Loose coupling reduces dependencies between systems, ensuring that if one service fails, others continue to function. In this scenario, isolating the payment system from the browsing and ordering services allows customers to continue using the application even if payment processing is temporarily unavailable.

Step-by-Step Solution

1
Analyze the scenario
The scenario describes a system where one component (payment service) can fail without causing other components (restaurant browsing and ordering) to fail.
This is a key requirement of high availability and fault isolation.
2
Map the system behavior to AWS design principles
Separating components so they interact with minimal dependency is the definition of loose coupling.
Loose coupling prevents cascading failures and allows individual services to be updated or scale independently.

Key Concept

Loose coupling is a core design principle of the AWS Cloud that reduces dependencies between components, preventing single points of failure from disabling the entire system.
Question 180Question →

A digital publishing company is planning to migrate its content archive and seasonal traffic analytics systems from an on-premises data center to the AWS Cloud. The systems experience predictable, low baseline activity throughout the month, except for a 4848-hour window at the end of each month when monthly reports are generated and traffic spikes by 400%400\%. The company's goal is to minimize total cost of ownership (TCO) while ensuring performance during peak periods.

Which of the following strategies represent direct applications of AWS cloud economics to achieve these goals? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Implementing auto-scaling policies that dynamically provision compute capacity for the 4848-hour reporting spike and terminate the extra resources immediately afterward.; Converting upfront physical server acquisition costs into variable operating expenses, paying only for the compute runtime actually consumed.

Answer

The correct strategies are implementing auto-scaling policies to dynamically provision capacity during peak spikes, and converting upfront capital expenditures into variable operating expenses.
Implementing auto-scaling policies to dynamically provision capacity during peak spikes allows the company to pay only for the resource runtime they actually use, which leverages cloud elasticity. Converting upfront physical server acquisition costs into variable operating expenses shifts the financial risk from a capital expense model to an operational expense model, aligning costs directly with business demand.

Step-by-Step Solution

1
Analyze the workload characteristics and financial goals described in the scenario.
The workload has a low baseline with a predictable 4848-hour spike (400%400\% increase), and the goal is to optimize costs and minimize TCO.
Understanding the workload pattern is necessary to match it with the correct economic and operational strategies in AWS.
2
Evaluate the financial shifts associated with cloud migration.
Transitioning from purchasing physical hardware (CapEx) to paying for runtime hourly/secondly (OpEx) matches the goal of variable cost optimization.
Cloud economics favors trading capital expenses for variable operating expenses to increase financial agility.
3
Evaluate the technical scaling strategies for transient spikes.
Applying elasticity (scaling up and down dynamically) fits the 4848-hour spike, whereas permanent provisioning or long-term Reserved Instances for peak capacity are financially inefficient.
Elasticity prevents paying for idle resources, which directly reduces TCO compared to on-premises over-provisioning.

Key Concept

AWS Cloud Economics: CapEx to OpEx shift and the financial benefit of elasticity
PreviousPage 9 / 18Next
Cloud Concepts Practice Questions — AWS Certified Cloud Practitioner — Page 9 | Examkin