Cloud Concepts

358 questions

All types358 Multiple choice180 Multiple select178

A university research department is transitioning its scientific simulation workloads to AWS. These workloads run for approximately $12$ hours at the end of each month, requiring $64$ high-performance compute nodes. The rest of the month, the department only requires a single low-power server to host their results archive. The IT director is evaluating the economic impact of this migration compared to their legacy on-premises hardware.

Which of the following describes the most cost-effective provisioning strategy that illustrates the economic benefit of cloud elasticity for this workload?

Deploying

64

On-Demand Instances only for the

12

hours the simulations run and terminating them immediately afterward, while running a single low-power instance continuously.

Purchasing a

3

-year Reserved Instance contract for

64

instances to guarantee that compute capacity is permanently available and reserved for the monthly simulation runs.

Capitalizing the virtual hardware costs upfront as a capital expense (CapEx) to establish a baseline of

64

active instances, then converting the idle capacity into operating expenses (OpEx) when they are not in use.

Statically provisioning

64

instances to remain active throughout the entire month to ensure the system has the scalability to handle the peak, which represents the AWS definition of elasticity.

Show answer & explanation

Answer: Deploying $64$ On-Demand Instances only for the $12$ hours the simulations run and terminating them immediately afterward, while running a single low-power instance continuously.

Answer

Deploying

64

On-Demand Instances only for the

12

hours the simulations run and terminating them immediately afterward, while running a single low-power instance continuously.

The correct answer demonstrates elasticity by running the high-performance compute nodes only when active (

12

hours a month) and terminating them when finished. This ensures the university only pays for what it uses, avoiding the cost of idle servers.

Step-by-Step Solution

Analyze the workload's resource usage pattern over time.

The workload has a highly fluctuating demand pattern: it requires

64

compute nodes for only

12

hours per month (approx.

1.6\%

of the month) and just a single node for the remaining

98.4\%

of the time.

Identifying the demand pattern is necessary to choose between static provisioning and elastic, dynamic provisioning.

Evaluate the economic feasibility of AWS pricing models for the intermittent portion of the workload.

Using On-Demand instances for the

64

simulation nodes costs only for the

12

hours of actual use, whereas Reserved Instances or static provisioning would charge for the entire month regardless of utilization.

This step determines how to minimize waste for resources that are idle most of the month.

Formulate a hybrid provisioning strategy that matches the workload segments.

Run a single low-power instance continuously for the archive, and spin up

64

On-Demand instances only when the monthly simulation runs, terminating them immediately upon completion.

This strategy leverages cloud elasticity to optimize cost by dynamically aligning compute supply with workload demand.

Key Concept

Cloud elasticity vs. static provisioning, and the pay-as-you-go consumption model.

Estimated Time:2m 0s

Question 2Question →

A municipal utility enterprise operates a smart grid analytics platform. The workload fluctuates dramatically and unpredictably based on seasonal weather patterns, leading to periods where on-premises servers run at 95% capacity, followed by weeks of near-zero utilization. To address this, the enterprise wants to migrate to a model where they only pay for resources when they are actively consumed, eliminating the need to pre-allocate hardware. Furthermore, they are mandated to quickly replicate their software environment to support municipal grids across South America and Europe with sub-second response times. Which of the following core benefits of the AWS Cloud directly support the resolution of these operational challenges? (Select TWO.)

Select all that apply

Stop guessing capacity

Go global in minutes

Trading variable operating expenses for fixed capital expenses

Eliminating latency by scaling up individual instances vertically instead of scaling out horizontally

Deploying application components as a single, tightly coupled monolithic architecture to minimize overhead

Show answer & explanation

Answer: Stop guessing capacity; Go global in minutes

Answer

The correct answers are the benefits to go global in minutes and to stop guessing capacity.

The correct options are stopping guessing capacity and going global in minutes. Stopping guessing capacity allows the utility enterprise to scale automatically to match variable workloads instead of maintaining idle on-premises hardware. Going global in minutes enables them to rapidly deploy applications to multiple global AWS Regions to reduce latency for municipal partners in South America and Europe.

Step-by-Step Solution

Analyze the first requirement: dealing with dramatic, unpredictable workload fluctuations and eliminating pre-allocated hardware.

Identify that the ability to scale resources automatically to meet demand without upfront capacity planning corresponds to the AWS benefit of stopping guessing capacity.

This matches the operational challenge of weather-induced traffic spikes.

Analyze the second requirement: replicating the software environment across South America and Europe with sub-second response times.

Identify that the capability to deploy applications in multiple regions globally with minimal effort corresponds to the AWS benefit of going global in minutes.

This addresses the geographical expansion requirement with low latency.

Key Concept

Benefits of the AWS Cloud (Stop guessing capacity and Go global in minutes)

Estimated Time:2m 0s

Question 3Question →

A media streaming company is redesigning its video processing and delivery platform to handle highly fluctuating demand. The platform experiences sudden spikes in traffic during popular video releases and very low traffic during off-peak hours. Which two architectural decisions align with the AWS Cloud design principles of elasticity and services not servers? (Select TWO.)

Select all that apply

Configuring Amazon EC2 Auto Scaling to dynamically adjust the number of active virtual servers in response to fluctuating user demand

Utilizing AWS Lambda to transcode short video clips serverlessly without provisioning or managing underlying virtual machines

Provisioning a fixed number of high-performance Amazon EC2 instances designed to handle the maximum expected load at all times

Deploying the database and web server components onto a single large virtual machine to eliminate network latency between components

Manually restarting and upgrading the database instance size (vertical scaling) whenever traffic increases

Show answer & explanation

Answer: Configuring Amazon EC2 Auto Scaling to dynamically adjust the number of active virtual servers in response to fluctuating user demand; Utilizing AWS Lambda to transcode short video clips serverlessly without provisioning or managing underlying virtual machines

Answer

The correct architectural decisions are configuring Amazon EC2 Auto Scaling to dynamically adjust the number of active virtual servers in response to fluctuating user demand, and utilizing AWS Lambda to transcode short video clips serverlessly without provisioning or managing underlying virtual machines.

The correct choices are using Amazon EC2 Auto Scaling to dynamically adjust instance count, which is a direct application of elasticity, and using AWS Lambda to run code serverlessly, which applies the 'services, not servers' principle. Together, they allow the application to scale dynamically based on demand and minimize server management overhead.

Step-by-Step Solution

Analyze the requirements in the scenario.

The platform needs to handle fluctuating traffic efficiently (demand spikes vs. off-peak lows) using elasticity and 'services not servers' principles.

Understanding the core cloud design principles requested is key to identifying correct answers.

Evaluate options for the elasticity principle.

Configuring Amazon EC2 Auto Scaling allows the platform to scale out/in automatically to match the demand curve, proving elastic.

Elasticity is the ability to match resource supply to demand dynamically.

Evaluate options for the 'services not servers' principle.

Utilizing AWS Lambda allows executing code serverlessly without managing underlying operating systems or virtual machines.

The 'services, not servers' principle advocates using managed and serverless offerings to reduce operational overhead.

Key Concept

AWS Cloud Design Principles: Elasticity and Services not Servers

Estimated Time:1m 30s

Question 4Question →

A community theater company plans to migrate its ticketing platform to AWS. The platform receives extremely high volumes of traffic during the first hour of ticket releases for major shows, but experiences negligible traffic during the rest of the month. The theater needs to avoid paying for idle infrastructure and eliminate upfront server procurement costs.

Which two AWS cloud economics concepts or benefits should the theater leverage to meet these requirements? (Select TWO.)

Select all that apply

Replacing upfront capital expenses with variable operational expenses

Leveraging elasticity to dynamically adjust resource capacity to match actual demand

Converting variable operational expenses into fixed capital expenses to guarantee predictable budgeting

Permanently provisioning resources at peak capacity levels to guarantee scalability

Using a rehosting migration strategy to automatically redesign the application into serverless functions

Show answer & explanation

Answer: Replacing upfront capital expenses with variable operational expenses; Leveraging elasticity to dynamically adjust resource capacity to match actual demand

Answer

The theater company should replace upfront capital expenses with variable operational expenses, and leverage elasticity to dynamically adjust resource capacity to match actual demand.

The correct options identify two core AWS cloud economics benefits: shifting upfront capital expenses (CapEx) to variable operational expenses (OpEx), and using elasticity to scale resources dynamically. By trading capital expenses for operational expenses, the theater avoids upfront server purchasing costs. By leveraging elasticity, the ticketing system dynamically provisions resources to handle the sudden burst of ticket buyers and downscales during idle periods to prevent wasted expenditures.

Step-by-Step Solution

Analyze the financial constraint of avoiding upfront server procurement costs.

Trading upfront hardware costs for variable billing maps to the concept of shifting capital expenses (CapEx) to operational expenses (OpEx).

AWS allows businesses to pay as they go rather than buying hardware before using it.

Analyze the operational constraint of handling high traffic surges while minimizing idle resource costs.

Scaling resources up and down to match demand maps to the concept of elasticity.

Elasticity prevents paying for unused, running infrastructure during periods of low activity.

Key Concept

AWS Cloud Economics (CapEx to OpEx shift and Elasticity)

Estimated Time:1m 0s

Question 5Question →

NovaSprout Organics, a distributor of organic produce, is migrating its operations to the AWS Cloud. The IT department has finalized plans for two distinct workloads:

1. The company's core inventory tracking database will be moved to Amazon RDS to eliminate the administrative burden of backups and patching, while keeping the database engine and application code unchanged.
2. The legacy customer relationship management (CRM) system, which is complex and expensive to maintain on-premises, will be decommissioned in favor of a cloud-based CRM software-as-a-service (SaaS) application.

Which two migration strategies are being utilized by NovaSprout Organics? (Select TWO)

Select all that apply

Rehosting

Replatforming

Repurchasing

Refactoring

Retaining

Show answer & explanation

Answer: Replatforming; Repurchasing

Answer

Replatforming and Repurchasing are the migration strategies utilized in this scenario.

Replatforming is the correct strategy for the database migration because the company is moving the database to a managed service (Amazon RDS) to reduce administrative overhead while keeping the application code unchanged. Repurchasing is the correct strategy for the CRM system because the company is decommissioning its legacy on-premises system and replacing it with a third-party Software as a Service (SaaS) application.

Step-by-Step Solution

Analyze the database migration: The workload is moved to Amazon RDS (a managed database service) to reduce administrative tasks, but the engine and code remain unchanged.

Identify this as Replatforming (lift-tinker-and-shift), which involves optimizing a workload during migration without rewriting application code.

To classify the first workload's migration strategy.

Analyze the CRM system migration: The legacy system is decommissioned and replaced by a third-party CRM Software-as-a-Service (SaaS) product.

Identify this as Repurchasing (drop-and-shop), which involves moving to a different product, typically a SaaS platform.

To classify the second workload's migration strategy.

Select the two options that correspond to the identified strategies.

Select the options representing Replatforming and Repurchasing.

To provide the final correct answer keys.

Key Concept

Identifying cloud migration strategies (the 6 Rs), specifically Replatforming and Repurchasing.

Estimated Time:1m 30s

Question 6Question →

A logistics company, RouteLogix, runs a fleet management application that processes vehicle telemetry. The application requires high compute capacity to run route optimization algorithms for 4 hours every morning. During the rest of the day, the system only requires minimal resources to receive and store GPS location pings. The company's management wants to understand the economic impact of migrating this workload from their on-premises data center to AWS. Which of the following describe the financial benefits of this migration? (Select TWO.)

Select all that apply

The company can eliminate cost overhead from idle compute capacity by dynamically scaling resources down when the optimization algorithms are not running.

The company shifts from upfront capital expenditures (CapEx) for physical server procurement to variable operating expenditures (OpEx) based on actual compute usage.

The company will completely eliminate operating expenditures (OpEx) because AWS manages all physical infrastructure.

The company can reduce costs by provisioning resources at constant peak capacity to ensure continuous availability throughout the day.

AWS automatically assumes responsibility for all software licensing costs associated with the company's custom algorithms.

Show answer & explanation

Answer: The company can eliminate cost overhead from idle compute capacity by dynamically scaling resources down when the optimization algorithms are not running.; The company shifts from upfront capital expenditures (CapEx) for physical server procurement to variable operating expenditures (OpEx) based on actual compute usage.

Answer

The correct options are the statements describing how the company can eliminate cost overhead from idle compute capacity by dynamically scaling resources down, and how the company shifts from upfront capital expenditures (CapEx) to variable operating expenditures (OpEx).

The correct answer identifies the fundamental cloud economic principles of elasticity and shifting CapEx to OpEx. By utilizing elasticity, the company stops paying for idle compute capacity during the 20 hours of low daily utilization. Additionally, paying for AWS resources on-demand shifts upfront capital investments in physical hardware to operational expenses based on actual usage.

Step-by-Step Solution

Analyze the workload requirements of RouteLogix.

The workload has a high requirement for 4 hours and minimal requirements for the remaining 20 hours.

Identifying the variability of the workload helps determine the relevance of elasticity and compute demand matching.

Evaluate the financial transition from on-premises to AWS.

On-premises requires buying physical hardware for peak capacity (CapEx), leading to idle resources. AWS allows pay-as-you-go billing (OpEx) and dynamic resource scaling (elasticity).

This matches the target economic principles: shifting CapEx to OpEx and maximizing savings through elasticity.

Key Concept

Understand concepts of cloud economics (CapEx to OpEx shift and the financial benefit of elasticity)

Estimated Time:1m 30s

Question 7Question →

A fitness technology company is launching a new health-tracking application that collects workout data from smartwatches. To handle unpredictable traffic spikes during morning workouts and prevent data loss if a processing server fails, the development team wants to implement core AWS Cloud design principles. Which two of the following architectural strategies represent the correct application of these design principles? (Select TWO.)

Select all that apply

Deploy Amazon Simple Queue Service (Amazon SQS) to buffer incoming metrics and decouple the data ingestion layer from the backend processing servers.

Configure Amazon EC2 Auto Scaling to dynamically adjust the number of instances based on real-time application load.

Consolidate all database, caching, and application processing layers onto a single large Amazon EC2 instance to eliminate network latency.

Maintain a constant, fixed number of running Amazon EC2 instances sized for peak hourly load to avoid scaling delays.

Delegate operating system patching and firewall configuration of all Amazon EC2 instances to AWS.

Show answer & explanation

Answer: Deploy Amazon Simple Queue Service (Amazon SQS) to buffer incoming metrics and decouple the data ingestion layer from the backend processing servers.; Configure Amazon EC2 Auto Scaling to dynamically adjust the number of instances based on real-time application load.

Answer

Deploying Amazon Simple Queue Service (Amazon SQS) to buffer incoming metrics and decouple layers, and configuring Amazon EC2 Auto Scaling to dynamically adjust instance count.

Deploying Amazon SQS to buffer incoming metrics decouples the ingestion layer from the processing backend, adhering to the principle of loose coupling and ensuring that data is not lost if backend servers fail. Configuring Amazon EC2 Auto Scaling allows the system to scale out or in dynamically in response to workload demands, adhering to the principle of elasticity.

Step-by-Step Solution

Analyze the business and technical requirements of the fitness tracking application, which include handling unpredictable traffic spikes and preventing data loss during server failures.

Identified the need for elasticity to handle traffic spikes and loose coupling/design for failure to prevent data loss.

Aligns the application scenario with core AWS design principles.

Evaluate the architectural options against AWS design principles.

Determined that using Amazon SQS to buffer metrics decouple components (loose coupling), and Amazon EC2 Auto Scaling to dynamically scale compute capacity (elasticity), directly address the requirements.

Identifies the correct cloud architecture practices.

Key Concept

AWS Cloud design principles such as loose coupling, design for failure, and elasticity enable resilient, scalable, and cost-effective cloud architectures.

Question 8Question →

A healthcare startup wants to rapidly test and deploy a new patient wellness application. In the cloud, the company can provision compute resources in minutes to run experiments and launch the app, compared to waiting weeks for physical hardware procurement in an on-premises data center. Which benefit of the AWS Cloud does this scenario represent?

Trade fixed expense for variable expense

Stop guessing capacity

Deploy systems using tightly coupled monolithic architectures

Increase speed and agility

Show answer & explanation

Answer: Increase speed and agility

Answer

The correct answer is the option stating that the scenario represents increasing speed and agility.

The scenario highlights the ability to provision compute resources in minutes to run experiments and launch an application, rather than waiting weeks for physical hardware. This capability directly defines the benefit of increasing speed and agility by making resources instantly available to developers.

Step-by-Step Solution

Identify the key operational capability described in the scenario.

The healthcare company is spinning up compute resources in minutes instead of waiting weeks for physical hardware procurement.

This establishes that the primary benefit highlighted is the speed of resource acquisition and deployment.

Map this capability to one of the six benefits of the AWS Cloud.

Reducing resource provisioning time from weeks to minutes aligns directly with the benefit of increasing speed and agility.

Agility in the cloud refers to the speed at which developers can access resources, which accelerates innovation and experimentation.

Key Concept

Increase speed and agility as a benefit of the AWS Cloud

Estimated Time:45s

Question 9Question →

A healthcare organization is migrating its digital health record system to AWS. The system must remain available even if a physical data center experiences a complete power outage. The architecture team deploys the application servers across three Availability Zones behind an Application Load Balancer, and configures a Multi-AZ deployment for their database. Which design principle of the AWS Cloud does this architectural strategy directly implement?

Elasticity

Design for failure

Loose coupling

Scalability

Show answer & explanation

Answer: Design for failure

Answer

Design for failure

The correct answer is design for failure. This principle assumes that any component can and will fail over time. To mitigate this, architectures must be designed to avoid single points of failure by distributing resources across multiple physical locations (Availability Zones) and deploying redundant database instances to achieve high availability and fault tolerance.

Step-by-Step Solution

Analyze the technical requirements of the scenario.

The healthcare organization requires continuous system availability and resilience against physical data center outages.

Identifying the primary operational constraint helps map the architecture to the correct cloud design principle.

Evaluate the architectural components chosen for the solution.

The architecture utilizes three Availability Zones and a Multi-AZ database setup to eliminate single points of physical infrastructure failure.

Understanding how the components function helps determine which design principle they embody.

Match the architectural strategy to the core AWS Cloud design principles.

Deploying redundant resources across multiple Availability Zones to survive hardware or site failures directly aligns with the principle of designing for failure.

This confirms that the design assumes failure at any level and implements redundancy to prevent service interruption.

Key Concept

Designing for failure on AWS involves building architectures that assume any component can fail. By utilizing multiple Availability Zones and database replication, workloads remain operational despite localized infrastructure disruptions.

Question 10Question →

A retail company wants to implement a system on AWS that processes customer product reviews. The system must detect the sentiment of the reviews, translate non-English reviews to English, and save the results. The team wants to deploy this solution with the lowest possible operational overhead, avoiding tasks like operating system patching, capacity provisioning, and software installation. Which of the following designs best adheres to the AWS Cloud design principle of 'services not servers' to accomplish this goal?

Ingesting reviews via Amazon API Gateway, processing them using AWS Lambda functions that call Amazon Comprehend and Amazon Translate, and storing the final data in Amazon DynamoDB.

Deploying a single, high-capacity Amazon EC2 instance that runs a web server, a custom natural language processing library, a translation database, and a local PostgreSQL database.

Deploying the application as a monolithic service across a fleet of Amazon EC2 instances managed by an Auto Scaling group, using Amazon CloudWatch metrics to scale the instances in and out based on processing demand.

Provisioning dedicated Amazon EC2 instances pre-configured with AWS-managed machine learning software, and configuring AWS Systems Manager to automate the operating system patching on these instances.

Show answer & explanation

Answer: Ingesting reviews via Amazon API Gateway, processing them using AWS Lambda functions that call Amazon Comprehend and Amazon Translate, and storing the final data in Amazon DynamoDB.

Answer

Ingesting reviews via Amazon API Gateway, processing them using AWS Lambda functions that call Amazon Comprehend and Amazon Translate, and storing the final data in Amazon DynamoDB.

The correct design uses Amazon API Gateway, AWS Lambda, Amazon Comprehend, Amazon Translate, and Amazon DynamoDB. Each of these is a serverless or fully managed service. With this architecture, AWS handles server provisioning, operating system patching, scaling, and high availability, which completely removes the operational burden of managing servers from the customer.

Step-by-Step Solution

Analyze the requirement to minimize operational overhead, specifically avoiding operating system patching, capacity provisioning, and software installation.

Identify that the solution must avoid using virtual servers (Amazon EC2) that require manual administrative management.

The 'services not servers' principle guides architects to use fully managed services and serverless technologies to offload operational responsibility to AWS.

Evaluate the proposed architectural designs to see which one utilizes fully managed, serverless services instead of managing virtual instances.

The design using Amazon API Gateway, AWS Lambda, Amazon Comprehend, Amazon Translate, and Amazon DynamoDB relies entirely on serverless services.

Each of these services is fully managed by AWS, requiring no server provisioning, OS maintenance, or manual scaling configurations from the customer.

Verify that the alternative options rely on virtual servers (Amazon EC2) and explain why they do not meet the 'services not servers' principle.

Designs involving EC2 instances (whether scaled automatically, running on a single large instance, or using patch automation) still require the customer to manage the operating system and capacity.

This establishes that the serverless architecture is the correct choice because it completely removes the need to manage servers.

Key Concept

The AWS Cloud design principle of 'services not servers' guides architects to use fully managed and serverless services to minimize operational overhead and focus on application logic rather than infrastructure maintenance.

Question 11Question →

A digital publishing company wants to migrate its legacy on-premises email marketing tool to a modern, cloud-based software-as-a-service (SaaS) solution available in AWS Marketplace. Which migration strategy does this change represent?

Repurchasing

Rehosting

Replatforming

Refactoring

Show answer & explanation

Answer: Repurchasing

Answer

Repurchasing

The correct answer is the strategy of moving to a different product, typically a software-as-a-service (SaaS) model. When a company abandons their legacy on-premises tool to adopt a SaaS solution (such as one found in AWS Marketplace), they are utilizing the Repurchasing migration strategy.

Step-by-Step Solution

Identify the migration requirement described in the scenario.

The company wants to move from an on-premises marketing tool to a ready-made SaaS solution in AWS Marketplace.

Understanding the target state helps match it to one of the 6 Rs of migration.

Evaluate the 6 Rs migration strategies against a transition to a SaaS platform.

Replacing a legacy self-managed system with a software-as-a-service (SaaS) platform corresponds to the Repurchasing strategy.

Repurchasing is defined as moving to a different product, typically a cloud-hosted commercial software package or SaaS.

Key Concept

AWS Migration Strategies (6 Rs) - Repurchasing

Question 12Question →

A media company is planning to migrate its application portfolio to the AWS Cloud and wants to minimize implementation time and effort. Which TWO migration strategies should the company use to migrate its workloads with either zero changes to the underlying code, or only minor optimizations to use managed services without changing the core application architecture? (Select TWO.)

Select all that apply

Rehosting

Replatforming

Refactoring

Repurchasing

Retaining

Show answer & explanation

Answer: Rehosting; Replatforming

Answer

The correct strategies are Rehosting and Replatforming.

The correct strategies are Rehosting and Replatforming. Rehosting, often called 'lift-and-shift', moves the application directly to the cloud without modifying its architecture or code. Replatforming, or 'lift-tinker-and-shift', introduces minor optimizations to take advantage of managed services (such as migrating a database to Amazon RDS) without altering the application's core architecture.

Step-by-Step Solution

Analyze the migration requirements in the scenario.

The company wants to migrate workloads with either zero changes to code or only minor optimizations to use managed services, without altering the core application architecture.

This establishes the constraints of the migration, ruling out strategies that require code rewriting or vendor changes.

Evaluate the 6 Rs migration strategies against these requirements.

Rehosting ('lift-and-shift') requires no changes. Replatforming ('lift-tinker-and-shift') involves only minor optimizations (like adopting managed services) without changing the core architecture. Refactoring requires re-architecting/code changes, Repurchasing changes the application to a new product (SaaS), and Retaining leaves the application on-premises.

To select the two correct strategies that fit the criteria.

Key Concept

Cloud migration strategies (the 6 Rs), specifically Rehosting and Replatforming, which minimize changes to code and architecture during migration.

Estimated Time:45s

Question 13Question →

A startup is building a new mobile application backend on AWS. The startup wants to focus on writing code and minimizing infrastructure management while automatically handling fluctuating user demands. Which two of the following design decisions align with AWS cloud design principles to achieve this? (Select TWO.)

Select all that apply

Deploy the application code on AWS Lambda to run without provisioning or managing servers

Configure Amazon EC2 Auto Scaling to automatically adjust compute capacity based on live traffic

Host the web server, application logic, and database on a single large virtual machine to simplify network configuration

Pre-provision a fixed, maximum number of compute instances to guarantee peak performance during all hours

Perform physical security checks and hardware maintenance on the host servers running the application

Show answer & explanation

Answer: Deploy the application code on AWS Lambda to run without provisioning or managing servers; Configure Amazon EC2 Auto Scaling to automatically adjust compute capacity based on live traffic

Answer

Deploying the application code on AWS Lambda to run without provisioning servers and configuring Amazon EC2 Auto Scaling to adjust capacity based on traffic are the correct answers.

The correct options are deploying application code on AWS Lambda and configuring Amazon EC2 Auto Scaling. AWS Lambda aligns with the 'services, not servers' design principle by eliminating server management tasks, while Auto Scaling aligns with the 'elasticity' principle by matching resource capacity to demand dynamically.

Step-by-Step Solution

Analyze the scenario requirements: minimize infrastructure management overhead and automatically handle fluctuating demand.

Identified two primary design goals: adopting managed services ('services, not servers') and utilizing dynamic scaling ('elasticity').

This sets the target criteria for the correct options.

Evaluate the option regarding running serverless code.

AWS Lambda is a serverless service that aligns with the 'services, not servers' principle, removing the need to manage infrastructure.

This matches the goal of minimizing server management overhead.

Evaluate the option regarding automatic scaling.

Amazon EC2 Auto Scaling dynamically scales resources, which aligns with 'elasticity'.

This matches the goal of automatically handling fluctuating user demands.

Key Concept

AWS Cloud design principles including 'services, not servers' and 'elasticity'.

Question 14Question →

An insurance firm is migrating its claims processing system to AWS. The system consists of a web portal, a document generation service, and a document archiving service. Currently, the web portal calls the document generation and archiving services synchronously. If the archiving service is temporarily unavailable, the entire claim submission fails. How should the firm redesign the application on AWS to resolve this issue?

Consolidate the web portal, document generation, and document archiving services into a single monolithic application deployed on a single Amazon EC2 instance.

Increase the size of the web portal's Amazon EC2 instances to handle the additional connection load and wait times when downstream services fail.

Redesign the system to communicate asynchronously using Amazon Simple Queue Service (Amazon SQS), decoupling the web portal from downstream processing.

Configure the web portal to trigger synchronous execution of all services inside a single database transaction across multiple Availability Zones.

Show answer & explanation

Answer: Redesign the system to communicate asynchronously using Amazon Simple Queue Service (Amazon SQS), decoupling the web portal from downstream processing.

Answer

Redesign the system to communicate asynchronously using Amazon Simple Queue Service (Amazon SQS), decoupling the web portal from downstream processing.

Decoupling components using an asynchronous message queue like Amazon Simple Queue Service (Amazon SQS) is a core AWS design principle (loose coupling). It allows the web portal to queue requests and continue responding to users even if downstream services (like document generation or archiving) are experiencing latency or are temporarily offline.

Step-by-Step Solution

Analyze the current system architecture and identify dependencies.

The web portal has synchronous, tight coupling with the document generation and archiving services, making it vulnerable to downstream failures.

To solve the reliability issue, we must identify where the tight coupling is causing cascading failures.

Apply AWS design principles to decouple the components.

An asynchronous communication mechanism, such as a message queue, is selected to buffer requests.

Decoupling ensures that a failure or slowdown in downstream services does not immediately impact the web portal's availability.

Select the appropriate AWS service for queueing and asynchronous processing.

Amazon Simple Queue Service (Amazon SQS) is integrated between the web portal and the downstream services.

SQS provides a fully managed, scalable message queue that allows components to scale and fail independently without losing data.

Key Concept

Loose coupling

Estimated Time:1m 30s

Question 15Question →

A smart-home technology company is migrating its device telemetry processing system to the AWS Cloud. The workload experiences significant demand fluctuations, with peak traffic occurring in the morning and evening, and near-zero activity overnight. Which of the following describe the primary cloud economic benefits of this migration? (Select TWO.)

Select all that apply

The capability to dynamically scale resources to match actual hourly demand, minimizing cost during low-activity periods.

The utilization of standard On-Demand Instances to achieve the lowest possible long-term pricing for baseline workloads.

The transition from upfront capital expenditures (CapEx) to variable operating expenditures (OpEx) linked directly to resource consumption.

The ability to leverage Amazon EC2 Dedicated Hosts to eliminate all operating expenses (OpEx) for compute infrastructure.

The reduction of the customer's operational overhead by transferring guest operating system patching responsibility to AWS.

Show answer & explanation

Answer: The capability to dynamically scale resources to match actual hourly demand, minimizing cost during low-activity periods.; The transition from upfront capital expenditures (CapEx) to variable operating expenditures (OpEx) linked directly to resource consumption.

Answer

The correct answers are the capability to dynamically scale resources to match actual hourly demand, and the transition from upfront capital expenditures (CapEx) to variable operating expenditures (OpEx).

The correct options reflect the main economic benefits of AWS: elasticity and cost model shifting. Elasticity enables scaling resources up or down dynamically to prevent over-provisioning costs during off-peak hours. The cost shift changes the spending structure from capital expenses (CapEx) to operating expenses (OpEx), allowing the company to pay only for active resources.

Step-by-Step Solution

Analyze the workload's resource usage pattern over a 24-hour cycle.

The workload has high peaks during morning/evening and near-zero usage overnight, highlighting a need for resource elasticity.

Determining the workload's variability helps identify how cloud elasticity avoids the cost of idle on-premises hardware.

Evaluate the financial implications of shifting infrastructure from an on-premises data center to the pay-as-you-go cloud model.

The company moves from buying physical servers upfront (CapEx) to paying monthly based on consumption (OpEx).

Trading upfront capital expense for variable operational expense is a core economic advantage of the AWS Cloud.

Key Concept

Understanding cloud economics principles, particularly the cost benefits of elasticity and the shift from capital expenses (CapEx) to operational expenses (OpEx).

Question 16Question →

An online gaming portal manages player matchmaking and game lobby orchestration. The current architecture relies on a single monolithic server to run the matchmaking logic, store active session states, and send notification emails to players when a match is found. During peak tournament events, the system struggles to handle the load, resulting in delayed notifications and failed match setups. To align with AWS Cloud design principles, which of the following architectural changes should the portal implement? (Select TWO.)

Select all that apply

Use Amazon DynamoDB to externalize session state, allowing the matchmaking compute components to operate statelessly and scale independently.

Migrate the email notification subsystem to Amazon Simple Notification Service (Amazon SNS), leveraging a managed service instead of maintaining custom mail server software.

Deploy the monolithic matchmaking server on a single, highly-configured Amazon EC2 instance that remains running continuously to handle maximum potential user connections.

Store session states in the local memory of the matchmaking server and use sticky sessions to bind each player to that specific instance.

Configure a secondary duplicate monolithic server in a cold standby state and manually update its configuration files whenever a game update is released.

Show answer & explanation

Answer: Use Amazon DynamoDB to externalize session state, allowing the matchmaking compute components to operate statelessly and scale independently.; Migrate the email notification subsystem to Amazon Simple Notification Service (Amazon SNS), leveraging a managed service instead of maintaining custom mail server software.

Answer

The portal should implement using Amazon DynamoDB to externalize session state for stateless compute scaling and migrating the email notification subsystem to Amazon Simple Notification Service (Amazon SNS) to leverage managed services.

The correct architecture uses Amazon DynamoDB to store matchmaking session data externally, allowing the application tier to operate statelessly and scale horizontally (implementing loose coupling). It also utilizes Amazon SNS as a managed messaging service to handle notifications, removing the operational burden of managing a dedicated mail server (implementing services not servers).

Step-by-Step Solution

Analyze the bottlenecks in the monolithic setup, specifically state storage (local memory) and custom notification management.

Identify that statefulness prevents scaling and managing a custom email server adds unnecessary operational overhead.

AWS design principles advocate for stateless applications and offloading server management to managed services.

Select options that replace stateful components with external state stores and custom application code with managed services.

Amazon DynamoDB externalizes state (loose coupling), and Amazon SNS replaces custom notification infrastructure (services not servers).

This aligns the architecture with the core AWS design principles of loose coupling and utilizing managed services.

Key Concept

AWS Cloud Design Principles

Question 17Question →

A digital art auction platform hosts live virtual auctions once a week for exactly one hour. During this hour, user traffic increases five-fold, while the platform remains mostly idle for the rest of the week. Under their traditional on-premises model, the company had to purchase and configure high-end servers to handle this short weekly peak, which resulted in low resource utilization. By migrating to AWS, the company can automatically scale their resources up during the auction hour and scale down afterwards. Which AWS Cloud benefit is most directly demonstrated by this transition?

Trading variable expense for capital expense

Stop guessing capacity

Prioritizing vertical scalability to eliminate the need for elasticity

Implementing a monolithic design to simplify service coordination

Show answer & explanation

Answer: Stop guessing capacity

Answer

Stop guessing capacity

The correct answer is the option focusing on stopping capacity guesswork. Under an on-premises model, organizations often must provision resources based on maximum predicted peak demand, leading to idle capacity and wasted costs. AWS eliminates this by allowing systems to automatically scale up and down to match actual demand in real-time.

Step-by-Step Solution

Analyze the business scenario and identify the infrastructure challenges.

The company has highly variable traffic (a short weekly peak) and suffers from low resource utilization because they pre-provisioned physical hardware to meet that peak.

Understanding the current challenge is essential to mapping it to the correct AWS Cloud benefit.

Compare the transition to AWS features (automatic scaling up/down) with the six benefits of the AWS Cloud.

Automatically scaling resources to match demand instead of pre-purchasing peak capacity aligns with the benefit of 'Stop guessing capacity'.

This directly maps the solution to the correct cloud benefit, which addresses the inefficiency of over-provisioning.

Key Concept

Stop guessing capacity

Question 18Question →

A genomics research institute processes large datasets for DNA sequencing. These analysis runs occur sporadically, lasting only a few days each month, but require high-performance computing resources. Additionally, the institute wants to eliminate the operational overhead of managing physical hardware, power, and cooling in their local server rooms.

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

Select all that apply

Stop spending money running and maintaining data centers

Stop guessing capacity

Trade variable expense for capital expense

Design tightly coupled monolithic systems to simplify resource monitoring

Rely on scalability to automatically shrink and grow compute resources in real-time to match demand

Show answer & explanation

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

Answer

The benefits of stopping spending money running and maintaining data centers and stopping guessing capacity are correct.

The correct options are the statements focusing on stopping running and maintaining data centers and stopping guessing capacity. The institute's goal to eliminate the overhead of managing hardware, cooling, and power in local server rooms maps directly to stopping the operation of physical data centers. The sporadic sequencing runs map directly to the ability to avoid guessing capacity, as the institute can spin up large scale resources only when they need them and shut them down afterwards.

Step-by-Step Solution

Analyze the business requirements from the scenario.

The institute has two needs: first, handling highly variable, sporadic workloads (large runs lasting a few days per month); second, removing physical hardware management tasks (cooling, power, server maintenance).

Understanding the specific operational and financial pain points guides the selection of the correct AWS Cloud benefits.

Map the requirement of handling sporadic workloads to the correct AWS Cloud benefit.

The benefit of 'Stop guessing capacity' is the direct solution, as it allows scaling resources dynamically to match the sporadic peaks without buying excess hardware.

AWS allows scaling up and down as needed, eliminating the risk of underprovisioning or paying for idle resources.

Map the requirement of eliminating physical hardware management overhead to the correct AWS Cloud benefit.

The benefit of 'Stop spending money running and maintaining data centers' is the direct solution, as AWS handles all physical infrastructure logistics.

By using AWS, the institute shifts focus from racking servers and cooling rooms to analyzing genomic data.

Key Concept

The six core benefits of cloud computing as defined by AWS.

Question 19Question →

A multi-national retail corporation plans to migrate its inventory analysis system to AWS. The current on-premises system runs on a cluster of physical servers that cost $120,000 to purchase (depreciated over 3 years) plus$ 3,000 monthly for datacenter space and power. The database utilization spikes heavily during seasonal sales events (about 15 days a year) but is minimal otherwise. To maximize the Total Cost of Ownership (TCO) reduction and leverage cloud economics, which strategy should the financial team approve?

Increase capital expenditures (CapEx) by purchasing 3-year Dedicated Hosts upfront to ensure baseline and peak capacity are fully reserved, thereby reducing operational expenditures (OpEx) through long-term volume discounts.

Transition to a variable operating expense (OpEx) model by using AWS Auto Scaling to dynamically match compute capacity with peak demand, combined with Savings Plans for the predictable baseline workload, minimizing overall Total Cost of Ownership (TCO).

Deploy the inventory system on a fixed cluster of instances sized for peak performance, relying on AWS to automatically refund the cost of unused CPU cycles under standard pay-as-you-go elastic pricing policies.

Migrate the system as a monolithic database to a single large instance and use AWS Budgets to dynamically scale down hardware CPU and RAM capacity in real-time, converting traditional server depreciation into a capital expense (CapEx) credit.

Show answer & explanation

Answer: Transition to a variable operating expense (OpEx) model by using AWS Auto Scaling to dynamically match compute capacity with peak demand, combined with Savings Plans for the predictable baseline workload, minimizing overall Total Cost of Ownership (TCO).

Answer

The correct strategy involves transitioning to an operational expenditure (OpEx) model using AWS Auto Scaling for peak demand and commitment-based pricing like Savings Plans for the baseline workload. This combination eliminates upfront capital expenditures (CapEx), matches resource consumption directly with demand, and minimizes the overall Total Cost of Ownership (TCO).

Step-by-Step Solution

Analyze the workload characteristics of the retail inventory system.

The workload has a predictable baseline with short, highly variable seasonal spikes (15 days per year).

Understanding the baseline and variable patterns is necessary to determine the appropriate cloud economics strategy.

Evaluate the financial transition from capital expenditures to operational expenditures.

On-premises requires upfront physical server purchases (CapEx), while AWS allows pay-as-you-go consumption (OpEx).

Shifting to OpEx eliminates the risk of depreciation and underutilized capacity.

Apply elasticity and pricing models to optimize the Total Cost of Ownership (TCO).

AWS Auto Scaling handles peak demand dynamically, and Savings Plans reduce costs for the baseline workload.

Combining elasticity with commitment discounts maximizes cost efficiency for both constant and variable workloads.

Key Concept

Leveraging elasticity and demand-driven scaling to transition from fixed capital expenditures (CapEx) to variable operating expenditures (OpEx), reducing the Total Cost of Ownership (TCO).

Question 20Question →

A logistics enterprise is migrating its legacy supply chain optimization tool to AWS. The application requires massive computing power for $3$ hours every Sunday night to calculate optimal delivery routes, but remains completely idle for the rest of the week. Under their traditional on-premises model, the company had to purchase and maintain high-end physical servers that sat underutilized for $98\%$ of the week. Which of the following describes the financial transformation and the specific AWS Cloud benefit this migration achieves?

Trading variable expense for capital expense, enabling the enterprise to convert their ongoing operational software costs into a predictable, long-term physical asset.

Trading capital expense for variable expense, allowing the enterprise to pay only for the compute resources consumed during the active window rather than investing in upfront server hardware.

Leveraging scalability to dynamically shrink the infrastructure during idle times, which directly achieves the benefit of going global in minutes.

Stop spending money running and maintaining data centers, which allows the company to eliminate all variable operating expenses by utilizing AWS-managed physical hardware.

Show answer & explanation

Answer: Trading capital expense for variable expense, allowing the enterprise to pay only for the compute resources consumed during the active window rather than investing in upfront server hardware.

Answer

Trading capital expense for variable expense, allowing the enterprise to pay only for the compute resources consumed during the active window rather than investing in upfront server hardware.

The correct option correctly identifies the transition from capital expense (buying physical servers) to variable expense (paying only for the

3

hours of usage). This matches the definition of the AWS Cloud benefit: 'trade capital expense for variable expense'.

Step-by-Step Solution

Analyze the financial and operational pain points of the legacy supply chain application in the scenario.

The application runs for only

3

hours a week but required purchasing physical servers that remain idle for

98\%

of the time.

This establishes the current baseline of high capital expenditure (CapEx) and low resource utilization.

Map the transition from purchasing hardware upfront to paying based on usage to the appropriate AWS Cloud benefit.

Paying only for resources when they are consumed instead of investing in physical assets represents 'trading capital expense for variable expense'.

This is a core cloud economics concept that shifts costs from CapEx to OpEx.

Evaluate the choices to find the one that accurately describes this economic benefit and avoids common misconceptions.

The correct option outlines trading capital expense for variable expense to pay only for consumed compute resources during the active window.

This option correctly matches the scenario's shift from fixed hardware investments to pay-as-you-go consumption.

Key Concept

Trading capital expense for variable expense is a key AWS Cloud benefit where users pay only for consumed computing resources on a utility basis instead of making heavy upfront investments in physical infrastructure.

Estimated Time:2m 0s

Page 1 / 18Next

Cloud Concepts

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept