Examkin

Cloud Concepts

358 questions

All types358Multiple choice180Multiple select178
Question 261Question →

A financial technology company is migrating its application workloads to AWS. The Chief Financial Officer (CFO) wants to transition from paying large, upfront costs for physical hardware that depreciates over time to a pay-as-you-go model where expenses align directly with real-time resource consumption. Which benefit of the AWS Cloud is the CFO referring to?

Show answer & explanation

Answer: Trading capital expense for variable expense

Answer

Trading capital expense for variable expense
The benefit of trading capital expense for variable expense is demonstrated when a company moves from upfront hardware investments (Capital Expenditure, or CapEx) to a pay-as-you-go utility model (Operating Expenditure, or OpEx). This allows organizations to pay only for the resources they consume.

Step-by-Step Solution

1
Analyze the CFO's requirement to move from large, upfront hardware expenditures to a pay-as-you-go model based on consumption.
Identify that upfront hardware represents capital expenses (CapEx) and pay-as-you-go represents variable operational expenses (OpEx).
This sets the foundation for mapping the transition to the correct AWS Cloud benefit.
2
Evaluate the 6 benefits of AWS Cloud to find the one matching the transition from CapEx to OpEx.
The benefit 'Trading capital expense for variable expense' directly describes this shift.
This ensures the selected option corresponds exactly to official AWS Cloud Practitioner taxonomy.

Key Concept

Trading capital expense for variable expense allows businesses to pay only for the resources they consume, shifting upfront hardware investments to ongoing operational costs.
Estimated Time:1m 0s
Question 262Question →

A food delivery platform processes orders by executing a customer's payment and immediately transmitting the order details to the restaurant's kitchen terminal in a single, synchronous transaction. When a restaurant's internet connection drops, the kitchen terminal becomes unreachable, which causes the payment transaction to time out and fail. Which AWS Cloud design principle should the company apply to prevent kitchen connection issues from impacting the payment process, and how should it be implemented?

Show answer & explanation

Answer: Loose coupling; use an asynchronous messaging service to decouple the payment transaction from the kitchen order delivery process.

Answer

Loose coupling; use an asynchronous messaging service to decouple the payment transaction from the kitchen order delivery process.
Implementing loose coupling by introducing an asynchronous messaging service ensures that the payment process and the kitchen order delivery process operate independently. If the kitchen connection drops, the order details are safely buffered in the message queue, allowing the payment transaction to complete successfully without waiting for the kitchen terminal.

Step-by-Step Solution

1
Analyze the scenario to identify the system failure reason.
The failure is caused by a synchronous dependency where the payment transaction blocks while waiting for an external, unreliable network endpoint.
Understanding the root cause is necessary before selecting the appropriate design principle.
2
Apply the appropriate AWS Cloud design principle to break the dependency.
The principle of loose coupling indicates that systems should be designed with independent components so that a failure in one does not affect the others.
Decoupling allows the payment service to function independently of the kitchen terminal's network state.
3
Select the correct architectural pattern to implement the principle.
Introduce an asynchronous queue (such as Amazon SQS) to buffer the kitchen notifications, allowing the payment transaction to complete immediately.
This guarantees that payment processing remains highly available and orders are eventually delivered when the terminal reconnects.

Key Concept

Loose coupling and asynchronous messaging to prevent cascading failures in distributed systems.
Question 263Question →

A digital media agency runs containerized video rendering workloads on AWS. The workloads are highly unpredictable, with sudden bursts of activity when client campaigns launch. To optimize costs and efficiency, the agency utilizes Amazon Elastic Container Service (Amazon ECS) on AWS Fargate to automatically run containers only when rendering tasks are in the queue, shut them down immediately after completion, and avoid managing any underlying virtual machines.

Which AWS Cloud design principles are demonstrated by this architecture? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Services, not servers; Disposable resources

Answer

The architecture demonstrates the principles of 'Services, not servers' and 'Disposable resources'. By utilizing AWS Fargate, the company does not manage the underlying virtual servers, and by spinning containers up and down on demand, they treat compute resources as disposable assets rather than static systems.
The correct principles are using services, not servers, and treating resources as disposable. By deploying AWS Fargate, a serverless container execution engine, the agency does not have to manage underlying servers, directly applying the services, not servers principle. Additionally, running containers dynamically on demand and terminating them immediately when the job is done demonstrates the principle of disposable resources, where resources are treated as temporary rather than permanent.

Step-by-Step Solution

1
Analyze the technical requirements of the scenario.
The agency runs containerized rendering tasks on AWS Fargate on demand and shuts them down when finished, without managing virtual servers.
Understanding the actions taken helps identify which cloud design practices are in use.
2
Map the elimination of server management to AWS design principles.
Avoiding the management of underlying virtual machines by utilizing AWS Fargate maps to the 'Services, not servers' principle.
AWS Fargate is a serverless container engine that removes the operational burden of server maintenance.
3
Map the dynamic creation and termination of containers to AWS design principles.
Automatically running containers only when tasks exist and shutting them down immediately after completion maps to the 'Disposable resources' principle.
In the cloud, resources are treated as temporary assets (disposable) rather than fixed physical infrastructure.

Key Concept

AWS Cloud design principles recommend using managed and serverless services to reduce operational overhead (services, not servers) and treating compute resources as temporary, dynamic assets (disposable resources).
Estimated Time:1m 30s
Question 264Question →

A regional retail bakery chain is migrating its point-of-sale inventory system to AWS. By moving to the cloud, the bakery avoids purchasing expensive on-premises hardware upfront and instead pays a monthly bill based on actual resource consumption. Which economic transition does this scenario demonstrate?

Show answer & explanation

Answer: Replacing upfront capital expenditures with variable operational expenses

Answer

Replacing upfront capital expenditures with variable operational expenses
Moving to the cloud allows the business to replace capital expenditures (CapEx) for physical servers with variable operational expenses (OpEx) paid monthly.

Step-by-Step Solution

1
Identify the financial model of the on-premises setup described in the scenario.
Purchasing physical hardware upfront is classified as a capital expenditure (CapEx).
Capital expenditures are upfront investments in physical assets.
2
Identify the financial model of the AWS Cloud setup described in the scenario.
Paying a monthly bill based on actual consumption is classified as a variable operational expense (OpEx).
Operational expenses are day-to-day costs of running a business.
3
Combine these definitions to identify the correct transition.
The transition is from CapEx (upfront hardware cost) to OpEx (monthly pay-as-you-go cost).
This represents replacing upfront capital expenditures with variable operational expenses.

Key Concept

Understanding CapEx versus OpEx in cloud economics
Question 265Question →

Horizon Media Group plans to migrate its legacy on-premises content management system (CMS). To reduce operational overhead, the company decides to decommission the self-managed system and transition to a commercial third-party CMS subscription delivered as a Software-as-a-Service (SaaS) application. Which migration strategy is Horizon Media Group using for this transition?

Show answer & explanation

Answer: Repurchasing

Answer

Repurchasing
The correct strategy is Repurchasing. This strategy (also known as 'drop and shop') involves abandoning the existing legacy application and purchasing a license or subscription for a new product, commonly a Software-as-a-Service (SaaS) solution, to replace the old application.

Step-by-Step Solution

1
Analyze the migration scenario details.
The company is decommissioning its legacy on-premises CMS and transitioning to a commercial third-party CMS subscription delivered as Software-as-a-Service (SaaS).
To identify which of the 6 Rs migration strategies is being applied.
2
Compare the scenario against the definition of the 6 Rs migration strategies.
Decommissioning an application and replacing it with a SaaS subscription is the definition of Repurchasing.
To select the correct strategy and rule out other strategies like Rehosting, Replatforming, and Refactoring.

Key Concept

Repurchasing (Drop and Shop) Migration Strategy
Estimated Time:1m 0s
Question 266Question →

A local bookstore chain is migrating its inventory database and customer-facing web application from on-premises physical servers to the AWS Cloud. Which two of the following choices represent core cloud economics benefits of this migration?

Select all that apply

Show answer & explanation

Answer: Replacing upfront capital expenses for hardware with variable operating expenses.; Eliminating the need to estimate capacity needs by automatically scaling resources with customer demand.

Answer

Replacing upfront capital expenses for hardware with variable operating expenses, and eliminating the need to estimate capacity needs by automatically scaling resources with customer demand.
Replacing upfront capital expenses with variable operating expenses enables a pay-as-you-go financial model. Eliminating guess capacity requirements via elasticity optimizes cost by scaling down resources when they are not needed.

Step-by-Step Solution

1
Analyze the financial implications of shifting from on-premises infrastructure to the cloud.
Identify that the shift reduces upfront physical hardware investments (CapEx) in favor of pay-as-you-go services (OpEx).
This is a fundamental concept of cloud economics where businesses pay only for what they use.
2
Analyze how elasticity affects infrastructure sizing and cost optimization.
Identify that dynamic scaling removes the risk of under-provisioning or over-provisioning (guessing capacity).
Elasticity allows resource supply to match demand closely, maximizing cost efficiency.

Key Concept

Cloud Economics: CapEx to OpEx shift and Elasticity
Question 267Question →

A global logistics firm is migrating its package tracking system to the AWS Cloud. In the current on-premises architecture, a single database server and a single application server are tightly coupled. During peak shipping periods, database write bottlenecks cause the front-end portal to become completely unresponsive, resulting in lost transaction details. To improve system resilience and ensure messages are not lost, which of the following strategies align with the AWS Cloud design principles of loose coupling and designing for failure? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Introduce Amazon Simple Queue Service (Amazon SQS) to buffer incoming tracking updates before writing them to the database.; Deploy application instances across multiple Availability Zones behind an Elastic Load Balancer.

Answer

Introducing Amazon Simple Queue Service (Amazon SQS) to buffer incoming tracking updates before writing them to the database, and deploying application instances across multiple Availability Zones behind an Elastic Load Balancer.
The correct strategies are introducing Amazon Simple Queue Service (Amazon SQS) to buffer incoming tracking updates, which implements loose coupling, and deploying application instances across multiple Availability Zones behind an Elastic Load Balancer, which implements designing for failure.

Step-by-Step Solution

1
Analyze the current architectural bottlenecks and issues.
The current application is tightly coupled and lacks fault tolerance, meaning database overload crashes the entire system and causes data loss.
Identifying these failures points to the need for design principles that decouple services and create redundancy.
2
Select a solution that provides loose coupling to prevent database writes from directly impacting the frontend.
Using Amazon SQS allows message buffering, ensuring that frontend tracking updates are stored reliably even if the database database write speed lags.
Message queuing isolates components, allowing them to fail or scale independently.
3
Select a solution that designs for failure to ensure high availability.
Using Multi-AZ deployments with an Elastic Load Balancer ensures that if an instance or an entire zone fails, the system automatically redirects traffic to healthy resources.
Distributing resources across isolated infrastructure zones mitigates single points of failure.

Key Concept

AWS Cloud design principles state that loose coupling reduces interdependencies so that a failure in one component does not cascade, while designing for failure ensures system components have redundancy to survive infrastructure outages.
Estimated Time:1m 30s
Question 268Question →

Aegis Insurance Group is preparing to migrate its legacy on-premises IT portfolio to the AWS Cloud. During the portfolio discovery phase, the migration team identifies two distinct systems:

- System 1: A core underwriting application that will be completely rewritten to utilize a cloud-native, serverless architecture with AWS Lambda and Amazon DynamoDB.
- System 2: An old, redundant testing environment that is no longer used by any business unit and has no regulatory data retention requirements.

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

Select all that apply

Show answer & explanation

Answer: Refactoring System 1 to transition to a serverless architecture; Retiring System 2 since it is no longer required

Answer

The correct strategies are Refactoring for System 1 and Retiring for System 2.
Refactoring (or Re-architecting) is chosen when an application needs to be rebuilt from scratch to utilize cloud-native features, such as serverless compute and managed databases, which aligns with System 1. Retiring involves decommissioning applications and assets that are no longer useful or needed, which applies to the redundant test environment in System 2.

Step-by-Step Solution

1
Analyze the requirement for System 1.
System 1 is a core application being completely rewritten to use serverless services (AWS Lambda and Amazon DynamoDB) to achieve cloud-native scale. This architectural modification represents the Refactoring/Re-architecting strategy.
Identifying the correct strategy requires evaluating how much of the application architecture and code will be modified during migration.
2
Analyze the requirement for System 2.
System 2 is a redundant, unused testing environment with no compliance or data retention requirements. Decommissioning these assets represents the Retiring strategy.
Identifying assets that are no longer needed prevents unnecessary migration costs and efforts.
3
Select the correct combination of strategies.
The correct strategies are Refactoring for System 1 and Retiring for System 2.
These choices align with the 6 Rs framework definitions.

Key Concept

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

A smart agriculture startup processes high-resolution satellite imagery to predict crop yields. The company runs massive image-processing workloads for just one week at the end of each harvest season, requiring thousands of virtual compute instances. Throughout the rest of the year, they only run a small, low-traffic web dashboard. Additionally, because they do not have to buy, install, or maintain physical servers in a local facility, their engineering team focuses solely on developing machine learning models. Which two advantages of the AWS Cloud are directly demonstrated in this scenario? (Select TWO.)

Select all that apply

Show answer & explanation

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

Answer

The advantages 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 company avoids guessing capacity by dynamically scaling virtual instances to handle peak workload during the harvest season and scaling down afterward. They also avoid data center maintenance costs by not owning or maintaining physical servers, which lets them focus on development.

Step-by-Step Solution

1
Analyze the workload characteristics mentioned in the scenario.
The workload requires massive computing power (thousands of cores) for only one week per quarter, and very little power for the rest of the year.
Understanding the dynamic nature of the workload helps identify the capacity benefit.
2
Identify the AWS benefit related to these workload characteristics.
This aligns with 'Stop guessing capacity', as the company does not need to pre-purchase hardware for peak times.
Matching the scenario's workload flexibility with the AWS Cloud benefit of elastic capacity.
3
Analyze the operational characteristics regarding physical hardware.
The company does not have to buy, install, or maintain physical servers in a local facility.
Understanding the lack of physical server management requirements.
4
Identify the AWS benefit related to physical hardware management.
This aligns with 'Stop spending money running and maintaining data centers', allowing engineering teams to focus on core product delivery.
Matching the lack of physical facility management with the AWS Cloud benefit of offloading data center maintenance.

Key Concept

Define the benefits of the AWS Cloud
Question 270Question →

A boutique video production agency needs to expand its storage capacity for raw footage. Instead of purchasing expensive new physical storage hardware that requires upfront funding, the agency decides to use Amazon S3, allowing them to pay only for the storage they use on a monthly basis. Which concept of cloud economics does this spending shift demonstrate?

Show answer & explanation

Answer: Trading capital expenses (CapEx) for variable operating expenses (OpEx)

Answer

Trading capital expenses (CapEx) for variable operating expenses (OpEx)
The correct answer is trading capital expenses (CapEx) for variable operating expenses (OpEx). Capital expenses refer to upfront investments in physical assets like servers and storage arrays. By migrating to Amazon S3, the boutique video production agency avoids these upfront costs and instead pays a variable operating expense based on their actual monthly consumption.

Step-by-Step Solution

1
Analyze the business decision made by the boutique video production agency.
The agency is choosing not to purchase physical hardware upfront and instead paying monthly for storage resources actually used.
To classify the change in the company's financial model.
2
Map the spending models to cloud economic concepts.
Buying physical hardware represents a capital expense (CapEx), whereas paying monthly for consumption represents an operating expense (OpEx).
To determine which cloud economics concept describes shifting from upfront physical purchases to consumption-based pricing.

Key Concept

Trading Capital Expenses for Variable Expenses (CapEx vs OpEx)
Estimated Time:45s
Question 271Question →

Vanguard Logistics plans to migrate its legacy on-premises route optimization application to the AWS Cloud. The application currently runs on an outdated, unsupported Linux distribution. To minimize migration time while improving operational support, the company decides to migrate the application to Amazon EC2 instances running a modern, supported Amazon Linux operating system without modifying the core application code. Which cloud migration strategy is Vanguard Logistics using?

Show answer & explanation

Answer: Replatforming

Answer

Replatforming
Replatforming (also known as lift-tinker-and-shift) is correct because the company is making a minor optimization—upgrading the underlying operating system to a supported version—without changing the core architecture or code of the application.

Step-by-Step Solution

1
Analyze the migration scenario details
The application code remains unchanged, but the underlying operating system is upgraded to a supported version during the migration.
This establishes that the migration involves some modification at the platform level (operating system upgrade) but no modification to the core application code.
2
Map the observed changes to the 6 Rs migration strategies
Upgrading the operating system without changing the core application code is classified as Replatforming (lift-tinker-and-shift).
Rehosting preserves the operating system environment as-is, whereas Replatforming allows small changes (like OS or runtime upgrades) to meet platform compatibility and support requirements without full re-architecting.

Key Concept

Identifying AWS migration strategies (6 Rs), specifically distinguishing between Rehosting and Replatforming
Question 272Question →

A logistics company is struggling with the high costs of maintaining its physical server rooms, including electricity, cooling, and security staff. The company decides to migrate its package-tracking applications to AWS so that its IT team can focus on developing new route-optimization algorithms rather than managing infrastructure. Which benefit of the AWS Cloud is this company realizing?

Show answer & explanation

Answer: Stop spending money running and maintaining data centers

Answer

Stop spending money running and maintaining data centers
The correct answer is the option that states 'Stop spending money running and maintaining data centers'. By migrating to AWS, the logistics company no longer needs to manage the physical infrastructure, power, cooling, and security of on-premises server rooms. This allows the IT department to redirect its efforts toward activities that add direct business value, such as developing route-optimization algorithms.

Step-by-Step Solution

1
Analyze the company's problem in the scenario.
The company is spending resources on physical infrastructure operations, including cooling, power, and security staff for its server rooms.
Identifying the primary operational bottleneck helps map it to the correct AWS Cloud benefit.
2
Analyze the company's objective after migrating to AWS.
The company wants its IT team to focus on developing route-optimization algorithms instead of managing physical servers.
This shows the company is shifting effort from infrastructure management to core business value.
3
Match the scenario's outcome to the official AWS Cloud benefits.
By outsourcing the physical hosting environment to AWS, the company is realizing the benefit of stopping data center maintenance.
This matches the official AWS benefit: 'Stop spending money running and maintaining data centers' (which lets companies focus on projects rather than infrastructure heavy lifting).

Key Concept

AWS Cloud Benefit: Stop spending money running and maintaining data centers
Question 273Question →

A financial consulting firm is preparing to migrate its client portal to the AWS Cloud. The firm wants to understand how the migration will impact its spending and operational model.

Which of the following statements regarding the cloud economics of this migration are correct? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The migration allows the firm to trade upfront capital expenses (CapEx) for variable operating expenses (OpEx).; The total cost of ownership (TCO) is reduced by eliminating the cost of purchasing, powering, and maintaining physical servers.

Answer

Migrating to AWS allows the firm to trade upfront capital expenses (CapEx) for variable operating expenses (OpEx), and reduces the total cost of ownership (TCO) by eliminating the cost of purchasing, powering, and maintaining physical servers.
Migrating to AWS allows organizations to convert their financial model from capital expenditures (CapEx) to operating expenditures (OpEx), as they pay only for resources consumed rather than investing upfront in physical hardware. Furthermore, total cost of ownership (TCO) is reduced because the firm no longer needs to pay for the purchase, power, cooling, or maintenance of physical servers and data centers.

Step-by-Step Solution

1
Analyze how cloud migration shifts financial models.
Identify that cloud services convert capital expenses (CapEx) for hardware into variable operating expenses (OpEx).
This is a fundamental concept of cloud economics where businesses pay-as-they-go.
2
Analyze the impact on physical infrastructure costs.
Identify that total cost of ownership (TCO) decreases because physical servers and data centers are managed by AWS.
Eliminating physical hardware maintenance, power, and cooling directly lowers overall costs.

Key Concept

Shifting from CapEx to OpEx and reducing TCO through the elimination of physical infrastructure management.
Estimated Time:1m 0s
Question 274Question →

A genomics research institute runs high-performance DNA sequencing data analysis that requires 128 compute nodes for exactly 6 hours every Friday. For the rest of the week, the institute only needs 2 compute nodes to allow researchers to access historical data. Which of the following best describes the cloud economics benefit of running this workload on AWS rather than on-premises?

Show answer & explanation

Answer: The institute can leverage elasticity to pay for the 128 compute nodes only during the 6 hours of active analysis, avoiding the costs of idle on-premises infrastructure.

Answer

The institute can leverage elasticity to pay for the 128 compute nodes only during the 6 hours of active analysis, avoiding the costs of idle on-premises infrastructure.
The correct answer correctly identifies elasticity and the pay-as-you-go billing model. In an on-premises deployment, the institute would have to purchase and maintain 128 servers to handle the Friday workload, meaning 126 servers would sit idle and waste resources for the rest of the week. With AWS, the institute can scale up to 128 nodes for the 6 hours of processing and then scale back down to 2 nodes, paying only for the resources they consume.

Step-by-Step Solution

1
Analyze the workload demand pattern.
The workload has a highly variable demand pattern: 128 nodes for 6 hours a week (peak demand) and 2 nodes for the remaining 162 hours (baseline demand).
Understanding the ratio of peak-to-baseline usage helps identify whether elasticity and variable pricing will provide cost benefits.
2
Compare on-premises provisioning with AWS cloud economics.
On-premises requires purchasing and maintaining 128 nodes (CapEx) to support the peak workload, leaving 126 nodes idle for 96% of the week. AWS allows dynamic scaling and pay-as-you-go pricing (OpEx).
This shows the contrast between fixed capital expenditure for idle capacity versus variable operating expenditure for actual consumption.
3
Identify the key cloud concept that matches this scenario.
Elasticity is the ability to scale computing resources up and down easily to meet demand. Using elasticity ensures the institute only pays for peak capacity when it is actively used.
This links the workload requirements directly to the economic benefit of elasticity.

Key Concept

Cloud elasticity and pay-as-you-go pricing model vs. on-premises over-provisioning
Estimated Time:1m 30s
Question 275Question →

An online university hosting global certification exams experiences a massive surge in website traffic for exactly four hours during a monthly testing event. The university uses AWS Auto Scaling to automatically launch hundreds of Amazon EC2 instances to handle the exam traffic and subsequently terminates those instances when the testing window closes. Which AWS Cloud design principle is directly demonstrated by this dynamic adjustment of resources to match fluctuating demand?

Show answer & explanation

Answer: Elasticity

Answer

Elasticity
The correct answer is elasticity because the scenario highlights a system that dynamically expands capacity during traffic spikes and contracts capacity when demand decreases. Elasticity allows organizations to match supply with demand automatically, ensuring high availability while minimizing costs by only paying for the resources used.

Step-by-Step Solution

1
Analyze the scenario details.
The scenario describes a system that automatically adds instances to handle a temporary demand spike and then removes them (terminates them) when demand drops.
This establishes that we are looking for a cloud design principle focused on dynamic resource adjustment in both directions (scaling out and scaling in).
2
Differentiate between elasticity and scalability.
Scalability is the capability to handle growth, while elasticity is the capability to dynamically scale resources to match short-term fluctuations in demand, including reducing capacity when not needed.
Since the key cost-saving action is terminating instances when the event ends, elasticity is the most specific and correct principle.

Key Concept

AWS Cloud design principles: Elasticity
Question 276Question →

A marketing company launches promotional websites that are only active for a few weeks at a time. Instead of purchasing physical servers to host these websites, the company hosts them on AWS and pays only for the resources consumed during the campaigns. Which of the following cloud economics benefits is demonstrated in this scenario?

Show answer & explanation

Answer: Trading upfront capital expenses for variable operating expenses

Answer

Trading upfront capital expenses for variable operating expenses
The correct answer is correct because purchasing physical servers requires upfront investment, which is a capital expense (CapEx). Moving to AWS allows the company to pay only for resources consumed on an ongoing basis, shifting these costs to variable operating expenses (OpEx). This directly represents the benefit of trading capital expenses for variable expenses.

Step-by-Step Solution

1
Analyze the financial model of purchasing physical servers.
Purchasing physical servers requires significant upfront investment, which represents a Capital Expense (CapEx).
To understand the baseline on-premises cost model.
2
Analyze the financial model of paying for AWS resources on demand.
Paying only for virtual resources while they are active represents a variable Operating Expense (OpEx).
To identify how cloud services are billed.
3
Compare the transition between the two models.
The company trades the high upfront CapEx of buying servers for the flexible, variable OpEx of cloud resources.
To determine the cloud economics concept demonstrated.

Key Concept

Trading capital expenses for variable expenses
Estimated Time:45s
Question 277Question →

A digital publishing platform experiences highly variable web traffic, with sudden surges during breaking news events and minimal activity overnight. The platform owners want to migrate to AWS to avoid purchasing and maintaining physical servers sized for their peak traffic. Which of the following cloud economics concepts best explains how this migration helps the company optimize its infrastructure costs?

Show answer & explanation

Answer: Trading capital expenses for variable operating expenses, which allows the company to pay only for the compute resources it consumes.

Answer

Trading capital expenses for variable operating expenses, which allows the company to pay only for the compute resources it consumes.
The correct option describes the core cloud economics benefit of trading capital expenses (upfront hardware purchases) for variable operating expenses (paying only for resources used). This allows the platform to scale down during low-activity periods and avoid paying for idle capacity.

Step-by-Step Solution

1
Analyze the company's requirement to avoid upfront physical hardware costs for peak traffic.
Identify that purchasing hardware for peak capacity represents a Capital Expense (CapEx) where hardware is underutilized during low-traffic periods.
Understanding the baseline operational challenges of on-premises infrastructure is key to identifying the correct cloud economic benefit.
2
Evaluate the financial transition model when migrating to AWS.
AWS enables an Operating Expense (OpEx) model where costs are variable and scale directly with consumption.
Trading capital expenses for variable expenses is a core pillar of AWS cloud economics.

Key Concept

Trading capital expenses for variable expenses (CapEx to OpEx shift)
Estimated Time:1m 0s
Question 278Question →

An agricultural technology startup is deploying a crop monitoring platform that processes sensor data primarily during the three-month harvest season, with minimal activity during the rest of the year. The startup is deciding whether to purchase physical on-premises servers or migrate the workload to the AWS Cloud. Which TWO of the following represent cloud economics benefits of migrating this platform to AWS?

Select all that apply

Show answer & explanation

Answer: Replacing upfront capital expenditures (CapEx) for physical server hardware with variable operating expenditures (OpEx).; Eliminating costs for idle server capacity during the off-season by paying only for resources when they are actively used.

Answer

Migrating the platform to AWS allows the startup to replace upfront capital expenditures (CapEx) with variable operating expenditures (OpEx) and eliminate costs for idle server capacity during the off-season by paying only for resources when they are actively used.
The correct options describe the fundamental economic advantages of cloud computing for highly seasonal workloads. First, replacing upfront capital expenditures for hardware with variable operating expenditures allows the startup to avoid initial setup costs. Second, paying only for resources when they are actively used prevents the startup from paying for idle server capacity during the nine-month off-season.

Step-by-Step Solution

1
Analyze the workload characteristics of the startup.
The platform has highly seasonal demand, active for only 3 months of the year and idle for the remaining 9 months.
Understanding the usage pattern helps identify how elasticity and pay-as-you-go pricing apply.
2
Evaluate the financial benefits of the cloud model.
Avoiding upfront hardware purchases shifts the model from capital expenditure (CapEx) to operating expenditure (OpEx), and elasticity allows scaling down during the off-season.
These factors directly map to the core concepts of cloud economics.

Key Concept

Cloud Economics (CapEx vs. OpEx and Elasticity)
Question 279Question →

A smart home security startup wants to enable its development team to quickly build, test, and tear down experimental video analytics features. In their on-premises environment, procuring, installing, and configuring the required physical servers to test new features would take several weeks. By migrating to AWS, developers can provision and configure the necessary virtual servers and services in a few clicks, reducing setup time to minutes. Which benefit of the AWS Cloud is directly demonstrated by this scenario?

Show answer & explanation

Answer: Increase speed and agility

Answer

Increase speed and agility
The correct answer is the option stating 'Increase speed and agility'. The scenario describes the ability for developers to provision and configure resources in minutes instead of weeks, which directly aligns with AWS's definition of increasing speed and agility by making new IT resources only a click away.

Step-by-Step Solution

1
Analyze the business scenario provided in the question stem.
The startup needs to quickly set up and tear down environments for feature experimentation. AWS reduces this setup time from weeks to minutes.
Understanding the key pain point (slow infrastructure provisioning) and the resolution (rapid provisioning via AWS) helps identify the specific benefit demonstrated.
2
Map the scenario features to the six core AWS Cloud benefits.
Reducing resource availability time from weeks to minutes for developers is the definition of increasing speed and agility.
AWS explicitly defines 'Increase speed and agility' as reducing the time to make IT resources available to developers from weeks to minutes, making this the correct match.

Key Concept

AWS Cloud Benefit: Increase Speed and Agility
Estimated Time:1m 0s
Question 280Question →

A software company is planning to migrate its database workload to the AWS Cloud. Currently, database administrators spend several hours each week configuring database replication, managing operating system updates, and executing manual backups on local servers. To eliminate these tasks, the company decides to migrate to Amazon Aurora, allowing AWS to manage these operational responsibilities automatically.

Which AWS Cloud design principle does this decision directly represent?

Show answer & explanation

Answer: Services, not servers

Answer

Services, not servers
The correct answer is the option stating 'Services, not servers'. This AWS design principle encourages using managed services (such as Amazon Aurora) to reduce operational complexity. By choosing a managed database service, the organization delegates server maintenance, OS patching, and backups to AWS, freeing up internal teams to focus on core business applications.

Step-by-Step Solution

1
Analyze the operational requirements described in the scenario.
The company's database administrators are manually performing system-level administration tasks (OS patching, database backups, replication) on self-managed servers.
Understanding the current manual tasks helps identify the administrative overhead that needs to be eliminated.
2
Evaluate the proposed solution (migrating to Amazon Aurora).
Amazon Aurora is a fully managed relational database service that automates provisioning, patching, and backups.
Identifying the nature of the target service helps determine which cloud design principle applies.
3
Match the transition from self-managed servers to managed services with AWS Cloud design principles.
Using managed services instead of managing virtual servers directly aligns with the 'Services, not servers' design principle.
This confirms that the primary goal of the migration is to offload operational management to AWS.

Key Concept

The AWS Cloud design principle of choosing managed services over self-managed servers to reduce administrative overhead and operational effort.
PreviousPage 14 / 18Next
Cloud Concepts Practice Questions — AWS Certified Cloud Practitioner — Page 14 | Examkin