Examkin

Cloud Concepts

358 questions

All types358Multiple choice180Multiple select178
Question 41Question →

A financial services company is migrating its transaction processing system to AWS. The system currently uses an application server that synchronously writes transaction logs to a database and simultaneously invokes a third-party credit check API. If either the database or the third-party API becomes unresponsive, the entire transaction fails, resulting in customer dissatisfaction. Which architectural design modification should the company implement to align with AWS cloud design principles and improve the system's resilience?

Show answer & explanation

Answer: Introduce an Amazon Simple Queue Service (Amazon SQS) queue to buffer transaction requests, processing them asynchronously to isolate the application server from database or API downtime.

Answer

Introduce an Amazon Simple Queue Service (Amazon SQS) queue to buffer transaction requests, processing them asynchronously to isolate the application server from database or API downtime.
The correct design uses Amazon Simple Queue Service (Amazon SQS) to decouple the components. By buffering transaction requests in a queue and processing them asynchronously, the core application server is isolated from downstream database latency or third-party credit check API downtime. This aligns with the AWS design principles of loose coupling and designing for failure, ensuring the system remains responsive even if dependencies fail.

Step-by-Step Solution

1
Identify the system bottlenecks and failure domains.
The application server, database, and third-party credit check API are synchronously dependent, meaning any failure in the downstream services causes a total system failure.
Understanding the current tightly coupled state is necessary to apply the correct AWS design principles.
2
Apply the 'loose coupling' and 'design for failure' AWS design principles.
Determine that an asynchronous communication mechanism is required to break the synchronous dependencies.
Loose coupling ensures that components can fail or experience latency independently without causing a cascading failure across the entire system.
3
Select the appropriate AWS service to decouple the components.
Introduce Amazon SQS to queue incoming transaction requests and process them asynchronously.
An SQS queue buffers incoming requests, allowing the application server to accept transactions immediately and processing consumers to retry requests if downstream services are temporarily unavailable.

Key Concept

Loose coupling and design for failure using asynchronous messaging
Estimated Time:2m 0s
Question 42Question →

A startup is migrating its application to AWS. The application consists of an order processing service and an inventory service. Originally, the order processing service made direct, synchronous HTTPS calls to the inventory service. To ensure that orders can still be accepted even if the inventory service is temporarily offline or experiencing high latency, the team introduces an Amazon Simple Queue Service (Amazon SQS) queue to decouple the two services. Which of the following cloud design principles does this architectural change directly implement?

Show answer & explanation

Answer: Loose coupling

Answer

Loose coupling
The correct answer is loose coupling. By inserting Amazon SQS as a messaging buffer between the order processing service and the inventory service, the systems are decoupled. If the inventory service goes offline or is slow, the order processing service can still write messages to the queue and complete the transaction from the user's perspective, avoiding a system-wide failure.

Step-by-Step Solution

1
Analyze the problem scenario
The application has two services (order processing and inventory) that communicate synchronously, creating a single point of failure where if the inventory service is offline, the entire order process fails.
Understanding the current architecture helps identify the main drawback being addressed.
2
Evaluate the architectural change
An Amazon SQS queue is placed between the two services so that messages are queued asynchronously instead of direct, synchronous calls.
This shows that the services are no longer tightly dependent on each other's immediate runtime availability.
3
Map the change to AWS Cloud design principles
This separation is a classic implementation of loose coupling, which prevents cascading failures and allows components to scale or fail independently.
Matches the action of decoupling to the design principle of loose coupling.

Key Concept

Loose coupling is a key AWS design principle that reduces dependencies between components, preventing failures in one service from impacting another.
Estimated Time:1m 0s
Question 43Question →

A startup is designing a web application on AWS. They want to ensure that if the database layer experiences a temporary outage, the front-end web servers can still accept incoming customer orders without immediately failing. Which AWS Cloud design principle should the startup implement to achieve this goal?

Show answer & explanation

Answer: Loose coupling

Answer

Loose coupling
Loose coupling is the correct design principle because it isolates components of an application (often using intermediary services like Amazon Simple Queue Service or Amazon EventBridge). This ensures that if one component (such as the database) becomes unavailable, other components (such as the web servers) can continue to function and accept requests without failing immediately.

Step-by-Step Solution

1
Analyze the scenario requirements.
The startup needs to prevent a failure in the database layer from causing the front-end web servers to fail.
This requires isolating components and removing direct dependencies so they can operate independently.
2
Evaluate the design principles against the goal.
Loose coupling (for example, using a message queue like Amazon SQS between the web servers and database) allows the web servers to continue accepting orders even if the database is down.
Loose coupling is the AWS design principle dedicated to reducing dependencies and isolating failures.

Key Concept

Loose coupling is a fundamental AWS design principle that decouples application components (e.g., using queues or asynchronous communication) so that they run independently. This prevents a failure in one service from cascading to other services, improving overall system resilience.
Question 44Question →

A company is planning to migrate a legacy web application to AWS. The application currently runs on an on-premises physical server and uses an Oracle database. To meet a tight datacenter exit deadline, the company decides to migrate the application servers directly to Amazon EC2 instances without any modifications. Simultaneously, they decide to migrate the Oracle database to Amazon RDS for Oracle to reduce database administration overhead. Which migration strategies is the company using for the web application and the database respectively?

Show answer & explanation

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

Answer

Rehosting for the web application and Replatforming for the database
The correct answer states that the company uses Rehosting for the web application and Replatforming for the database. Rehosting (lift-and-shift) is used when moving virtual or physical servers directly to Amazon EC2 without modifications, which fits the rapid migration of the application servers. Replatforming (lift-tinker-and-shift) involves adopting managed services like Amazon RDS to reduce management overhead without changing the core application architecture, which is how the database is being migrated.

Step-by-Step Solution

1
Analyze the web application migration method
The company migrates the application servers directly to Amazon EC2 without modifications.
This is a classic 'lift-and-shift' approach, which corresponds to the Rehosting migration strategy.
2
Analyze the database migration method
The Oracle database is moved to Amazon RDS for Oracle to reduce database administration overhead.
This involves optimizing the platform by adopting a managed service (RDS) while keeping the same database engine and application code. This corresponds to the Replatforming (lift-tinker-and-shift) migration strategy.
3
Combine the identified strategies and select the matching option
The correct combination is Rehosting for the web application and Replatforming for the database.
This correctly maps both migration actions to their respective AWS cloud migration strategies.

Key Concept

Cloud migration strategies (the 6 Rs) allow organizations to choose the right path for moving workloads to AWS, balancing speed, cost, and effort.
Question 45Question →

An enterprise is planning to migrate its on-premises workloads to the AWS Cloud. During the discovery phase, the migration team identifies two specific workloads:

1. A legacy system that is no longer used by any business unit and has no operational value.
2. An on-premises customer relationship management (CRM) application that the company wants to replace entirely with a cloud-based Software-as-a-Service (SaaS) platform.

Which of the following migration strategies describe the correct paths for these workloads? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Retiring the legacy system that is no longer in use; Repurchasing the CRM application by moving to a SaaS platform

Answer

The correct strategies are retiring the legacy system that is no longer in use, and repurchasing the CRM application by moving to a SaaS platform.
The correct strategy for the legacy system is retiring it because it has no business value and can be safely shut down. The correct strategy for the CRM application is repurchasing because the company is replacing its existing on-premises software with a new cloud-native Software-as-a-Service (SaaS) product.

Step-by-Step Solution

1
Analyze the requirement for the first workload (obsolete legacy system).
Identify that because the system has no operational value and is no longer used, it should be turned off or decommissioned. The migration strategy for decommissioning workloads is Retiring.
Retiring helps reduce costs and focus migration effort only on active and valuable workloads.
2
Analyze the requirement for the second workload (CRM application to be replaced by SaaS).
Identify that replacing an on-premises product with a different product or platform, specifically a Software-as-a-Service (SaaS) model, represents the Repurchasing strategy.
Repurchasing, or 'drop-and-shop', refers to switching to a different product, commonly a SaaS platform.

Key Concept

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

An e-learning company plans to migrate its legacy student portal to the AWS Cloud. The IT team wants to adopt AWS Cloud design principles to increase the portal's reliability and reduce operational overhead. Which of the following architectural actions align with these design principles? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Decoupling the frontend user interface from the backend databases using Amazon Simple Queue Service (Amazon SQS) to manage requests.; Using AWS Lambda to process student quiz submissions automatically instead of maintaining running virtual servers.

Answer

Decoupling the frontend user interface from the backend databases using Amazon SQS, and using AWS Lambda to process student quiz submissions automatically instead of maintaining running virtual servers.
Decoupling components with message queues (such as Amazon SQS) is a key aspect of loose coupling, ensuring that a failure in one component does not break the entire system. Implementing serverless functions (such as AWS Lambda) aligns with the 'services, not servers' design principle, allowing the team to focus on application logic while AWS manages server provisioning and scaling.

Step-by-Step Solution

1
Analyze the scenario requirements.
The company wants to apply AWS Cloud design principles (such as loose coupling, services not servers, and elasticity) to modernize a legacy application.
This establishes the criteria for evaluating the choices.
2
Evaluate the architectural options against AWS Cloud design principles.
Using Amazon SQS decouples components (loose coupling), and using AWS Lambda leverages serverless compute (services not servers). Consolidating into a single EC2 instance, manually provisioning fixed capacity, and misinterpreting shared responsibility boundaries are cloud anti-patterns.
This identifies the correct design choices and eliminates the incorrect options.

Key Concept

AWS Cloud Design Principles (Loose Coupling and Services not Servers)
Question 47Question →

A logistics and distribution firm is evaluating a migration to the AWS Cloud. The company's leadership wants to eliminate the high overhead costs associated with powering, cooling, and protecting physical server rooms. Furthermore, they want to leverage the lower pricing that AWS can offer due to its high volume of aggregated customer usage. Which of the following are benefits of migrating to the AWS Cloud that align with these goals? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Stop spending money running and maintaining data centers; Benefit from massive economies of scale

Answer

The benefits of 'Stop spending money running and maintaining data centers' and 'Benefit from massive economies of scale' are the two benefits that align with the company's goals.
The correct options are stopping spending money running and maintaining data centers, and benefiting from massive economies of scale. These directly map to the logistics firm's goals of eliminating physical infrastructure overhead and leveraging lower volume-based pricing.

Step-by-Step Solution

1
Analyze the company's requirements from the scenario: eliminating the overhead of physical server rooms, and utilizing lower pricing from high aggregated usage.
The requirements demand reduction in facility maintenance costs and leveraging volume-based price reductions.
Understanding the customer's specific business drivers helps map them to correct AWS Cloud benefits.
2
Map the analyzed requirements to the official six benefits of AWS Cloud computing.
Eliminating physical server rooms maps to 'Stop spending money running and maintaining data centers'. Lower pricing from aggregated usage maps to 'Benefit from massive economies of scale'.
This confirms the alignment between the scenario's challenges and the standard benefits of cloud adoption.

Key Concept

Benefits of the AWS Cloud
Question 48Question →

A gaming company is launching a new multiplayer game. The team cannot accurately predict how many players will join on launch day. They want to avoid paying for idle servers if player turnout is low, while also ensuring the game does not crash if player turnout is high. Which AWS Cloud benefit is directly demonstrated in this scenario?

Show answer & explanation

Answer: Stop guessing capacity

Answer

Stop guessing capacity
The correct answer is the option stating that customers can stop guessing capacity. This benefit allows organizations to automatically adjust resource capacity in response to real-time traffic demand, avoiding both the cost of idle resources and the performance issues of under-provisioned infrastructure.

Step-by-Step Solution

1
Analyze the business scenario's requirements.
The company has unpredictable user demand and needs to scale resources dynamically to avoid high costs (over-provisioning) or crashes (under-provisioning).
Understanding the core requirement helps map it to the correct AWS Cloud benefit.
2
Map the scenario requirements to the six benefits of AWS Cloud computing.
The scenario directly describes eliminating the need to guess infrastructure capacity by scaling up or down dynamically, which aligns with 'Stop guessing capacity'.
Identifying the correct AWS definition ensures alignment with exam expectations.

Key Concept

Eliminating infrastructure capacity guessing to prevent resource waste and application downtime.
Estimated Time:1m 0s
Question 49Question →

A software development company is designing a new continuous integration and continuous deployment (CI/CD) pipeline on AWS. The pipeline must run multiple automated tests on isolated, clean environments for every code commit, and then clean up all resources immediately after the tests complete. Which two of the following design decisions demonstrate the application of the 'disposable resources' design principle?

Select all that apply

Show answer & explanation

Answer: Using AWS CloudFormation templates to programmatically provision identical testing environments for each commit and deleting the stacks automatically after test execution.; Configuring the test runner to launch temporary Amazon EC2 Spot Instances that boot up, execute the tests, and are terminated immediately upon completion.

Answer

The correct decisions are: using AWS CloudFormation templates to programmatically provision and delete testing environments, and using temporary Amazon EC2 Spot Instances that are terminated immediately after test execution.
The correct design decisions involve using AWS CloudFormation to automatically provision and delete testing environments, and utilizing temporary Amazon EC2 Spot Instances that are terminated immediately after use. Both decisions treat infrastructure as temporary and disposable, allowing environments to be created and destroyed programmatically to optimize costs and maintain consistency.

Step-by-Step Solution

1
Analyze the business and technical requirements of the scenario.
The scenario requires isolated, clean environments for automated testing that are terminated immediately after execution to minimize costs.
Understanding the lifecycle of the required resources is necessary to match them with the appropriate AWS design principle.
2
Evaluate the design decisions against the definition of 'disposable resources'.
The principle of disposable resources states that servers and other components should be treated as temporary assets that can be easily replaced, typically enabled through automation and Infrastructure as Code (IaC).
Applying the core definition of the AWS design principle helps filter out static or manual architectures.
3
Identify options that utilize automated provisioning and teardown of temporary components.
Using AWS CloudFormation to automatically spin up and destroy identical stacks, and using EC2 Spot Instances that are terminated post-execution, are both practices that align with disposable resources.
These actions programmatically manage the resource lifecycle dynamically based on demand rather than maintaining fixed assets.

Key Concept

Disposable resources instead of fixed servers is a core AWS Cloud design principle. It states that infrastructure components should be treated as temporary assets that can be programmatically launched, configured, and terminated on demand, rather than being treated as permanent, static servers.
Estimated Time:2m 30s
Question 50Question →

A media company is migrating a legacy web application to AWS. To avoid managing virtual machines, the team decides to package the application's code into containers and run it on AWS Fargate, and migrate the underlying MySQL database to Amazon Aurora MySQL. The application's core code and business logic remain completely unchanged. Which migration strategy is the company executing?

Show answer & explanation

Answer: Replatforming

Answer

Replatforming
The correct strategy is replatforming because the company is migrating its application to the cloud with minor optimizations—specifically moving to managed container orchestration (AWS Fargate) and a managed database service (Amazon Aurora)—without changing the core application logic.

Step-by-Step Solution

1
Identify the architectural and infrastructure changes made during migration.
The application is moved to containers on AWS Fargate, and the database is moved to Amazon Aurora.
Analyzing infrastructure modifications helps classify the migration type.
2
Examine whether the application's core code or business logic has been modified.
The application's core code and business logic remain completely unchanged.
No code changes rules out the refactoring strategy, which requires re-architecting application code.
3
Distinguish between a direct lift-and-shift (rehosting) and optimizations using managed services (replatforming).
Moving to Fargate and Aurora represents optimizations using managed services without changing application code.
Replatforming involves modifying the platform to reduce operational overhead while keeping the core application intact.

Key Concept

AWS Cloud Migration Strategies
Question 51Question →

A healthcare provider is planning to migrate its patient portal to AWS to handle unpredictable seasonal traffic. The IT director proposes that by deploying this application on AWS and utilizing dynamic resource scaling, the organization will benefit by transitioning their IT spending from operating expenses (OpEx) to capital expenses (CapEx). Which of the following statements directly refutes the IT director's proposal by correctly identifying a core benefit of the AWS Cloud?

Show answer & explanation

Answer: The organization will transition from capital expenses (CapEx) to variable operating expenses (OpEx), which represents the benefit of trading upfront expense for variable expense.

Answer

The organization will transition from capital expenses (CapEx) to variable operating expenses (OpEx), which represents the benefit of trading upfront expense for variable expense.
The correct answer accurately states that migrating to AWS allows organizations to shift their IT spending from capital expenses (CapEx)—such as physical servers and data centers—to variable operating expenses (OpEx), where they only pay for the resources they use. This directly aligns with the AWS Cloud benefit of trading upfront expense for variable expense.

Step-by-Step Solution

1
Analyze the IT director's statement regarding the transition from operating expenses (OpEx) to capital expenses (CapEx).
Identify that the statement is financially backward; cloud computing is characterized by shifting from capital expenses (buying servers upfront) to operating expenses (paying for what is used).
Understanding cloud economics requires recognizing that the primary financial shift is from CapEx to OpEx.
2
Map this financial shift to the official six benefits of the AWS Cloud.
The transition from upfront capital costs to variable running costs aligns directly with the benefit of trading upfront expense for variable expense.
This matches the official AWS Cloud Practitioner definition of cloud benefits.
3
Evaluate the alternative options to identify the correct response.
Select the statement that correctly defines the transition from CapEx to variable OpEx, and reject options that suggest maintaining CapEx, owning physical hardware, or eliminating OpEx entirely.
This ensures the correct cloud benefit is identified while refuting the incorrect financial assertions.

Key Concept

Understanding the financial and operational benefits of the AWS Cloud, specifically trading upfront capital expenses for variable operating expenses.
Question 52Question →

A software development firm wants to reduce the time it takes to deploy new testing environments for its developers. In their on-premises data center, provisioning physical hardware requires waiting several weeks for procurement and configuration. By migrating to the AWS Cloud, the developers can spin up new resource stacks in minutes. Which benefit of the AWS Cloud does this scenario demonstrate?

Show answer & explanation

Answer: Increase speed and agility

Answer

Increase speed and agility
The correct answer is the option stating 'Increase speed and agility'. In a cloud environment, new IT resources are only a click away, which means developers can reduce the time it takes to make those resources available to them from weeks to just minutes. This dramatically increases the speed and agility of the organization, as the cost and time it takes to experiment and develop are significantly lower.

Step-by-Step Solution

1
Analyze the scenario details.
The software development firm transitions from waiting weeks for physical hardware on-premises to provisioning resource stacks in minutes on AWS.
Identifying the key improvement (reducing deployment time from weeks to minutes) is necessary to map it to a specific AWS Cloud benefit.
2
Map the scenario's outcome to the six documented AWS Cloud benefits.
The ability to rapidly deploy and configure resources reduces time-to-market and allows for faster experimentation, which represents the benefit of increased speed and agility.
Comparing the scenario's characteristics against official AWS Cloud benefits helps identify the correct definition.

Key Concept

The benefit of increased speed and agility in AWS allows businesses to reduce the time required to spin up resources, fostering faster innovation and deployment.
Estimated Time:45s
Question 53Question →

An agricultural technology company wants to launch a new crop-monitoring application but has limited initial funding. Instead of purchasing physical servers and networking hardware upfront, the company decides to build the system on AWS and pay only for the computing resources they actually use. Which benefit of the AWS Cloud is directly demonstrated by this approach?

Show answer & explanation

Answer: Trading fixed expense for variable expense

Answer

Trading fixed expense for variable expense
The correct answer is the choice describing the trade-off of fixed expenses for variable expenses. In cloud computing, you pay only for the resources you consume (a variable expense) instead of investing heavily in physical data centers and servers (a fixed capital expense) before you know how you are going to use them.

Step-by-Step Solution

1
Analyze the financial transition described in the scenario.
The company avoids paying upfront capital expenses (fixed cost) for physical hardware and instead pays for resources based on actual consumption (variable cost).
Identifying the shift from upfront capital expenditure to ongoing operational expenditure is key to selecting the correct AWS Cloud benefit.
2
Match this financial model with the official six advantages of cloud computing.
The scenario directly aligns with the cloud benefit defined as 'trading fixed expense for variable expense'.
This matches the AWS definition where businesses pay only for what they consume, allowing them to remain agile without significant upfront investments.

Key Concept

Trading fixed expense for variable expense (CapEx to OpEx)
Question 54Question →

A financial institution is migrating its retail banking platform to AWS. During the portfolio discovery phase, the migration team identifies a proprietary mainframe ledger application that has strict hardware dependencies and cannot be modified or easily migrated. The team decides to keep this mainframe ledger running in their on-premises data center for the foreseeable future, while establishing a dedicated network connection to integrate it with the newly migrated web frontend on AWS.

Which of the following migration strategies is the institution applying to the mainframe ledger application?

Show answer & explanation

Answer: Retaining

Answer

Retaining
The correct strategy is Retaining. Retaining (also known as re-visit) involves keeping applications in their source environment (on-premises) during a migration. This is common for workloads with major hardware/software dependencies that cannot run in the cloud, or applications that need to be revisited later. The mainframe ledger is being kept on-premises for these reasons.

Step-by-Step Solution

1
Analyze the migration scenario and identify the target workload being evaluated.
The target workload is a legacy mainframe ledger application with strict hardware dependencies.
This establishes which component's migration strategy is being questioned.
2
Determine the action taken by the IT team regarding the ledger application's deployment location.
The team decides to keep the ledger running on-premises rather than moving it to AWS.
Understanding where the application resides post-migration narrows down the 6 Rs strategies.
3
Map this decision to one of the AWS 6 Rs migration strategies.
Keeping an application on-premises because of dependency constraints or lack of readiness is defined as the Retaining strategy.
Retaining is chosen when components must remain in the source environment while other parts of the portfolio migrate.

Key Concept

AWS Cloud Migration Strategies (6 Rs) - Retaining
Question 55Question →

An organization is designing a financial transaction processing pipeline on AWS. The system must handle highly unpredictable transaction volumes, ensure that downstream failures in third-party settlement APIs do not disrupt upstream transaction ingestion, and allow developers to test changes in isolated environments that match production scale without incurring permanent infrastructure costs. Which of the following design choices align with AWS Cloud design principles to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Decouple the ingestion layer from the settlement processing layer using message queues to ensure downstream API failures do not block transaction intake.; Use infrastructure as code to provision and terminate temporary, full-scale testing environments on demand, rather than keeping a dedicated staging environment active.

Answer

Decouple the ingestion layer from the settlement processing layer using message queues to ensure downstream API failures do not block transaction intake; and Use infrastructure as code to provision and terminate temporary, full-scale testing environments on demand, rather than keeping a dedicated staging environment active.
The correct choices are to decouple the ingestion and settlement layers using message queues, and to use infrastructure as code to manage temporary testing environments. Using message queues allows the system to achieve loose coupling, meaning the components act independently, and downstream failures do not prevent upstream data ingestion. Utilizing infrastructure as code to spin up and tear down test environments implements the principle of disposable resources, allowing the organization to test at scale only when needed without paying for idle assets.

Step-by-Step Solution

1
Identify the system requirement for handling downstream failures without affecting ingestion.
Downstream settlement failure isolation is needed, indicating a loose coupling and design for failure architecture.
This isolates independent components so that a failure in one does not cascade.
2
Identify the requirement for testing at scale without permanent costs.
The environments must be treated as disposable resources, created on-demand and terminated when finished.
This aligns with the principle of disposable resources, replacing fixed staging servers with temporary ones.
3
Evaluate the architectural options to determine which align with these cloud design principles.
Decoupling with message queues and using infrastructure as code to provision/terminate environments on-demand are selected.
These directly manifest the target AWS design principles.
4
Eliminate choices that represent anti-patterns.
Consolidating layers is a monolithic anti-pattern; pre-provisioning capacity ignores elasticity; expecting AWS to patch EC2 OS violates the shared responsibility model.
These options run counter to core AWS cloud concepts and security frameworks.

Key Concept

AWS Cloud Design Principles (Loose Coupling, Disposable Resources)
Estimated Time:3m 0s
Question 56Question →

A gaming studio is launching a new online multiplayer game. The studio wants to deploy the application to players worldwide with low latency and avoid pre-purchasing physical servers for potential spikes in user traffic.

Which of the following benefits of the AWS Cloud directly support these goals? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Go global in minutes; Stop guessing capacity

Answer

The two correct benefits are deploying globally in minutes and not having to guess capacity limits.
The correct options are the benefits of deploying globally in minutes and not guessing capacity. Deploying globally in minutes allows the studio to host resources closer to players worldwide, reducing latency. Stopping guessing capacity allows the studio to scale resources automatically based on demand rather than paying for idle capacity.

Step-by-Step Solution

1
Analyze the requirements in the scenario.
The studio needs to deploy globally with low latency and handle dynamic traffic spikes without pre-purchasing physical servers.
This helps map the business requirements to the specific benefits of the AWS Cloud.
2
Identify the AWS Cloud benefits that match these requirements.
Deploying globally with low latency maps to the benefit of going global in minutes. Handling traffic dynamically without pre-purchasing or guessing capacity maps to the benefit of stopping guessing capacity.
Matching requirements directly to official cloud benefits yields the correct answer.

Key Concept

Benefits of the AWS Cloud
Question 57Question →

A healthcare company is designing a system on AWS to process patient telemetry data from wearable devices. The system must ingest incoming data streams, store them securely, and automatically generate reports when new data arrives. The architecture should minimize operational overhead and ensure that a failure in the reporting component does not disrupt the ingestion of patient data.

Which of the following architectural decisions align with AWS Cloud design principles to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy Amazon Simple Queue Service (Amazon SQS) to decouple the telemetry data ingestion layer from the report generation process.; Use AWS Lambda to run the report generation code instead of provisioning and managing persistent virtual servers.

Answer

Deploying Amazon SQS to decouple the layers and using AWS Lambda to run report generation code instead of managing servers.
The correct options are deploying Amazon SQS to decouple the ingestion layer from the report generation process and using AWS Lambda to run report generation serverlessly. The SQS option demonstrates loose coupling, which prevents failures in downstream components from affecting upstream ingestion. The Lambda option aligns with the 'services, not servers' principle, eliminating server administration tasks and scaling automatically.

Step-by-Step Solution

1
Analyze the requirements to identify the core AWS design principles needed.
The requirements ask to decouple components (preventing reporting failures from affecting ingestion) and minimize operational overhead (avoiding server management).
This maps directly to the design principles of loose coupling and using managed services (services, not servers).
2
Evaluate the architectural options against the design principle of loose coupling.
Using an asynchronous queue like Amazon SQS decouples the services, ensuring that a failure in report generation doesn't block ingestion. Direct API calls (synchronous) or monolithic deployment violate this principle.
Loose coupling ensures components can scale and fail independently.
3
Evaluate the architectural options against the design principle of 'services, not servers' or reducing operational overhead.
Using AWS Lambda allows running code serverlessly without managing underlying operating systems or virtual instances. Managing or over-provisioning EC2 instances manually violates this principle.
Using managed services reduces administrative burden and increases agility.

Key Concept

AWS Cloud design principles such as loose coupling, design for failure, and services not servers.
Question 58Question →

A digital media company is launching a live video streaming service for a major international tournament. The company expects a massive, unpredictable surge in user traffic during live matches, followed by periods of near-zero activity. The CFO requires that the company only pay for active resource usage during the tournament and avoid upfront infrastructure investments. Which of the following benefits of the AWS Cloud directly address this scenario? (Select TWO)

Select all that apply

Show answer & explanation

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

Answer

The benefits of 'Stop guessing capacity' and 'Trade fixed expense for variable expense' directly address the requirements.
The scenario highlights two distinct requirements: handling unpredictable traffic spikes without wasting capacity, and paying only for active usage without upfront investments. The benefit of 'Stop guessing capacity' allows the system to scale dynamically to meet the exact demand of the tournament matches. The benefit of 'Trade fixed expense for variable expense' allows the company to pay only for the resources they consume rather than buying physical servers upfront.

Step-by-Step Solution

1
Analyze the operational traffic requirements.
Identify that the massive, unpredictable spikes and drops in user traffic require a system that can scale resources on demand, matching 'Stop guessing capacity' (elasticity).
This avoids both under-provisioning during peak matches and over-provisioning during idle periods.
2
Analyze the financial requirements.
Identify that the CFO's goal of paying only for active resource usage and avoiding upfront infrastructure investments matches 'Trade fixed expense for variable expense'.
This shifts cost from capital expenses (CapEx) to operating expenses (OpEx).
3
Evaluate the choices and eliminate distractors.
Confirm that the options corresponding to these two benefits are correct, while eliminating options that reverse CapEx/OpEx, advocate for static peak provisioning, or promote monolithic design.
This ensures the final answer aligns with official AWS cloud benefits and architecture best practices.

Key Concept

The six core benefits of the AWS Cloud, specifically focusing on dynamic scaling (elasticity) and the shift from capital expenses (CapEx) to operational expenses (OpEx).
Estimated Time:2m 30s
Question 59Question →

An aerospace manufacturing firm is evaluating its cloud migration strategy for two specific workloads:

* Workload 1: A customized commercial off-the-shelf (COTS) HR system that is nearing its license expiration. The company has decided to retire the system and purchase a subscription to a cloud-hosted Software-as-a-Service (SaaS) platform, migrating their active user records to the new SaaS platform.
* Workload 2: A proprietary Java application running on an on-premises web server. The engineering team plans to migrate the application to AWS by containerizing it and hosting it on AWS App Runner to reduce runtime management tasks. The application code will remain unchanged, but the team will adjust the application's configuration to use environment variables for database connections.

Which of the following migration strategies describe the planned paths for Workload 1 and Workload 2? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Repurchasing for Workload 1; Replatforming for Workload 2

Answer

Repurchasing for Workload 1 and Replatforming for Workload 2
The correct choices are Repurchasing for Workload 1 and Replatforming for Workload 2. Repurchasing is the process of moving from a legacy or commercial off-the-shelf (COTS) license model to a cloud-based Software-as-a-Service (SaaS) subscription model. Replatforming involves modifying the deployment platform (e.g., containerizing it for a managed service like AWS App Runner) to gain benefits like reduced administrative overhead, without modifying the application's core code architecture.

Step-by-Step Solution

1
Analyze the migration plan and target destination for Workload 1.
Workload 1 is a commercial off-the-shelf (COTS) HR system that is being retired in favor of a subscription to a cloud-hosted SaaS platform.
Moving from an existing licensed application to a different cloud-hosted product (typically SaaS) is the definition of the Repurchasing strategy.
2
Analyze the migration plan and target destination for Workload 2.
Workload 2 is a Java application being containerized and moved to AWS App Runner without changing its core application code.
Deploying the workload to a managed container service to eliminate OS-level maintenance without altering its core architecture represents the Replatforming strategy (lift-tinker-and-shift).
3
Synthesize the findings to match the options.
The correct strategies are Repurchasing for Workload 1 and Replatforming for Workload 2.
This accurately reflects the chosen pathways for both workloads.

Key Concept

Cloud migration strategies (6 Rs)
Estimated Time:2m 0s
Question 60Question →

A healthcare provider is planning to migrate its applications to the AWS Cloud. The migration team has decided on the following plans for two of their systems:

- The patient scheduling application's server VMs will be moved to Amazon EC2 without changes, but its backend relational database will be migrated from a self-managed on-premises server to Amazon Aurora to reduce operational overhead without modifying the application's core code.
- The legacy custom document management system will be decommissioned, and its capabilities will be fully replaced by a third-party software-as-a-service (SaaS) solution purchased through AWS Marketplace.

Which of the following migration strategies are represented in this plan? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Replatforming; Repurchasing

Answer

The correct strategies are Replatforming and Repurchasing.
The correct answers are Replatforming and Repurchasing. Moving the database from an on-premises self-managed server to a managed service like Amazon Aurora without altering the core application code represents Replatforming. Decommissioning the custom legacy document management system and replacing it with a third-party SaaS product from AWS Marketplace represents Repurchasing.

Step-by-Step Solution

1
Analyze the migration plan for the patient scheduling application.
The database is migrated to Amazon Aurora to reduce administrative overhead while the core code remains unchanged.
This corresponds to Replatforming (lift, tinker, and shift), where the database is optimized using a managed service without rewriting the core application.
2
Analyze the migration plan for the legacy document management system.
The legacy custom system is decommissioned and replaced by a third-party SaaS product purchased from AWS Marketplace.
This corresponds to Repurchasing (drop and shop), where an application is discarded in favor of a commercially available SaaS platform.

Key Concept

Understand the 6 Rs cloud migration strategies: Rehosting, Replatforming, Refactoring, Repurchasing, Retaining, and Retiring.
PreviousPage 3 / 18Next