AWS Cloud Practitioner > Cloud Architecture & Design > Flashcards

Cloud Architecture & Design Flashcards

Identify core architectural principles and how AWS services support fault tolerance and high availability. (24 cards)

Study These Flashcards
2
Q

Which design principles are enabled by the AWS Cloud to improve the operation of workloads?

(Select TWO.)

  1. Minimize platform design
  2. Loose coupling
  3. Customized hardware
  4. Remove single points of failure
  5. Minimum viable product
A

2. Loose coupling
4. Remove single points of failure

  • Loose coupling is correct, it is when you break systems down into smaller components that are loosely coupled together. This reduces interdependencies between systems components. This is achieved in the cloud using messages buses, notification and messaging services.
  • Removing single points of failure is also correct, it ensures fault tolerance and high availability. This is easily achieved in the cloud as the architecture and features of the cloud support the implementation of highly available and fault tolerant systems.
  • Customized hardware is incorrect. You cannot customize hardware in the cloud.
  • Minimize platform design is incorrect. This is not an operational advantage for workloads in the cloud.
  • Minimum viable product is incorrect. This is not an operational advantage for workloads in the cloud.

Reference:
Architecting for the Cloud

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

A user is planning to launch three EC2 instances behind a single Elastic Load Balancer. The deployment should be highly available.

How should the user achieve this?

  1. Launch the instances across multiple Availability Zones in a single AWS Region.
  2. Launch the instances as EC2 Spot Instances in the same AWS Region and the same Availability Zone.
  3. Launch the instances in multiple AWS Regions and use Elastic IP addresses.
  4. Launch the instances as EC2 Reserved Instances in the same AWS Region, but in different Availability Zones.
A

1. Launch the instances across multiple Availability Zones in a single AWS Region.

To make the deployment highly available the user should launch the instances across multiple Availability Zones in a single AWS Region. Elastic Load Balancers can only serve targets in a single Region so it is not possible to deploy across Regions.

  • Launch the instances as EC2 Spot Instances in the same AWS Region and the same Availability Zone is incorrect. The pricing model is not relevant to high availability and deploying in a single AZ does not result in a highly available deployment.
  • Launch the instances in multiple AWS Regions and use Elastic IP addresses is incorrect. You cannot use an ELB with instances in multiple Regions and using an EIP does not help.
  • Launch the instances as EC2 Reserved Instances in the same AWS Region, but in different Availability Zones is incorrect. Using reserved instances may not be appropriate as we do not know whether this is going to be a long-term workload or not.

Reference:
Regions and Availability Zones

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Which resource should a new user on AWS use to get help with deploying popular technologies based on AWS best practices, including architecture and deployment instructions?

  1. AWS CloudFormation
  2. AWS Artifact
  3. AWS Config
  4. AWS Partner Solutions
A

4. AWS Partner Solutions

Partner Solutions are built by Amazon Web Services (AWS) solutions architects and partners to help you deploy popular technologies on AWS, based on AWS best practices for security and high availability. These accelerators reduce hundreds of manual procedures into just a few steps, so you can build your production environment quickly and start using it immediately.
Each Partner Solutions includes AWS CloudFormation templates that automate the deployment and a guide that discusses the architecture and provides step-by-step deployment instructions.

  • AWS CloudFormation is incorrect. CloudFormation is used to deploy infrastructure from templates, the Quick Starts use CloudFormation.
  • AWS Artifact is incorrect. Artifact provides on-demand access to AWS security and compliance reports.
  • AWS Config is incorrect. Config is a service used for compliance relating the configuration of AWS resources.

Reference:
AWS Solutions Library

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Which of the following statements best describes the concept of agility in relation to cloud computing on AWS?

(Select TWO.)

  1. The speed at which AWS rolls out new features.
  2. The ability to experiment quickly.
  3. The elimination of wasted capacity.
  4. The ability to automatically scale capacity.
  5. The speed at which AWS resources can be created.
A

2. The ability to experiment quickly.
5. The speed at which AWS resources can be created.

In a cloud computing environment, new IT resources are only a click away, which means that you reduce the time to make those resources available to your developers from weeks to just minutes. This results in a dramatic increase in agility for the organization, since the cost and time it takes to experiment and develop is significantly lower.

  • The speed at which AWS rolls out new features is incorrect. This is not a statement that describes agility.
  • The elimination of wasted capacity is incorrect. This is also known as right-sizing and it is a cost benefit of running in the cloud. It is not a statement that describes agility.
  • The ability to automatically scale capacity is incorrect. Auto scaling ensures you have the right amount of capacity available.

Reference:
Six advantages of cloud computing

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

A company is designing a new a service that must align with the operational excellence pillar of the AWS Well-Architected Framework.

Which design principles should the company follow?

(Select TWO.)

  1. Anticipate failure.
  2. Make large-scale changes.
  3. Perform operations as code.
  4. Perform manual operations.
  5. Create static operational procedures.
A

1. Anticipate failure.
3. Perform operations as code.

AWS Well-Architected helps cloud architects build secure, high-performing, resilient, and efficient infrastructure for their applications and workloads. There are 5 pillars and under the operational excellence pillar the following best practices are recommended:

  1. Perform operations as code.
  2. Make frequent, small, reversible changes.
  3. Refine operations procedures frequently.
  4. Anticipate failure.
  5. Learn from all operational failures.

  • Make large-scale changes is incorrect. This is not an operational best practice.
  • Perform manual operations is incorrect. This is not an operational best practice.
  • Create static operational procedures is incorrect. This is not an operational best practice.

Reference:
AWS Well-Architected

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Which of the following deployments involves the reliability pillar of the AWS Well-Architected Framework?

  1. Amazon RDS Multi-AZ deployment
  2. Amazon EBS provisioned IOPS volume
  3. Attach a WebACL to a CloudFront distribution
  4. Use CloudFormation to deploy infrastructure
A

1. Amazon RDS Multi-AZ deployment

An Amazon Relational Database Service (RDS) deployment across multiple availability zones is a good example of using the reliability pillar of the AWS Well-Architected Framework. The specific design principle being followed here is Automatically recover from failure.

  • Amazon EBS provisioned IOPS volume is incorrect. This would be an example of performance efficiency.
  • Attach a WebACL to a CloudFront distribution is incorrect. This would be an example of using the security pillar.
  • Use CloudFormation to deploy infrastructure is incorrect. This would be an example of using the operational excellence pillar.

Reference:
The 6 Pillars of the AWS Well-Architected Framework

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

A company plan to move the application development to AWS. Which benefits can they achieve when developing and running applications in the AWS Cloud compared to on-premises?

(Select TWO.)

  1. AWS automatically replicates all data globally.
  2. AWS will fully manage the entire application.
  3. AWS makes it easy to implement high availability.
  4. AWS can accommodate large changes in application demand.
  5. AWS takes care of application security patching.
A

3. AWS makes it easy to implement high availability.
4. AWS can accommodate large changes in application demand.

AWS provides many options for high availability including multiple availability zones within Regions and multiple Regions around the world. There are also many options to leverage durable data storage, message buses, databases.
AWS have a huge global infrastructure with massive amounts of capacity. It is therefore very easy to accommodate large changes in application demand and this can often be seamless to your application.

  • AWS automatically replicates all data globally is incorrect. This is not true; data is not replicated globally unless you configure it do so.
  • AWS will fully manage the entire application is incorrect. This is not true; AWS will not manage your application.
  • AWS takes care of application security patching is incorrect. AWS take care of security patches for the underlying infrastructure but not your application.

Reference:
Six advantages of cloud computing

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

A Cloud Practitioner is re-architecting a monolithic application. Which design principles for cloud architecture do AWS recommend?

(Select TWO.)

  1. Implement manual scalability.
  2. Implement loose coupling.
  3. Use self-managed servers.
  4. Rely on individual components.
  5. Design for scalability.
A

2. Implement loose coupling.
5. Design for scalability.

Dependencies such as queuing systems, streaming systems, workflows, and load balancers are loosely coupled. Loose coupling helps isolate behavior of a component from other components that depend on it, increasing resiliency and agility
AWS recommend that you architect applications that scale horizontally to increase aggregate workload availability. This scaling should be automatic where possible.

  • Implement manual scalability is incorrect. AWS do not recommend manual processes. Everything should be automated as much as possible.
  • Use self-managed servers is incorrect. AWS do not recommend using self-managed servers. They do recommend using serverless services if you can.
  • Rely on individual components is incorrect. This is not a best practice; you should never rely on individual components. It is better to build redundancy into the system so the failure of an individual component does not affect the functioning of the application.

Reference:
The 6 Pillars of the AWS Well-Architected Framework

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What should a Cloud Practitioner ensure when designing a highly available architecture on AWS?

  1. Servers have low-latency and high throughput network connectivity.
  2. The failure of a single component should not affect the application.
  3. There are enough servers to run at peak load available at all times.
  4. A single monolithic application component handles all operations.
A

2. The failure of a single component should not affect the application.

In a highly available system the failure of a single component should not affect the application. This means that if a single component such as an application server fails, there should be other applications servers available that can seamlessly take over operations and ensure the application continues to operate.

  • Servers have low-latency and high throughput network connectivity is incorrect. It is not necessary for all architectures to have low-latency and high throughput network connectivity and this does not ensure high availability.
  • There are enough servers to run at peak load available at all times is incorrect. This would be wasteful in terms of resources and cost. There should be enough servers available to handle current load with adequate capacity to operate functionally in the event of a system failure. Additional servers can be launched automatically. as the application demand increases.
  • A single monolithic application component handles all operations is incorrect. This is a bad design practice that reduces the availability of the system as the failure of update of any individual component can bring the whole system down.

Reference:
High availability and scalability on AWS

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Which cloud architecture design principle is supported by deploying workloads across multiple Availability Zones?

  1. Automate infrastructure.
  2. Design for agility.
  3. Enable elasticity.
  4. Design for failure.
A

4. Design for failure.

Amazon EC2 instances can be deployed in an Amazon VPC across multiple Availability Zones. You would then typically use an Elastic Load Balancer (ELB) to distribute load between the available instances. This architecture enables high availability as if a single instance fails or if something fails that causes an outage in an entire Availability Zone, the application still has available instances to continue to service demand.

  • Design for agility is incorrect. This is not an example of agility; it is an example of high availability and fault tolerance.
  • Automate infrastructure is incorrect. This is not an example of automating.
  • Enable elasticity is incorrect. This is not an example of elasticity. Elasticity would be enabled by using Amazon EC2 Auto Scaling.

Reference:
AWS Well-Architected

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Which of the following statements are security principles within the AWS Well-Architected Framework?

(Select TWO.)

  1. Analyze and attribute expenditures.
  2. Monitor, alert, and audit actions and changes to AWS resources.
  3. Deploy globally in minutes.
  4. Protect data in transit and at rest.
  5. Perform operations as code.
A

2. Monitor, alert, and audit actions and changes to AWS resources.
4. Protect data in transit and at rest.

Ongoing monitoring with alerting and remediation actions is a critical part of a coherent security posture. With ongoing monitoring, you can make sure any potential threats or security concerns can be remediated as soon as possible.
Secondly, protecting data both in transit and at rest is a vital part of a security procedure which ensures that no data is read by anyone who shouldn’t have access to it.

  • Analyze and attribute expenditures is incorrect as this relates specifically to cost optimization
  • Deploy globally in minute is incorrect. This advantage of the cloud can help with reliability, scalability, and performance efficiency however security is not affected by the ability to host globally distributed applications.
  • Perform operations as code is incorrect. Operations as code can help tangentially with providing a strong security posture but performing operations as code is more associated with reliability.

Reference:
AWS Well-Architected

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Which of the below is an example of an architectural benefit of moving to the cloud?

  1. Elasticity
  2. Monolithic services
  3. Proprietary hardware
  4. Vertical scalability
A

1. Elasticity

A key architectural benefit of moving to the cloud is that you get elasticity. This means your applications can scale as demand increases and scale back as demand decreases. This reduces cost as you only pay for what you use, when you need it.

  • Monolithic services is incorrect. Monolithic services are not a design patter of the public cloud. Developers and architects prefer service oriented or micro-service architectures instead.
  • Proprietary hardware is incorrect. You do not get to choose your hardware in AWS as the infrastructure on which your services run is managed and operated by AWS. So you cannot use proprietary hardware.
  • Vertical scalability is incorrect. Vertical scalability is not unique to the cloud, nor is it something we aspire to as architects. Most of the time horizontal scalability is preferred and is something that the AWS cloud provides for many services.

Reference:
AWS Architecture Center

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Which pillar of the AWS Well-Architected Framework includes the design principle of defining workloads, applications, and infrastructure as code (IaC)?

  1. Operational excellence
  2. Reliability
  3. Performance efficiency
  4. Security
A

1. Operational excellence

There are five design principles for operational excellence in the cloud, the first one is:
Perform operations as code: In the cloud, you can apply the same engineering discipline that you use for application code to your entire environment. You can define your entire workload (applications, infrastructure) as code and update it with code. You can implement your operations procedures as code and automate their execution by triggering them in response to events. By performing operations as code, you limit human error and enable consistent responses to events.

  • Reliability is incorrect, as using Infrastructure as Code doesn’t inherently increase reliability.
  • Performance efficiency is incorrect also as using Infrastructure as Code doesn’t make your applications any more performant.
  • Security is incorrect also as Security is not increased by using Infrastructure as Code.

Reference:
AWS Well-Architected

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

An ecommerce company is using Auto Scaling groups to manage a group of web servers running on Amazon EC2 and are additionally placed behind an Elastic Load balancer.
This architecture follows which AWS Well-Architected Framework best practice?

  1. Secure the workload
  2. Decouple infrastructure components
  3. Design for failure
  4. Think parallel
A

3. Design for failure

Designing for failure is an important part of architecting for cloud workloads and the easiest way to do this when using Amazon EC2 instances is to put the within an Auto Scaling group and then place them behind an Elastic Load balancer.
An Auto Scaling group contains a collection of EC2 instances that are treated as a logical grouping for the purposes of automatic scaling and management. An Auto Scaling group also enables you to use Amazon EC2 Auto Scaling features such as health check replacements and scaling policies. Both maintaining the number of instances in an Auto Scaling group and automatic scaling are the core functionality of the Amazon EC2 Auto Scaling service.
An Elastic load balancer distributes the load to each of these web servers in a distributed manner, allowing for scalable and flexible architecture.
The combination of both features of Amazon EC2 will enable high availability and is an example of designing for failure.

  • Secure the workload is incorrect as whilst there are some security benefits of using an Elastic Load Balancer, the main reason why we would use one is to attach it to an Auto Scaling group and to distribute traffic to the instances within it.
  • Decouple infrastructure components is incorrect. Auto Scaling Groups and Elastic Load Balancers are typically not used to decouple architecture, and there are other services which are specifically designed to do this such as the Amazon Simple Queue Service (SQS) or AWS Lambda.
  • Think parallel is incorrect. This is about experimenting with different architectures at the same time. There is no reference made in this question statement regarding any other different architectures that are being compared to the setup of the Elastic Load Balancers and the Auto Scaling group.

Reference:
Use Elastic Load Balancing to distribute incoming application traffic in your Auto Scaling group

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

AWS Global Infrastructure consists of which of the following components?

  1. Amazon Alexa
  2. AWS Regions
  3. Amazon LightSail
  4. AWS Organizations
A

2. AWS Regions

AWS has the concept of a Region, which is a physical location around the world where we cluster Availability Zones. Each AWS Region consists of multiple, isolated, and physically separate AZs within a geographic area. This is a key part of the AWS Global Infrastructure.

  • Amazon Alexa is incorrect, is a virtual assistant technology, and is not part of the AWS Global infrastructure.
  • Amazon LightSail is incorrect. Amazon LightSail is a virtual private server (VPS) provider and is the easiest way to get started with AWS for developers, small businesses, students, and other users who need a solution to build and host their applications on cloud. Amazon LightSail is not part of the AWS Global Infrastructure.
  • AWS Organizations is incorrect. AWS Organizations is a way of managing multiple accounts under your root AWS account and is not a part of the AWS global infrastructure.

Reference:
Regions and Zones

Save time with our AWS cheat sheets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Which AWS service helps you deploy application configuration changes with features like validation checks and timely deployment while avoiding the need to write additional code or restart application services?

  1. AWS CodeStar
  2. AWS AppConfig
  3. AWS CodeCommit
  4. AWS CloudFormation
Study These Flashcards
A

2. AWS AppConfig

AWS AppConfig is the correct answer because it allows users to deploy application configuration changes quickly and reliably without needing to write additional code or restart services. It supports validation checks to ensure configuration data is syntactically and semantically correct before deployment, avoiding potential outages.

  • AWS CodeStar is incorrect because, while it provides a unified interface for managing software development activities in one place, it does not specifically deal with deploying application configuration changes with the features described in the question.
  • AWS CodeCommit is incorrect because it is a source control service hosted by AWS for privately storing and managing assets in the cloud, not for deploying and managing application configurations specifically.
  • AWS CloudFormation is incorrect because, even though it allows you to use programming languages or a simple text file to model and provision, in an automated and secure manner, all the resources needed for your applications, it doesn’t specialize in deploying application configurations with validation checks as described in the scenario.

Reference:
What is AWS AppConfig?

18
Q

Which AWS service provides a cloud-based integrated development environment (IDE) that lets you write, run, and debug your code with just a browser, without needing to install any software or configure servers?

  1. AWS Cloud9
  2. AWS CodeStar
  3. AWS CodeBuild
  4. Amazon WorkSpaces
Study These Flashcards
A

1. AWS Cloud9

AWS Cloud9 is the correct choice because it is a cloud-based integrated development environment (IDE) that allows developers to write, run, and debug their code using only a web browser. It eliminates the need to install software and configure servers, offering a seamless and convenient solution for developers.

  • AWS CodeStar is incorrect because, while it enables you to quickly develop, build, and deploy applications on AWS, it is not a service that provides a cloud-based IDE where you can write, run, and debug code directly from a web browser.
  • AWS CodeBuild is incorrect because it is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. It does not offer a cloud-based IDE for writing, running, and debugging code.
  • Amazon WorkSpaces is incorrect because, although it is a managed, secure Desktop-as-a-Service (DaaS) solution, it does not inherently provide a cloud-based IDE focused on coding, running, and debugging development projects directly in a browser.

Reference:
AWS Cloud9

19
Q

Which of the following are architectural best practices for the AWS Cloud?

(Select TWO.)

  1. Deploy into multiple Availability Zones
  2. Deploy into a single availability zone
  3. Close coupling
  4. Design for fault tolerance
  5. Create monolithic architectures
Study These Flashcards
A

1. Deploy into multiple Availability Zones
4. Design for fault tolerance

It is an architectural best practice to deploy your resources into multiple availability zones and design for fault tolerance. These both ensure that if resources or infrastructure fails, your application continues to run.

  • Deploy into a single availability zone is incorrect. You should not deploy all of your resources into a single availability zone as any infrastructure failure will take down access to your resources.
  • Close coupling is incorrect. Close coupling is not an architectural best practice – loose coupling is. With loose coupling you reduce interdependencies between components of an application and often put a middle layer such as a message bus between components.
  • Create monolithic architectures is incorrect. You should not create monolithic architectures. With monolithic architectures you have a single instance running multiple components of the application, if any of these components fails, your application fails. It is better to design microservices architectures where components are spread across more instances.

Reference:
AWS Well-Architected

Save time with our AWS cheat sheets.

20
Q

Which of the following is a benefit of moving to the AWS Cloud?

  1. Outsource all IT operations
  2. Pay for what you use
  3. Capital purchases
  4. Long term commitments
Study These Flashcards
A

2. Pay for what you use

With the AWS cloud you pay for what you use. This is a significant advantage compared to on-premises infrastructure where you need to purchase more equipment than you need to allow for peak capacity. You also need to pay for that equipment upfront.

  • Outsource all IT operations is incorrect. You do not outsource all IT operations when moving to the AWS Cloud. AWS provide some higher-level managed services which reduces your operations effort but does not eliminate it.
  • Capital purchases is incorrect. Capital purchases are not a benefit of moving to the cloud. The AWS Cloud is mostly an operational expenditure which is favored by many CFOs.
  • Long term commitments is incorrect. You do not need to enter into long term commitments with the AWS Cloud. There are options for 1 or 3 year commitments to lower prices with some services but this is not an advantage of the cloud.

Reference:
AWS Pricing

Save time with our AWS cheat sheets.

21
Q

Which of the following is an architectural best practice recommended by AWS?

  1. Design for success
  2. Design for failure
  3. Think servers, not services
  4. Use manual operational processes
Study These Flashcards
A

2. Design for failure

It is recommended that you design for failure. This means always considering what would happen if a component of an application fails and ensuring there is resilience in the architecture.

  • Design for success is incorrect. Design for success sounds good, but this is not an architectural best practice. As much as we want our applications to be successful, we should always be cognizant of the potential failures that might occur and ensure we are prepared for them.
  • Think servers, not services is incorrect. AWS do not recommend that you think servers, not services. What they do recommend is that you think services, not servers. This means that you should consider using managed services and serverless services rather than just using Amazon EC2.
  • Use manual operational processes is incorrect. You should not use manual operational processes; this is not an architectural best practice. You should automate as much as possible in the cloud.

Reference:
AWS Well-Architected

Save time with our AWS cheat sheets.

22
Q

As part of its cloud architecture, a company wants its workloads to be resilient, perform correctly, consistently, and recover from errors in a timely manner.

Which pillar of the AWS Well-Architected Framework are these requirements related to?

  1. Security
  2. Performance efficiency
  3. Operational excellence
  4. Reliability
Study These Flashcards
A

4. Reliability

The Reliability pillar encompasses the ability of a workload to perform its intended function correctly and consistently when it’s expected to. This includes the ability to operate and test the workload through its total lifecycle.

  • Security is incorrect. Security simply refers to the ability to ensure your workloads and infrastructure are safe from attack or from exploitation.
  • Operational excellence is incorrect. The operational excellence pillar focuses on running and monitoring systems, and continually improving processes and procedures. Key topics include automating changes, responding to events, and defining standards to manage daily operations, and it does not include initial resilience and recovery of workloads.
  • Performance Efficiency is incorrect. The performance efficiency pillar focuses on structured and streamlined allocation of IT and computing resources. Key topics include selecting resource types and sizes optimized for workload requirements, monitoring performance, and maintaining efficiency as business needs evolve.

Reference:
AWS Well-Architected

Save time with our AWS cheat sheets.

23
Q

The AWS shared responsibility model is included in which pillar of the AWS Well-Architected Framework?

  1. Operational excellence
  2. Performance efficiency
  3. Reliability
  4. Security
Study These Flashcards
A

4. Security

Security and compliance are shared responsibilities between AWS and the customer. Depending on the services deployed, this shared model can help relieve the customer’s operational burden. This is because AWS operates, manages, and controls the components from the host operating system and virtualization layer down to the physical security of the facilities in which the service operates.

  • Operational excellence is incorrect. The Operational Excellence pillar includes the ability to support development and run workloads effectively, gain insight into their operations, and to continuously improve supporting processes and procedures to deliver business value.
  • Performance efficiency is incorrect. The performance efficiency pillar focuses on the efficient use of computing resources to meet requirements, and how to maintain efficiency as demand changes and technologies evolve.
  • Reliability is incorrect. Reliability is the ability of a workload to perform its intended function correctly and consistently when it’s expected to.

Reference:
AWS Well-Architected

Save time with our AWS cheat sheets.

24
Q

Which AWS components aid in the construction of fault-tolerant applications?

(Select TWO.)

  1. Elastic IP addresses
  2. ARNs
  3. AMIs
  4. Tags
  5. Block device mappings
Study These Flashcards
A

1. Elastic IP addresses
3. AMIs

Elastic IP addresses can be easily remapped between EC2 instances in the event of a failure. Amazon Machine Images (AMIs) can be used to quickly launch replacement instances when there is a failure
Amazon Resource Names (ARNs), tags and block device mappings don’t really help with fault tolerance

Reference:
Fault-Tolerant Components on AWS

Save time with our AWS cheat sheets.

25
Q

Which AWS components aid in the construction of fault-tolerant applications?

(Select TWO.)

  1. Elastic IP addresses
  2. ARNs
  3. AMIs
  4. Tags
  5. Block device mappings
Study These Flashcards
A

1. Elastic IP addresses
3. AMIs

Elastic IP addresses can be easily remapped between EC2 instances in the event of a failure. Amazon Machine Images (AMIs) can be used to quickly launch replacement instances when there is a failure
Amazon Resource Names (ARNs), tags and block device mappings don’t really help with fault tolerance

Reference:
Fault-Tolerant Components on AWS

Save time with our AWS cheat sheets.

AWS Cloud Practitioner
flashcards
Decks in class (17)
# Cards
Brainscape helps you reach your goals faster, through stronger study habits.
© 2026 Bold Learning Solutions. Terms and Conditions