Examkin

Cloud Concepts

358 questions

All types358Multiple choice180Multiple select178
Question 81Question →

A news streaming startup wants to launch its application to users in Europe, Asia, and North America. By using AWS, they deploy their application's resources across multiple AWS Regions worldwide in a matter of minutes to ensure low-latency access for all users. Which benefit of the AWS Cloud is this startup directly utilizing?

Show answer & explanation

Answer: Go global in minutes

Answer

Go global in minutes
The correct answer is the option stating 'Go global in minutes'. AWS allows customers to easily deploy applications in multiple Regions around the world with just a few clicks. This enables businesses to provide lower latency and a better user experience for their customers at a minimal cost.

Step-by-Step Solution

1
Analyze the business scenario
The startup needs to deploy applications globally across Europe, Asia, and North America quickly and with low latency.
Identifying key constraints and goals (multi-region, speed, low latency) helps align with AWS cloud benefits.
2
Map the goal to AWS Cloud benefits
Deploying globally in a few clicks to multiple regions represents 'Go global in minutes'.
AWS global infrastructure allows rapid deployment across regions, matching the 'Go global in minutes' benefit.

Key Concept

Go global in minutes
Question 82Question →

A financial services startup is planning to launch a new algorithmic trading simulation platform. The platform experiences massive, unpredictable traffic spikes during market hours (9:30 AM9:30\text{ AM} to 4:00 PM4:00\text{ PM} EST) but is virtually idle at night. Additionally, the startup must perform a weekly risk analysis batch job every Sunday, which requires high-performance compute resources for exactly 33 hours and can be interrupted without losing progress. The startup wants to optimize its cost structure by shifting capital expenditures (CapEx) to operating expenditures (OpEx) while maximizing the cost benefits of cloud economics.

Which two AWS billing and architectural strategies will best align with the company's financial goals of reducing Total Cost of Ownership (TCO) and leveraging the economic benefits of elasticity? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Designing the trading simulation platform to dynamically scale compute instances up and down using Amazon EC2 Auto Scaling based on real-time demand metrics.; Utilizing Amazon EC2 Spot Instances to run the weekly risk analysis batch jobs.

Answer

The correct strategy involves scaling the trading platform dynamically using Amazon EC2 Auto Scaling and running the interruptible weekly risk analysis batch jobs on Amazon EC2 Spot Instances.
Leveraging Amazon EC2 Auto Scaling allows the platform to scale dynamically during unpredictable peak market hours and scale down to minimum capacity at night, optimizing operational costs (OpEx) through elasticity. Utilizing Amazon EC2 Spot Instances for the weekly risk analysis batch job is highly cost-effective because the job can tolerate interruptions, letting the startup take advantage of spare AWS capacity at deep discounts.

Step-by-Step Solution

1
Analyze the platform's traffic pattern and identify the elasticity requirements.
The platform has highly variable demand (9:30 AM9:30\text{ AM} to 4:00 PM4:00\text{ PM} peak, idle at night), indicating a strong need for elasticity to match resource supply with demand.
Elasticity prevents paying for idle resources during off-peak times.
2
Evaluate the weekly risk analysis workload characteristics.
The batch job is weekly, runs for 33 hours, and is interruptible, making it a perfect fit for EC2 Spot Instances.
Spot Instances offer up to 90%90\% cost reduction for fault-tolerant workloads.
3
Assess the financial goal of shifting CapEx to OpEx.
Avoid options that require upfront payments or long-term capacity lock-in (such as 3-Year All Upfront Dedicated Host Reserved Instances).
Upfront reservations behave like capital expenses, reducing financial flexibility.
4
Identify the combinations of decisions that optimize Total Cost of Ownership (TCO) and support elasticity.
Combining Auto Scaling for variable traffic and Spot Instances for interruptible batch jobs maximizes the economic benefits of the cloud.
This combination minimizes runtime costs and eliminates capital expenditures.

Key Concept

Shifting CapEx to OpEx, leveraging Spot instances for fault-tolerant batch workloads, and using Auto Scaling to achieve elasticity.
Question 83Question →

A food delivery platform wants to prevent an outage in its payment processing component from causing the entire ordering application to crash. Which AWS Cloud design principle should the platform implement to achieve this?

Show answer & explanation

Answer: Loose coupling

Answer

Loose coupling
Loose coupling ensures that application components are independent. In this scenario, decoupling the payment system from the rest of the ordering application ensures that if the payment system is down, customers can still browse menus and add items to their cart.

Step-by-Step Solution

1
Analyze the scenario requirement of isolating a component failure (payment processing) to prevent it from affecting the rest of the application.
Identified the need to remove direct dependencies between the application components.
Removing direct dependencies prevents a cascading failure where one down component causes the entire application to crash.
2
Select the AWS Cloud design principle that describes building independent components that interact without being tightly integrated.
Loose coupling is selected as the correct design principle.
Loose coupling allows components to remain operational and scale independently, ensuring high availability and fault isolation.

Key Concept

Loose coupling is an AWS Cloud design principle where components are decoupled, reducing dependencies so that a failure in one component does not cascade to others.
Estimated Time:45s
Question 84Question →

A smart-grid utility company experiences unpredictable surges in data processing demands during severe weather events, while data volume remains minimal during normal operations. The company wants to ensure its infrastructure can automatically scale to handle these sudden peaks without paying for idle capacity during quiet periods. Which benefit of the AWS Cloud directly addresses this requirement?

Show answer & explanation

Answer: Stop guessing capacity, which allows the company to scale resources dynamically in response to real-time demand fluctuations rather than pre-purchasing excess infrastructure.

Answer

Stop guessing capacity, which allows the company to scale resources dynamically in response to real-time demand fluctuations rather than pre-purchasing excess infrastructure.
The benefit of 'stopping guessing capacity' allows organizations to avoid over-provisioning or under-provisioning resources. Instead of guessing how much infrastructure is needed for peak storm demand, AWS automatically scales resources up or down as demand dictates, reducing costs and preventing outages.

Step-by-Step Solution

1
Analyze the company's requirement to handle unpredictable, temporary surges in data volume without paying for idle capacity during off-peak periods.
The company needs a mechanism that matches resource allocation directly to fluctuating real-time demand, avoiding both over-provisioning and under-provisioning.
This aligns with the AWS benefit of not having to guess capacity limits beforehand.
2
Evaluate the options against the 6 benefits of the AWS Cloud.
The concept of scaling dynamically to match demand rather than pre-provisioning for peak loads is known as 'stop guessing capacity'.
This benefit ensures resources are scaled in and out dynamically, preventing wasted spend and ensuring availability.

Key Concept

Stop guessing capacity as an AWS Cloud benefit
Question 85Question →

An enterprise runs a legacy monolithic application on-premises. The infrastructure costs 500,000annuallyinhardwaredepreciation(capitalexpense),500,000 annually in hardware depreciation (capital expense), 100,000 in data center power and cooling, and $200,000 in dedicated system administration salaries. The application's utilization is highly variable, requiring 80% of total capacity during a 3-month holiday peak, but dropping to just 10% during the remaining 9 months of the year. The company plans to migrate this application to AWS and re-architect it using Amazon EC2 Auto Scaling and Amazon Aurora. Which of the following best describes the primary economic shift and driver that will yield the greatest Total Cost of Ownership (TCO) reduction for this seasonal workload?

Show answer & explanation

Answer: Shifting from a capital expense (CapEx) model with fixed capacity to an operating expense (OpEx) model, leveraging elasticity to dynamically scale resources to match the seasonal demand variation, thereby eliminating idle capacity costs during off-peak months.

Answer

Shifting from a capital expense (CapEx) model with fixed capacity to an operating expense (OpEx) model, leveraging elasticity to dynamically scale resources to match the seasonal demand variation, thereby eliminating idle capacity costs during off-peak months.
The correct option correctly identifies that the primary financial driver is shifting from a Capital Expenditures (CapEx) model to an Operating Expenditures (OpEx) model, combined with leveraging AWS elasticity to dynamically scale down capacity during off-peak times. This directly minimizes the total cost of ownership by eliminating idle resource waste.

Step-by-Step Solution

1
Analyze the on-premises cost structure and utilization patterns.
The on-premises environment uses a capital expense (CapEx) model with high fixed costs ($500,000 hardware depreciation) sized for peak capacity, resulting in 90% idle capacity for 9 months of the year.
To calculate the potential savings of cloud migration, we must first understand the baseline expenditures and the waste patterns of the legacy infrastructure.
2
Identify the primary economic shift when migrating to AWS.
The company shifts from a CapEx model (upfront hardware investments) to an operating expense (OpEx) model, where they pay only for running resources on a variable basis.
Recognizing the shift from CapEx to OpEx is fundamental to understanding AWS cloud economics.
3
Evaluate the role of elasticity in reducing the Total Cost of Ownership (TCO).
Elasticity allows the application to automatically scale in/out using Amazon EC2 Auto Scaling, meaning the company only pays for 80% capacity during the 3-month peak, and drops to 10% capacity for the other 9 months.
Matching supply to demand directly eliminates the cost of idle resources, which is the main source of waste in seasonal on-premises environments.
4
Synthesize the options to select the correct driver.
The option advocating the shift from CapEx to OpEx coupled with elasticity to eliminate off-peak idle costs represents the correct cloud economic principle.
This option correctly applies both the CapEx-to-OpEx shift and the concept of elasticity to address the seasonal business scenario.

Key Concept

The economic benefits of shifting from Capital Expenditures (CapEx) to Operating Expenditures (OpEx) and utilizing elasticity to match capacity with demand.
Estimated Time:2m 0s
Question 86Question →

A digital health startup is transitioning its core genomic sequencing pipelines to AWS. Previously, the company had to buy expensive high-performance computing (HPC) hardware upfront, which took months to write off as capital depreciation. On AWS, they pay only for the compute hours their pipelines consume, allowing them to fund ongoing development directly from their operational budget. However, their CFO notices that because AWS aggregates usage from hundreds of thousands of active customers, the pay-as-you-go pricing for these compute resources is significantly lower than what the startup could negotiate on their own. Which benefit of the AWS Cloud is primarily responsible for the lower per-unit resource cost observed by the CFO?

Show answer & explanation

Answer: Benefit from massive economies of scale

Answer

Benefit from massive economies of scale
The correct answer is the option stating 'Benefit from massive economies of scale'. By aggregating resource usage across hundreds of thousands of active customers, AWS can achieve higher economies of scale. This translates into lower pay-as-you-go prices for individual customers than they could achieve on their own.

Step-by-Step Solution

1
Analyze the scenario details to identify the primary financial benefit being queried.
The CFO is noticing a lower per-unit resource cost obtained through aggregated customer demand.
This isolates the question from the general pay-as-you-go benefits to the specific driver of reduced pricing.
2
Differentiate between the AWS Cloud benefits related to cost.
Trading capital expense for variable expense describes the shift from CapEx to OpEx. Benefiting from massive economies of scale describes the lower per-unit pricing achieved through aggregation.
Ensures the correct classification of AWS's pricing advantage vs. the customer's billing model.
3
Select the benefit that corresponds to aggregated usage reducing unit pricing.
The correct benefit is 'Benefit from massive economies of scale'.
AWS passes these savings onto customers in the form of lower prices.

Key Concept

AWS Cloud economies of scale drive lower pricing through customer aggregation.
Question 87Question →

A maritime logistics enterprise is planning to migrate its fleet management system to the AWS Cloud. The system consists of a legacy monolithic desktop client application and a backend Microsoft SQL Server database. The enterprise wants to deploy the desktop client application as-is onto Amazon EC2 instances to meet a tight migration deadline. Simultaneously, they decide to migrate the database to Amazon RDS for SQL Server to offload database patching, backups, and OS maintenance. Which of the following correctly identifies the migration strategies chosen for the desktop client application and the database?

Show answer & explanation

Answer: Rehosting for the client application and Replatforming for the database

Answer

Rehosting for the client application and Replatforming for the database
The correct option is the one stating 'Rehosting for the client application and Replatforming for the database'. Rehosting (lift-and-shift) involves moving applications to the cloud as-is without modification, which fits the plan for the client application. Replatforming (lift-tinker-and-shift) involves making minimal platform optimizations, such as migrating a self-managed database to a managed database service like Amazon RDS, to reduce administrative overhead without altering core application code.

Step-by-Step Solution

1
Analyze the migration plan for the client application.
The application is migrated as-is without change to Amazon EC2, which corresponds to Rehosting (lift-and-shift).
To identify the correct migration strategy from the 6 Rs for the first component.
2
Analyze the migration plan for the database.
The SQL Server database is migrated to a managed service (Amazon RDS) to reduce administrative overhead without changing the core database engine, which corresponds to Replatforming (lift-tinker-and-shift).
To identify the correct migration strategy from the 6 Rs for the second component.
3
Combine the identified strategies and select the option that matches.
The correct combination is Rehosting for the client application and Replatforming for the database.
To select the option that accurately represents both migration paths.

Key Concept

Distinguishing between AWS migration strategies (6 Rs), specifically Rehosting (lift-and-shift) and Replatforming (lift-tinker-and-shift).
Estimated Time:2m 0s
Question 88Question →

A startup is building a document-processing application that converts uploaded files into different formats. Rather than deploying virtual servers to run the conversion software and maintaining the operating systems, the startup chooses to use Amazon S3 for storage and AWS Lambda to run the conversion script on demand. 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 design principle of using services, not servers. By leveraging managed and serverless offerings like Amazon S3 and AWS Lambda, the startup removes the operational overhead of provisioning, configuring, patching, and maintaining physical or virtual servers. This allows developers to focus entirely on application logic rather than infrastructure administration.

Step-by-Step Solution

1
Analyze the operational choices made in the scenario.
The startup is replacing traditional self-managed virtual servers with Amazon S3 and AWS Lambda, which are fully managed and serverless.
Understanding what is being replaced and what is being adopted helps identify the core architectural shift.
2
Determine the primary operational benefit of the chosen services.
The startup no longer has to patch operating systems, manage server lifecycles, or handle lower-level infrastructure administration.
Identifying the target benefit points directly to the design principle that values offloading operational tasks.
3
Match the architectural choice to the corresponding AWS Cloud design principle.
Choosing to utilize managed and serverless offerings to eliminate server management is defined as the 'Services, not servers' design principle.
This confirms the correct principle that matches the description of eliminating virtual server management.

Key Concept

AWS Cloud Design Principles - Services, not servers
Question 89Question →

A global logistics company, LogiRoute, is migrating its on-premises infrastructure to the AWS Cloud. The migration team has identified two specific workloads:

1. A custom inventory database that they want to migrate to Amazon RDS to automate database patching and backups, without making any changes to the database structure or code.
2. A legacy document archiving system that is no longer used by any business departments and provides no ongoing value.

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

Select all that apply

Show answer & explanation

Answer: Replatforming for the custom inventory database; Retiring for the legacy document archiving system

Answer

The correct strategies are Replatforming for the custom inventory database and Retiring for the legacy document archiving system.
Replatforming is correct for the database workload because it optimizes operations by adopting a managed database service (Amazon RDS) without modifying the schema or code. Retiring is correct for the archiving system because it is no longer used by the business, making decommissioning the optimal choice.

Step-by-Step Solution

1
Analyze the custom inventory database workload, which is being moved to Amazon RDS (a managed service) to reduce operational tasks like patching and backups without code alterations.
Determine that this lift-tinker-and-shift approach is Replatforming.
Replatforming involves modifying the platform to adopt managed services without changing the core application code.
2
Analyze the legacy document archiving system workload, which is decommissioned because it is no longer used and has no business value.
Determine that this decommissioning approach is Retiring.
Retiring refers to identifying assets that are no longer useful and turning them off during the migration.

Key Concept

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

An online gaming studio is migrating its platform to the AWS Cloud. The migration team is evaluating two specific workloads:

1. A multiplayer matchmaking system that is currently a legacy monolithic application. The studio plans to completely rewrite this application to leverage a serverless, microservices-based architecture for dynamic scaling.
2. A player profiles database currently running on an on-premises PostgreSQL server. The studio wants to move this database to a managed cloud database service to reduce administrative overhead, without changing the database engine or the database schema.

Which of the following migration strategies should the studio select for these workloads? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Refactoring (Re-architecting) for the multiplayer matchmaking system; Replatforming for the player profiles database

Answer

Refactoring (Re-architecting) for the multiplayer matchmaking system, and Replatforming for the player profiles database.
Refactoring (Re-architecting) is correct for the matchmaking system because it involves rewriting the application code to implement a microservices-based, serverless architecture. Replatforming is correct for the player profiles database because the database is moved to a managed cloud database service (like Amazon RDS) to minimize administrative overhead while preserving the original database engine and schema.

Step-by-Step Solution

1
Analyze the requirements for the multiplayer matchmaking system.
The workload requires a complete rewrite to migrate from a monolithic structure to a serverless, microservices-based architecture.
This workload requires modifying the code and design to leverage cloud-native features, which defines the Refactoring (Re-architecting) migration strategy.
2
Analyze the requirements for the player profiles database.
The database needs to move to a managed service to offload administrative tasks, but without changing the engine or schema.
This workload involves shifting to a managed service (such as Amazon RDS for PostgreSQL) while keeping the core schema and engine the same, which defines the Replatforming (lift-tinker-and-shift) strategy.

Key Concept

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

A mobile gaming studio is planning to launch a new multiplayer game. To minimize costs, they want to avoid upfront investments in physical servers. Additionally, they need to deploy the game to players worldwide with minimal latency. Which of the following benefits of the AWS Cloud directly address these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

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

Answer

The benefits of going global in minutes and trading capital expense for variable expense directly address the mobile gaming studio's needs.
The scenario describes a need to avoid upfront capital expenses for physical servers and to deploy the game worldwide with low latency. Trading capital expense for variable expense allows the company to pay only for the resources they consume rather than investing heavily in physical datacenters beforehand. Going global in minutes enables them to deploy applications in multiple AWS Regions around the world, providing lower latency and a better experience for players globally.

Step-by-Step Solution

1
Identify the requirement of avoiding upfront costs for physical servers.
This maps to the AWS Cloud benefit of trading capital expense for variable expense, which replaces upfront capital expenditures (CapEx) with pay-as-you-go operational expenses (OpEx).
The studio does not want to pay for physical servers before launching.
2
Identify the requirement of deploying the game to players worldwide with minimal latency.
This maps to the AWS Cloud benefit of going global in minutes, which allows deploying workloads globally across multiple AWS Regions rapidly.
Global distribution is required to minimize latency for players around the world.

Key Concept

Benefits of the AWS Cloud
Estimated Time:1m 0s
Question 92Question →

A media company is migrating its video processing pipeline to the AWS Cloud. The pipeline ingests raw video files, extracts metadata, transcodes the videos into multiple formats, and generates thumbnails. In the legacy on-premises system, all these tasks run sequentially on a single large server. If one task fails, the entire pipeline halts.

On AWS, the company wants to ensure that a failure in the thumbnail generation step does not interrupt video transcoding. Additionally, they want the compute capacity to automatically scale up during peak upload hours and scale down to zero when no videos are uploaded.

Which architectural approach on AWS directly addresses these requirements by applying the correct cloud design principles?

Show answer & explanation

Answer: Decouple the processing steps using Amazon Simple Queue Service (Amazon SQS) to achieve loose coupling, and use AWS Lambda functions to achieve elasticity.

Answer

Decouple the processing steps using Amazon Simple Queue Service (Amazon SQS) to achieve loose coupling, and use AWS Lambda functions to achieve elasticity.
The correct choice proposes decoupling the steps using Amazon SQS queues and using AWS Lambda functions. This directly implements loose coupling, preventing a failure in one component from stopping the rest of the pipeline. It also implements elasticity by scaling compute resources automatically to match load and scaling down to zero when idle.

Step-by-Step Solution

1
Analyze the system's resilience requirement.
Identify that isolating the thumbnail generation step so that it does not impact video transcoding requires a loosely coupled architecture.
Loose coupling ensures that components can fail independently without causing a cascade failure across the entire application pipeline.
2
Analyze the system's scaling and idle-state requirements.
Identify that dynamically scaling compute resources based on demand and scaling down to zero when idle requires elasticity.
Elasticity allows the application to automatically match resource supply with fluctuating demand, reducing costs during idle periods.
3
Evaluate the AWS services and principles described in the choices.
Select the option that decouples steps using Amazon SQS (loose coupling) and runs compute on AWS Lambda (elasticity and serverless scaling to zero).
Amazon SQS provides the queue buffering needed for loose coupling, and AWS Lambda provides event-driven serverless compute that scales to zero.

Key Concept

Loose coupling and elasticity are key design principles of the AWS Cloud that enable fault isolation and dynamic resource scaling.
Question 93Question →

A company is building a news portal on AWS. The portal must automatically adjust its capacity to handle sudden spikes in reader traffic during breaking news events. Additionally, the team wants to ensure that a database failure in the user comments section does not prevent users from reading the main news articles. Which AWS Cloud design principles should the company implement to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Loose coupling; Elasticity

Answer

The correct principles are loose coupling and elasticity.
Implementing loose coupling ensures that components are independent, so a failure in the comments component does not disrupt the main article reading experience. Implementing elasticity ensures the application automatically scales its infrastructure capacity to match traffic demands without manual intervention.

Step-by-Step Solution

1
Analyze the requirement for handling sudden spikes in traffic automatically.
Identify that dynamically scaling capacity up and down to match demand refers to elasticity.
This matches the requirement of automatically adjusting capacity during breaking news events.
2
Analyze the requirement that a database failure in one component (comments) should not impact another component (reading articles).
Identify that isolating dependencies between components is called loose coupling.
This ensures the application is resilient and that failures do not cascade.

Key Concept

AWS Cloud design principles: Elasticity and Loose Coupling
Estimated Time:50s
Question 94Question →

A startup in the digital health sector is launching a telemedicine platform. The company's leadership wants to avoid purchasing expensive physical servers and storage arrays upfront. Additionally, they are uncertain about the daily patient volume, making it difficult to predict the exact resource requirements needed to prevent application downtime. Which of the following AWS Cloud benefits directly address these business requirements? (Select TWO.)

Select all that apply

Show answer & explanation

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

Answer

Trading fixed expense for variable expense and stopping guessing capacity are the correct answers.
Trading fixed expense for variable expense allows the startup to avoid high upfront infrastructure costs by paying only for consumed resources. Stopping guessing capacity ensures that the application automatically scales to handle traffic spikes, preventing downtime without over-provisioning resources.

Step-by-Step Solution

1
Analyze the scenario requirements.
The startup needs to avoid high upfront server/storage costs and manage unpredictable resource demand to prevent downtime.
This helps map the business challenges to the official AWS Cloud benefits.
2
Evaluate the first requirement: avoiding upfront costs.
Trading fixed expense for variable expense allows the company to pay as they go instead of investing heavily in upfront hardware.
This directly aligns with the economic benefit of cloud computing over on-premises data centers.
3
Evaluate the second requirement: handling uncertain daily patient volume.
Stopping guessing capacity allows the system to scale resources automatically up or down based on actual usage.
This prevents application downtime from under-provisioning and saves cost from over-provisioning.

Key Concept

The six core benefits of AWS Cloud computing, specifically trading fixed expense for variable expense and stopping guessing capacity.
Question 95Question →

A media company, CineArchive, is migrating its legacy portfolio to AWS. The migration team has identified two specific workloads:

1. A legacy document management system that runs on an old operating system and relies on a specific local filesystem structure. The team wants to migrate this workload to AWS as quickly as possible with zero code or configuration changes.
2. A relational database running on-premises that suffers from high administrative overhead. The team wants to move the database to a managed service in AWS to reduce database administration tasks (such as patching and backups) without modifying the database schema or rewriting the SQL queries.

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

Select all that apply

Show answer & explanation

Answer: Rehosting (lift-and-shift) for the document management system; Replatforming (lift-tinker-and-shift) for the database workload

Answer

The correct strategies are Rehosting (lift-and-shift) for the document management system and Replatforming (lift-tinker-and-shift) for the database workload.
Rehosting (lift-and-shift) is the correct strategy for the document management system because it allows moving the workload to the cloud without any code or configuration changes. Replatforming (lift-tinker-and-shift) is the correct strategy for the database workload because moving to a managed service (such as Amazon RDS) reduces database management overhead (e.g., patching, backups) while keeping the database schema and SQL queries intact.

Step-by-Step Solution

1
Analyze the requirements for the legacy document management system.
The requirement specifies migrating the workload as quickly as possible with zero code or configuration changes. This maps directly to the Rehosting (lift-and-shift) migration strategy.
Rehosting involves copying the existing application to the cloud without modifying its architecture or code.
2
Analyze the requirements for the relational database.
The requirement specifies moving to a managed service to reduce administrative overhead (like patching and backups) without modifying the schema or rewriting queries. This maps directly to the Replatforming (lift-tinker-and-shift) strategy.
Replatforming involves modifying the runtime environment (e.g., moving to a managed database service like Amazon RDS) to optimize operations without changing the core application architecture.

Key Concept

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

A remote education company wants to focus on developing its online learning platform rather than managing physical server racks, power supplies, and cooling systems. Which of the following are benefits of the AWS Cloud that directly support this business direction? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Stop spending money running and maintaining data centers; Trade capital expense for variable expense

Answer

The correct answers are the benefits to stop spending money running and maintaining data centers, and to trade capital expense for variable expense.
The benefit to stop spending money running and maintaining data centers directly addresses the desire to avoid managing power, cooling, and physical racks. The benefit to trade capital expense for variable expense allows the business to pay only for resources consumed, avoiding heavy upfront investments in physical infrastructure.

Step-by-Step Solution

1
Identify the company's core pain points in the scenario.
The company wants to avoid physical management overhead (racks, power, cooling) and capital investments associated with hardware.
This allows mapping the requirements to the standard benefits of cloud computing.
2
Match these needs to the six defined benefits of the AWS Cloud.
Avoiding infrastructure management matches 'Stop spending money running and maintaining data centers.' Shifting away from heavy upfront physical purchases matches 'Trade capital expense for variable expense.'
These two benefits directly alleviate the burden of physical hardware operations and cost structures.

Key Concept

Benefits of the AWS Cloud
Estimated Time:1m 0s
Question 97Question →

A startup is deploying a healthcare booking application on AWS. To ensure the application is highly resilient and requires minimal operational effort, the architectural design must adhere to AWS Cloud design principles. Which two of the following architectural decisions demonstrate the application of these AWS Cloud design principles? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploying an Amazon Simple Queue Service (Amazon SQS) queue to buffer requests between the frontend web servers and the backend processing service; Utilizing Amazon Aurora Serverless instead of managing a relational database on self-provisioned Amazon EC2 instances

Answer

The correct architectural decisions are using Amazon SQS to buffer and decouple requests, and utilizing Amazon Aurora Serverless to reduce operational overhead instead of self-managing a database on Amazon EC2.
The correct architectural decisions are using Amazon SQS to buffer requests and adopting Amazon Aurora Serverless. SQS allows components to interact asynchronously, ensuring that a bottleneck or failure in the backend does not impact the frontend's ability to receive requests, which is a classic example of loose coupling. Using a managed, serverless database service like Amazon Aurora Serverless represents the 'services, not servers' principle, shifting the operational burden of database management, patching, and scaling to AWS.

Step-by-Step Solution

1
Analyze the scenario requirements
The startup needs a highly resilient architecture that requires minimal operational effort, which means applying principles such as loose coupling, services not servers, and design for failure.
This sets the criteria for evaluating the design choices.
2
Evaluate the option to use Amazon SQS
Amazon SQS provides an asynchronous communication channel that decouples the frontend from the backend, demonstrating loose coupling.
Loose coupling prevents a failure in one component from cascading to others, improving overall resilience.
3
Evaluate the option to use Amazon Aurora Serverless
Amazon Aurora Serverless is a fully managed service that eliminates the need to manage physical or virtual servers, demonstrating the services not servers principle.
Managed services minimize operational effort by offloading tasks like patching, backups, and scaling to AWS.
4
Evaluate the remaining options to identify anti-patterns
Monolithic architectures, single-instance configurations, and over-provisioned manual scaling are anti-patterns that violate loose coupling, design for failure, and elasticity.
This confirms that the other choices represent incorrect architectural practices.

Key Concept

AWS Cloud design principles recommend decoupling components (loose coupling), using managed services (services not servers), and building for high availability and dynamic scaling.
Question 98Question →

An online education platform, EduLearn, wants to migrate its legacy student grading application to the AWS Cloud. The migration team decides to move the application's virtual machines directly to Amazon EC2 as-is, without altering any application code or configuration, to ensure a quick transition. Which migration strategy does this action represent?

Show answer & explanation

Answer: Rehosting

Answer

Rehosting
The correct answer is Rehosting. Rehosting, often referred to as 'lift-and-shift,' is a strategy where applications are migrated to the cloud without any modifications to their architecture or code, allowing for a fast and low-risk migration. In this scenario, moving the student grading application's virtual machines directly to Amazon EC2 without alterations is a classic example of Rehosting.

Step-by-Step Solution

1
Analyze the migration requirements in the scenario.
The platform wants to move the application's virtual machines to Amazon EC2 as-is, without making any modifications to the code or configurations.
Identifying the level of modification is the key to determining the correct 6 Rs migration strategy.
2
Map the level of modification to the standard AWS migration strategies.
Moving applications as-is without code modifications aligns with the definition of Rehosting (lift-and-shift).
Rehosting is characterized by zero changes to the application code, focusing on speed and simplicity of migration.

Key Concept

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

A digital publishing company experiences highly unpredictable traffic surges when articles go viral. Previously, the company managed these surges by purchasing and maintaining a permanent array of physical web servers capable of handling peak historic traffic, which cost $25,000\$25,000 per month but operated at a baseline utilization of only 8%8\%. After migrating to AWS, the company decommissioned their physical servers and implemented an Auto Scaling group of EC2 instances. Their monthly AWS bill now varies between $2,000\$2,000 and $18,000\$18,000 depending on actual monthly web traffic. While the financial shift from a fixed monthly cost to a variable bill represents one cloud benefit, which AWS Cloud benefit is directly demonstrated by the elimination of the operational inefficiencies of under-provisioning (outages) and over-provisioning (costly idle servers)?

Show answer & explanation

Answer: Stop guessing capacity

Answer

Stop guessing capacity is the correct answer because it directly addresses the elimination of over-provisioning (idle servers) and under-provisioning (outages) by scaling capacity dynamically to match demand.
The correct answer is 'Stop guessing capacity' because the company's dynamic scaling architecture eliminates the inefficiency of over-provisioning (which led to an 8%8\% utilization rate and high idle costs) and under-provisioning (which led to outages during viral surges). By matching compute capacity to real-time traffic, they avoid both operational issues.

Step-by-Step Solution

1
Analyze the operational challenges described in the scenario.
The publishing company is dealing with under-provisioning (outages during viral traffic surges) and over-provisioning (costly idle physical servers at 8%8\% utilization).
Identifying the core technical problem allows us to map it to the correct AWS Cloud benefit.
2
Differentiate between the financial and operational aspects of the scenario.
The financial transition from fixed to variable cost represents one benefit, but the question asks specifically for the benefit that solves the operational capacity mismatches.
This step prevents falling for the distractor related to Capex/Opex.
3
Match the operational solution (dynamic auto-scaling) to the official AWS Cloud benefits.
The ability to dynamically scale resources to eliminate idle capacity and prevent outages corresponds directly to 'Stop guessing capacity'.
This confirms 'Stop guessing capacity' as the correct answer based on AWS documentation definitions.

Key Concept

Define the benefits of the AWS Cloud
Question 100Question →

A mobile gaming studio, PixelVibe, is migrating its backend multiplayer matchmaking system to AWS. The current application relies on a proprietary on-premises database that requires expensive licensing and custom clustering. The studio decides to migrate the application's code as-is to Amazon EC2, but swaps the underlying database to Amazon Aurora PostgreSQL to eliminate licensing costs and benefit from automated clustering. Which migration strategy does this scenario describe?

Show answer & explanation

Answer: Replatforming

Answer

Replatforming
The correct strategy is Replatforming because the company is migrating its application code without major changes ('as-is'), but optimizing the database by switching to a fully managed cloud service (Amazon Aurora) to reduce licensing costs and management overhead.

Step-by-Step Solution

1
Analyze the migration actions performed by the studio.
The application code is migrated without changes (as-is to EC2), but the database is modified to use a managed cloud database service (Amazon Aurora).
This helps determine the extent of modification during migration.
2
Map the analyzed actions to the 6 Rs migration strategies.
Making minor adjustments to optimize the platform (using managed databases) without restructuring the core application code is characteristic of Replatforming.
To distinguish Replatforming from Rehosting (no changes) and Refactoring (significant architecture/code changes).

Key Concept

Replatforming migration strategy involves moving applications to the cloud with minor optimizations, such as swapping self-hosted components for managed services, without changing the core architecture.
PreviousPage 5 / 18Next
Cloud Concepts Practice Questions — AWS Certified Cloud Practitioner — Page 5 | Examkin