Examkin

Cloud Concepts

358 questions

All types358Multiple choice180Multiple select178
Question 181Question →

A quality assurance team at a financial software company currently maintains a permanent, always-on staging environment for testing weekly application updates. Because this environment is idle for most of the week, the team decides to use AWS CloudFormation to automatically spin up a brand new, identical staging environment at the start of a test run and completely destroy it once testing is complete. Which design principle of the AWS Cloud is directly demonstrated by this approach?

Show answer & explanation

Answer: Disposable resources

Answer

Disposable resources
The correct answer is the principle of disposable resources. In the AWS Cloud, infrastructure is treated as temporary and programmatically managed. Using tools like AWS CloudFormation to automatically spin up a staging environment for a test run and then terminating it immediately after completion directly applies the principle of disposable resources, helping to reduce costs and maintain clean test states.

Step-by-Step Solution

1
Analyze the scenario's operational goal.
The company wants to move away from a permanent, always-on staging environment to an on-demand, temporary environment that is programmatically created and destroyed using infrastructure as code (AWS CloudFormation).
Understanding the operational shift helps identify which architectural principle governs the lifecycle of these environments.
2
Map the team's approach to AWS Cloud design principles.
The practice of treating infrastructure as temporary and interchangeable assets that can be programmatically launched and terminated matches the principle of 'disposable resources' rather than maintaining static hardware.
This matches the definition of treating resources as disposable rather than fixed assets.

Key Concept

Disposable resources instead of fixed servers
Estimated Time:1m 0s
Question 182Question →

A logistics company, SwiftRoute Logistics, plans to migrate its on-premises package tracking application to the AWS Cloud. The migration team will move the application's web servers directly to Amazon EC2 instances without modification, but will transition its self-managed relational database to Amazon Relational Database Service (Amazon RDS) to eliminate database administration tasks. Which migration strategy is SwiftRoute Logistics using?

Show answer & explanation

Answer: Replatforming

Answer

Replatforming is the correct migration strategy because the company is migrating its application to the cloud while making minor optimizations—specifically moving the database to a managed service (Amazon RDS) to reduce management overhead—without altering the core application architecture or code.
The strategy described is replatforming (also known as lift-tinker-and-shift). In this scenario, the core application code is migrated to Amazon EC2 without changes, but the database is moved to a managed database service (Amazon RDS) to reduce administrative overhead. This optimization of a component without changing the core application structure is the defining characteristic of replatforming.

Step-by-Step Solution

1
Analyze the migration details for the application servers.
The web servers are moved directly to Amazon EC2 without modification (lift-and-shift).
To understand which parts of the application are migrated as-is.
2
Analyze the migration details for the database component.
The database is converted from a on-premises self-managed server to a managed database service (Amazon RDS) to reduce administrative efforts.
To identify any optimization or platform-level modifications.
3
Match the overall strategy to the AWS migration framework (6 Rs).
Combining lift-and-shift for servers with optimization of the database using a managed service represents Replatforming (lift-tinker-and-shift).
To select the migration strategy that aligns with these activities.

Key Concept

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

A media company is migrating its video transcoding pipeline to AWS. The solution architect designs the system to use Amazon S3 to store raw uploads, which triggers an AWS Lambda function to process the video. The processed videos are then stored in a different S3 bucket. Additionally, the Lambda functions automatically scale out to handle thousands of concurrent uploads during peak hours and scale down to zero when there is no activity.

Which two design principles of the AWS Cloud does this architecture represent? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Services, not servers; Elasticity

Answer

The correct design principles are 'Services, not servers' and 'Elasticity'.
The architecture demonstrates 'services, not servers' by utilizing fully managed services like Amazon S3 and AWS Lambda, which eliminates the need to provision or manage servers. It also demonstrates 'elasticity' because AWS Lambda automatically scales out to match the incoming demand of video uploads and scales back down when demand decreases.

Step-by-Step Solution

1
Identify the compute and storage resources used in the scenario and how they are managed.
The architecture uses Amazon S3 and AWS Lambda, which are fully managed services requiring no server provisioning or maintenance.
This identifies the 'services, not servers' design principle.
2
Analyze how the system handles changes in demand and workload.
The system automatically scales up to handle thousands of uploads and scales down to zero when idle.
This identifies the 'elasticity' design principle, which is the ability to scale dynamically based on demand.

Key Concept

AWS Cloud Design Principles focus on loose coupling, elasticity, and utilizing managed services to reduce operational overhead.
Estimated Time:1m 30s
Question 184Question →

An independent software vendor (ISV) is transitioning its application from a traditional on-premises hosting model to AWS. Under the old model, the ISV had to invest heavily in purchasing physical servers and storage arrays before launch to ensure the application could support its projected user base. On AWS, the ISV plans to deploy resources on-demand and scale them dynamically. Which option correctly identifies the primary AWS Cloud benefit demonstrated by this shift, along with the correct financial or operational rationale?

Show answer & explanation

Answer: Trading capital expense for variable expense, which allows the ISV to pay only for the resources they consume rather than investing heavily in physical data centers and servers before using them.

Answer

Trading capital expense for variable expense, which allows the ISV to pay only for the resources they consume rather than investing heavily in physical data centers and servers before using them.
The correct option is correct because the ISV is shifting from upfront investments in physical infrastructure (capital expenses) to a model where they pay for resources on-demand (variable expenses). This directly matches the AWS Cloud benefit of trading capital expense for variable expense.

Step-by-Step Solution

1
Analyze the resource procurement shift in the scenario.
The ISV moves from upfront purchasing of physical hardware (servers and storage arrays) to on-demand provisioning on AWS.
Understanding the transition from fixed upfront physical assets to pay-as-you-go computing is necessary to determine the financial shift.
2
Map the transition to the defined benefits of the AWS Cloud.
Shifting from upfront hardware investments to paying only for actual resource consumption aligns with the benefit of trading capital expense for variable expense.
This identifies the specific core benefit that addresses the financial optimization described.
3
Verify each option against the official definitions of AWS benefits and design principles.
The correct option outlines this exact trade-off. The incorrect options misidentify economies of scale, reverse the cost trade-off direction, or misapply design principles like loose coupling.
Ensures the selected option is factually accurate and that all distractors are based on distinct misconceptions.

Key Concept

Trading capital expense for variable expense allows organizations to avoid heavy upfront hardware costs and instead pay only for what they consume, shifting costs from CapEx to OpEx.
Estimated Time:2m 0s
Question 185Question →

A startup is developing a mobile application backend. The company wants to focus on writing application code and delivering features without spending time on provisioning, patching, or managing operating systems. To achieve this, they select AWS Lambda for compute and Amazon DynamoDB for database storage. Which AWS Cloud design principle is best demonstrated by this architectural decision?

Show answer & explanation

Answer: Services, not servers

Answer

Services, not servers
The correct answer is the principle of using managed services rather than managing servers. By selecting serverless and fully managed services like AWS Lambda and Amazon DynamoDB, the startup avoids the complexity and effort of operating system maintenance, patching, and server provisioning, allowing them to focus strictly on code.

Step-by-Step Solution

1
Analyze the requirement of the startup.
The startup wants to avoid the operational overhead of provisioning, patching, and maintaining servers.
This points to offloading infrastructure management tasks.
2
Evaluate the selected AWS services (AWS Lambda and Amazon DynamoDB).
Both AWS Lambda and Amazon DynamoDB are fully managed, serverless services that do not require server administration.
This aligns with using managed offerings rather than running virtual machines.
3
Match the architectural choice with the corresponding AWS Cloud design principle.
The selection matches the principle of using services rather than servers.
The 'Services, not servers' principle advises leveraging managed services to reduce operational complexity.

Key Concept

Services, not servers design principle
Question 186Question →

Zenith Retail is planning the migration of its application portfolio to the AWS Cloud. During the discovery phase, the team identifies a legacy mainframe application that is highly customized and runs critical accounting processes. Due to its complexity and the lack of an immediate business case for migration, the company decides to keep this application running in their on-premises data center for now. Which cloud migration strategy is Zenith Retail using for this mainframe application?

Show answer & explanation

Answer: Retaining

Answer

Retaining
The correct answer is Retaining. This strategy involves keeping applications in their current on-premises environment instead of migrating them to the cloud. This is typically chosen for legacy workloads that are highly customized, complex, or lack a business case for immediate migration.

Step-by-Step Solution

1
Analyze the scenario to determine the fate of the legacy mainframe application.
The application is highly customized, runs critical processes, and Zenith Retail decides to keep it running in their on-premises data center for now.
Understanding the target action (keeping the application on-premises) is key to selecting the correct migration strategy.
2
Match the decision of keeping the application on-premises to the correct AWS 6 Rs migration strategy.
This corresponds to the Retaining strategy.
Retaining is defined as keeping applications in their source environment, often due to complexity or pending deprecation/migration plans.

Key Concept

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

A retail business operates an e-commerce application on AWS. During peak shopping hours, the application requires 20 Amazon EC2 instances to handle the traffic, but during off-peak hours, only 4 instances are needed. The infrastructure team uses Amazon EC2 Auto Scaling to dynamically launch and terminate instances in response to the real-time load. Which AWS Cloud design principle is best illustrated by this scenario?

Show answer & explanation

Answer: Elasticity

Answer

Elasticity
The design principle of elasticity focuses on matching resource allocation with actual demand. In this scenario, dynamically provisioning 20 instances during peak hours and scaling down to 4 instances during off-peak hours ensures the system is cost-effective and performs well without over-provisioning.

Step-by-Step Solution

1
Analyze the scenario details.
The scenario describes a system that automatically adds resources (scaling up to 20 instances) when demand is high and removes them (scaling down to 4 instances) when demand is low.
To identify the specific cloud behavior described.
2
Match the behavior to AWS cloud design principles.
The ability to dynamically scale resources both up and down to match demand is the definition of elasticity.
To select the correct design principle from the options.

Key Concept

Elasticity versus Scalability in cloud design principles
Question 188Question →

GlowCare Cosmetics plans to migrate its on-premises relational database to Amazon Relational Database Service (Amazon RDS) to reduce database administration tasks. The company wants to complete this transition quickly without changing its core application architecture or rewriting its code. Which cloud migration strategy is the company using?

Show answer & explanation

Answer: Replatforming

Answer

Replatforming
The correct strategy is Replatforming. Replatforming involves making minor optimizations, such as migrating a self-managed database to a fully managed service like Amazon RDS, to reduce administrative tasks without changing the core application code or architecture.

Step-by-Step Solution

1
Analyze the migration target in the scenario.
The target is migrating an on-premises database to Amazon RDS, a managed service.
This establishes that an optimization (moving to a managed service) is being made to reduce administrative work.
2
Identify constraints on the code and architecture.
The company does not plan to change its core application architecture or rewrite any code.
This rules out refactoring or re-architecting, which requires code modifications.
3
Match the scenario to the correct migration strategy.
Migrating to a managed service without changing core application code is known as Replatforming.
Replatforming is the strategy that involves minimal modifications ('tinkering') to achieve cloud benefits, such as moving to a managed database.

Key Concept

AWS Cloud Migration Strategies (6 Rs) - Replatforming vs. Rehosting vs. Refactoring
Estimated Time:1m 0s
Question 189Question →

A smart grid utility operator runs complex grid-reliability simulations once a week. This process requires a large amount of compute capacity for a 6-hour window, but the infrastructure remains completely idle for the rest of the week. Currently, the company maintains an on-premises data center sized to handle this peak load, incurring high upfront costs, virtualization licensing, power, and cooling fees. Which of the following best describes the primary economic driver and financial shift of migrating this simulation workload to AWS?

Show answer & explanation

Answer: Transitioning from capital expenses (CapEx) to operating expenses (OpEx), allowing the company to leverage AWS elasticity and pay only for compute resources during the active simulation window.

Answer

Transitioning from capital expenses (CapEx) to operating expenses (OpEx), allowing the company to leverage AWS elasticity and pay only for compute resources during the active simulation window.
Transitioning from capital expenses (CapEx) to operating expenses (OpEx) is a core benefit of AWS. By leveraging AWS elasticity, the utility only incurs costs when the simulations run, eliminating the overhead of idle infrastructure.

Step-by-Step Solution

1
Analyze the workload's resource usage pattern.
The workload requires high compute capacity for 6 hours once a week, remaining idle for the other 162 hours of the week.
Identifying the pattern helps determine the appropriate cloud architecture and pricing model.
2
Evaluate the financial shift of cloud migration.
Moving away from owning and maintaining physical data centers shifts expenses from Capital Expenses (CapEx) to Operating Expenses (OpEx).
This is a fundamental concept of cloud economics where fixed upfront costs are replaced by variable expenses.
3
Apply the principle of cloud elasticity to the workload.
By scaling down resources to zero during the idle hours, the company only pays for the active 6 hours of simulation runtime.
Elasticity ensures cost optimization by aligning resource provisioning directly with real-time demand.

Key Concept

Concepts of Cloud Economics (CapEx vs OpEx and Elasticity)
Question 190Question →

A regional hospital network is planning to migrate its patient medical imaging archive and processing system to AWS. The network currently maintains physical storage arrays and server hardware on-premises, requiring significant upfront capital investments and ongoing facility maintenance. The imaging archive grows steadily, but the processing demand peaks predictably during daytime clinic hours and drops significantly at night. The network wants to align its infrastructure costs with actual usage and minimize capital expenditures (CapEx).

Which two strategies should the network implement to achieve these cloud economics goals?

Select all that apply

Show answer & explanation

Answer: Replacing upfront physical server purchases with a pay-as-you-go pricing model for compute and storage resources.; Deploying elastic resources that automatically scale down during night hours to match the reduced demand.

Answer

The correct strategies are replacing upfront physical server purchases with a pay-as-you-go pricing model, and deploying elastic resources that automatically scale down during night hours.
Replacing upfront physical server purchases with a pay-as-you-go model shifts capital expenses to operating expenses. Furthermore, deploying elastic resources that scale down at night aligns capacity with actual usage, minimizing waste and reducing the Total Cost of Ownership (TCO).

Step-by-Step Solution

1
Analyze the financial objective of minimizing capital expenditures (CapEx).
Determine that shifting from physical hardware acquisition (CapEx) to a pay-as-you-go consumption model (OpEx) fulfills this goal.
On-premises infrastructure requires large upfront investments, whereas AWS allows paying for resources as they are consumed, eliminating upfront CapEx.
2
Analyze the operational objective of aligning costs with actual usage.
Determine that resources should dynamically scale down when demand drops at night rather than running at peak levels constantly.
By using elasticity to match capacity with variable demand, the organization avoids paying for idle resources during off-peak hours.

Key Concept

Cloud economics benefits, specifically the shift from CapEx to OpEx and the utilization of elasticity to reduce TCO.
Question 191Question →

A digital marketing firm is moving its media processing application to the AWS Cloud. The application currently processes video uploads in a sequential manner, where a failure in the rendering module causes the upload module to stop responding. To address this, the firm wants to modernize the architecture using AWS Cloud design principles to improve resilience and cost efficiency.

Which design decisions should the firm implement to achieve these goals? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Implement an Amazon Simple Queue Service (Amazon SQS) queue to decouple the front-end upload interface from the back-end rendering service; Use Amazon EC2 Auto Scaling to dynamically provision and terminate rendering instances based on the volume of videos in the queue

Answer

Implementing an Amazon Simple Queue Service (Amazon SQS) queue to decouple the front-end upload interface from the back-end rendering service, and using Amazon EC2 Auto Scaling to dynamically provision and terminate rendering instances based on the volume of videos in the queue.
Implementing an Amazon SQS queue ensures the front-end upload interface and the rendering backend are decoupled, allowing them to scale and fail independently (loose coupling). Integrating Amazon EC2 Auto Scaling based on queue size allows capacity to automatically adjust to demand, ensuring both performance and cost-efficiency (elasticity).

Step-by-Step Solution

1
Analyze the architectural requirements for resilience and cost efficiency.
Identified that the application has a tight dependency between upload and rendering modules (needs loose coupling to improve resilience) and variable workload peaks (needs elasticity to optimize costs).
This establishes which design principles must be targeted to solve the issues described in the scenario.
2
Select options that match the required design principles.
Using Amazon SQS decouples the modules (loose coupling), and using Amazon EC2 Auto Scaling dynamically adjusts rendering instances (elasticity).
These choices implement cloud-native architectures that replace tightly coupled infrastructure with scalable, decoupled systems.

Key Concept

AWS Cloud Design Principles: Loose Coupling and Elasticity
Question 192Question →

A company is migrating its web application to AWS. To handle unpredictable changes in user demand, the company configures the application to automatically scale its compute resources up and down. Additionally, the company decides to use Amazon DynamoDB, a fully managed database service, instead of installing and maintaining database software on EC2 instances. Which of the following design principles of the AWS Cloud is the company implementing? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Elasticity; Services, not servers

Answer

The company is implementing the principles of Elasticity and Services, not servers.
The startup implements elasticity by configuring the application to automatically scale its compute resources in response to real-time demand. It also implements the 'services, not servers' principle by leveraging Amazon DynamoDB, a fully managed service, which eliminates the administrative burden of provisioning and managing virtual servers.

Step-by-Step Solution

1
Analyze the automatic scaling behaviour.
The application automatically scales resources up and down to match demand. This maps directly to the principle of Elasticity.
Elasticity is the ability to acquire resources as you need them and release them when you don't.
2
Analyze the choice of database service.
The company chose a managed database service (Amazon DynamoDB) instead of running the database software on EC2 instances. This maps to the principle of Services, not servers.
Using managed services allows organizations to focus on application development rather than server maintenance.

Key Concept

AWS Cloud Design Principles: Elasticity and Services, not servers
Question 193Question →

AeroTemp Solutions, a weather forecasting startup, wants to migrate its legacy monolithic weather prediction application to the AWS Cloud. The startup's primary goal is to fully leverage cloud-native features, such as serverless computing and auto-scaling, to handle sudden spikes in weather data processing. To achieve this, the IT team decides to completely redesign the application architecture, breaking the monolith into independent microservices using AWS Lambda and Amazon DynamoDB. Which cloud migration strategy is AeroTemp Solutions employing?

Show answer & explanation

Answer: Refactoring

Answer

Refactoring
Refactoring (also known as re-architecting) is the migration strategy where an application is reimagined and rewritten to run on a cloud-native architecture. In this scenario, breaking the monolith into serverless microservices using AWS Lambda and Amazon DynamoDB represents a complete architectural redesign, which is characteristic of Refactoring.

Step-by-Step Solution

1
Analyze the organization's requirements and migration plans.
The startup wants to break their monolithic application into microservices using serverless technologies (AWS Lambda and Amazon DynamoDB).
Identifying the planned actions helps determine which migration strategy is being used.
2
Map the migration actions to the 6 Rs migration strategies.
Completely redesigning and rewriting the application to use cloud-native services aligns with Refactoring (Re-architecting).
Comparing the actions against the definitions of the migration strategies leads to the correct classification.

Key Concept

Cloud migration strategies (6 Rs)
Estimated Time:1m 0s
Question 194Question →

An educational technology (EdTech) company is launching a new online learning platform. The platform experiences high traffic during school exams and very low traffic during holidays. The company wants to leverage the AWS Cloud to handle these traffic variations efficiently while minimizing costs. Which two of the following are benefits of the AWS Cloud that directly address this scenario? (Select TWO.)

Select all that apply

Show answer & explanation

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

Answer

The benefits of stopping guessing capacity and trading fixed expense for variable expense
The correct benefits are stopping guessing capacity and trading fixed expense for variable expense. Stopping guessing capacity allows the e-learning platform to scale dynamically as traffic spikes or drops. Trading fixed expense for variable expense means the company only pays for active usage during exam seasons rather than paying upfront for servers that sit idle during school holidays.

Step-by-Step Solution

1
Analyze the scenario details, focusing on fluctuating traffic (high during exams, low during holidays) and the desire to optimize costs.
Identify that the solution must support scaling resources up and down dynamically based on demand, and changing the billing model to only pay for active consumption.
This links the scenario needs directly to AWS Cloud benefits.
2
Evaluate which AWS Cloud benefits address dynamic scaling.
'Stop guessing capacity' is the direct benefit representing elasticity, allowing automatic scaling in response to traffic changes.
Elasticity eliminates the need to overprovision hardware for peak periods.
3
Evaluate which AWS Cloud benefits address the payment structure.
'Trade fixed expense for variable expense' allows paying only for what is consumed.
This replaces capital expenses (CapEx) with operational expenses (OpEx).

Key Concept

Benefits of AWS Cloud (Elasticity and Cost Optimization)
Question 195Question →

A mobile game studio wants to launch weekly experimental feature trials to gather player feedback. In their traditional on-premises environment, developers must wait several weeks for the IT department to procure and configure new physical server hardware for each test. By migrating to the AWS Cloud, the studio can now launch and terminate virtual servers in minutes, significantly reducing the cost and time required for experimentation.

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'. In a cloud computing environment, new IT resources are just a click away, which reduces the time it takes to make those resources available to developers from weeks to minutes. This dramatically increases agility for the organization, as the cost and time to experiment and develop are significantly lower.

Step-by-Step Solution

1
Analyze the business scenario described in the stem.
The game studio is transitioning from a weeks-long hardware procurement process to launching and terminating virtual servers within minutes to run experiments.
Understanding the core problem (slow provisioning vs. fast provisioning) helps map it to the correct AWS Cloud benefit.
2
Compare the scenario characteristics with the definition of 'Increase speed and agility' in AWS.
AWS defines 'Increase speed and agility' as having IT resources only a click away, reducing the time to make those resources available to developers from weeks to minutes, which lowers the cost and time to experiment.
This matches the scenario's focus on rapid provisioning for experimentation and development.

Key Concept

AWS Cloud Benefit: Increase speed and agility
Estimated Time:1m 0s
Question 196Question →

A global logistics and maritime transport enterprise is expanding its shipment tracking application to customers in Asia, Europe, and South America. Historically, this expansion would require the company's IT staff to negotiate real estate leases for colocation facilities, purchase physical servers, and manage local power infrastructure in each region. By migrating to AWS, the company can deploy its application across multiple global locations with a few clicks and redirect its engineering resources from server maintenance to logistics software innovation.

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

Select all that apply

Show answer & explanation

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

Answer

The correct answers are the benefits of going global in minutes and stopping spending money running and maintaining data centers.
The correct options are the benefits of going global in minutes and stopping spending money running and maintaining data centers. The global deployment across multiple continents with minimal effort illustrates going global in minutes. Getting rid of physical server procurement, leasing, and power management demonstrates stopping spending money running and maintaining data centers.

Step-by-Step Solution

1
Identify the geographic aspects of the deployment described in the scenario.
The tracking application is deployed across Asia, Europe, and South America with a few clicks.
This maps directly to the benefit of going global in minutes.
2
Identify the infrastructure management shifts described in the scenario.
The company stops managing physical server racks, power infrastructure, and real estate leases.
This maps directly to stopping spending money running and maintaining data centers, allowing engineers to focus on business innovation.

Key Concept

The six benefits of AWS Cloud, focusing on global deployment capabilities and the outsourcing of physical data center management.
Question 197Question →

A digital publishing organization is optimizing its content delivery platform. The organization plans to replace its self-managed caching clusters with a fully managed caching service. Additionally, they plan to use infrastructure templates to automatically deploy identical, short-lived staging environments that are destroyed after testing is complete.

Which of the following design principles are demonstrated by these architectural choices? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Leveraging managed services to reduce the operational overhead of server administration; Defining infrastructure as disposable resources that can be easily recreated using automation

Answer

Leveraging managed services to reduce operational overhead, and defining infrastructure as disposable resources that can be easily recreated using automation.
The correct architectural choices demonstrate utilizing managed services to remove server administration tasks and implementing disposable resources via automated infrastructure templates.

Step-by-Step Solution

1
Analyze the first architectural change: replacing self-managed caching clusters with a fully managed caching service.
Identified the design principle of prioritizing managed services over running and managing servers directly, which lowers operational administration.
This shows shift of operational responsibility to AWS.
2
Analyze the second architectural change: using templates to deploy identical, short-lived staging environments that are destroyed after testing.
Identified the design principle of treating resources as disposable assets that can be easily created and destroyed through automation.
This prevents configuration drift and avoids paying for idle resources.

Key Concept

AWS Cloud design principles focus on automating infrastructure deployment as disposable assets and leveraging managed services to shift operational burdens.
Question 198Question →

An online media company notices that its monthly AWS billing rates for data storage have periodically decreased over time, even though the company's own storage usage has remained constant. AWS is able to pass these savings on to customers due to the aggregated usage of hundreds of thousands of customers. Which benefit of the AWS Cloud does this scenario describe?

Show answer & explanation

Answer: Benefit from massive economies of scale

Answer

Benefit from massive economies of scale
The correct answer is the option indicating that the customer benefits from massive economies of scale. Because AWS aggregates usage from hundreds of thousands of customers, it can achieve higher economies of scale. This scale translates into savings that AWS passes back to customers in the form of lower pay-as-you-go prices.

Step-by-Step Solution

1
Analyze the business scenario described in the question stem.
The scenario focuses on general price drops passed down to customers because of AWS's aggregate usage from hundreds of thousands of customers.
To identify which cloud benefit allows AWS to offer lower unit rates as its customer base grows.
2
Compare the scenario details with the definition of AWS Cloud benefits.
The concept of passing savings from high-volume operations down to individual customers aligns exactly with 'Benefit from massive economies of scale'.
To select the correct option that matches the identified cloud benefit.

Key Concept

Benefit from massive economies of scale
Estimated Time:45s
Question 199Question →

Veloce Automotive is migrating its infrastructure to the AWS Cloud. The migration team has identified two workloads:

1. A third-party inventory system that will be replaced by purchasing a software-as-a-service (SaaS) application from the AWS Marketplace.
2. A critical legacy web server that must be moved to Amazon EC2 immediately with zero modifications to the application code or configuration.

Which two AWS migration strategies describe the paths chosen for these workloads?

Select all that apply

Show answer & explanation

Answer: Repurchasing; Rehosting

Answer

Repurchasing and Rehosting are the correct strategies.
Repurchasing is the correct strategy for the third-party inventory system because it is replaced by buying a Software-as-a-Service (SaaS) application. Rehosting is correct for the legacy web server because the server is moved to Amazon EC2 as-is with no modifications, which represents a lift-and-shift approach.

Step-by-Step Solution

1
Analyze the requirement for the first workload: replacing a COTS system with a SaaS application from the AWS Marketplace.
This is identified as the Repurchasing strategy.
Repurchasing involves dropping the existing software license and purchasing a SaaS-based version of the tool.
2
Analyze the requirement for the second workload: moving a legacy web server to EC2 with zero modifications.
This is identified as the Rehosting strategy.
Rehosting, or lift-and-shift, involves migrating workloads directly to the cloud without modifying code or configuration.

Key Concept

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

PixelForge Studios is planning to migrate its operations to the AWS Cloud. The IT team has categorized two of their workloads for migration:

First, they will replace their self-managed on-premises human resources (HR) application with a third-party Software-as-a-Service (SaaS) solution available on the AWS Marketplace.

Second, they will move their web application's underlying MySQL database to Amazon Relational Database Service (Amazon RDS) to eliminate database administration tasks, while leaving the application code unchanged.

Which two of the following AWS Cloud migration strategies describe these plans? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Repurchasing; Replatforming

Answer

The correct strategies are Repurchasing and Replatforming.
The correct strategies are Repurchasing and Replatforming. Replacing the legacy HR application with a third-party Software-as-a-Service (SaaS) solution corresponds to a Repurchasing strategy (sometimes referred to as drop-and-shop). Moving the database to a managed service like Amazon Relational Database Service (Amazon RDS) to eliminate database administration tasks while keeping the core application code intact represents a Replatforming strategy (also known as lift-tinker-and-shift).

Step-by-Step Solution

1
Analyze the first migration workload: replacing the on-premises HR application with a third-party SaaS solution on AWS Marketplace.
Identify this as the Repurchasing strategy, which involves transitioning to a different product or platform (often SaaS) and purchasing licenses.
The defining characteristic of Repurchasing is moving from a self-managed product to a SaaS model.
2
Analyze the second migration workload: moving the MySQL database to Amazon RDS to reduce management overhead without altering application code.
Identify this as the Replatforming strategy, where minor optimizations are made to leverage cloud-managed services without redesigning the core application architecture.
Migrating a database to a managed service like Amazon RDS without modifying code is a classic replatforming scenario.

Key Concept

AWS Cloud Migration strategies (6 Rs)
Estimated Time:1m 30s
PreviousPage 10 / 18Next
Cloud Concepts Practice Questions — AWS Certified Cloud Practitioner — Page 10 | Examkin