1.2 AWS Well-Architected Framework Flashcards

1
Q

How many pillars are there of the AWS Well-Architected Framework? What are they?

A
  1. Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Which AWS WAF pillar is 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?

A

Operational Excellence

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

Which AWS WAF pillar describes hot to take advantage of cloud technologies to protect data, systems, and assets in a away that improve your security posture?

A

Security

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

Which AWS WAF 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. This paper provides in-depth, best practice guidance for implementing reliable workloads on AWS?

A

Reliability

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

Which AWS WAF pillar uses computing resources efficiently to meet system requirements, and to maintain that efficiency as demand changes and technologies evolve?

A

Performance Efficiency

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

Which AWS WAF is the ability to run systems to deliver business value at the lowest price point?

A

Cost Optimization

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

Which AWS WAF is the ability to continually improve sustainability impacts by reducing energy consumption and increasing efficiency across all components of a workload by maximizing the benefits from the provisioned resources and minimizing the total resources required?

A

Sustainability

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

What WAF Term:
A <blank> The code, configuration, and AWS Resources that together deliver against a requirement. A <blank> is often the unit of technical ownership, and is decoupled from other <blanks>.</blanks></blank></blank>

A

Component(s)

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

What WAF Term:
The term <blank> is used to identify a set of components that together deliver business value. A <blank> is usually the level of detail that business and technology leaders communicate about.</blank></blank>

A

Workload

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

What WAF Term:
We think about <blank> as being how components work together in a workload. How components communicate and interact is often the focus of <blank> diagrams.</blank></blank>

A

Architecture

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

What WAF Term:

<Blanks> mark key changes in your architecture as it evolves throughout the product lifecycle (design, implementation, testing, go live, and in production).
</Blanks>

A

Milestones

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

What WAF Term:
Within an organization the <blank> is the collection of workloads that are required for the business to operate.</blank>

A

Technology Portfolio

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

What WAF Term:
The <blank> is categorizing the amount of time, effort, and complexity a task requires for implementation. Each organization needs to consider the size and expertise of the team and the complexity of the workload for additional context to properly categorize the <blank> for the organization.</blank></blank>

A

Level of Effort

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

Which level of effort might take multiple weeks or multiple months. This could be broken out into multiple stories, releases, and tasks?

A

High - Level of Effort

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

Which level of effort might take multiple days or multiple weeks. This could be broken out into multiple releases and tasks.

A

Medium - Level of Effort

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

Which level of effort might take multiple hours or multiple days. This could be broken out into multiple tasks.

A

Low - Level of Effort

17
Q

Which AWS WAF pillar generally is not considered as part of a business context trade-off?

A

Security

18
Q

Who said:
“Good intentions never work, you need good mechanisms to make anything happen.”

A

Jeff Bezos

19
Q

Name the 6 AWS WAF General Design Principles.

A
  1. Stop guessing your capacity needs
  2. Test Systems at production scale
  3. Automate with architectural experimentation in mind
  4. Consider evolutionary architectures
  5. Drive architectures using data
  6. Improve through game days
20
Q

Name the WAF General Design Principle:
If you make a poor capacity decision when deploying a workload, you might end up sitting on expensive idle resources or dealing with the performance implications of limited capacity. With cloud computing, these problems can go away. You can use as much or as little capacity as you need, and scale in and out automatically.

A

Stop guessing your capacity needs

21
Q

Name the WAF General Design Principle:
In the cloud, you can create a production-scale test environment on demand, complete your testing, and then decommission the resources. Because you only pay for the test environment when it’s running, you can simulate your live environment for a fraction of the cost of testing on premises.

A

Test systems at production scale

22
Q

Name the WAF General Design Principle:
Automation permits you to create and replicate your workloads at low cost and avoid the expense of manual effort. You can track changes to your automation, audit the impact, and revert to previous parameters when necessary.

A

Automate with architectural experimentation in mind

23
Q

Name the WAF General Design Principle:
In a traditional environment, architectural decisions are often implemented as static, onetime events, with a few major versions of a system during its lifetime. As a business and its context continue to evolve, these initial decisions might hinder the system’s ability to deliver changing business requirements. In the cloud, the capability to automate and test on demand lowers the risk of impact from design changes. This permits systems to evolve over time so that businesses can take advantage of innovations as a standard practice.

A

Consider evolutionary architectures

24
Q

Name the WAF General Design Principle:
In the cloud, you can collect data on how your architectural choices affect the behavior of your workload. This lets you make fact-based decisions on how to improve your workload. Your cloud infrastructure is code, so you can use that data to inform your architecture choices and improvements over time.

A

Drive architectures using data

25
Q

Name the WAF General Design Principle:
Test how your architecture and processes perform by regularly scheduling game days to simulate events in production. This will help you understand where improvements can be made and can help develop organizational experience in dealing with events.

A

Improve through game days

26
Q

What are the 5 Design Principles for the WAF Operational Excellence pillar?

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

What are the 4 Best Practices for the WAF Operational Excellence pillar?

A
  1. Organization
  2. Prepare
  3. Operate
  4. Evolve
28
Q

What are the 7 Design Principles for the WAF Security pillar?

A
  1. Implement a strong identity foundation
  2. Maintain traceability
  3. Apply security at all layers
  4. Automate security best practices
  5. Protect data in transit and at rest
  6. Keep people away from data
  7. Prepare for security events
29
Q

What are the 7 Best Practices for the WAF Security pillar?

A
  1. Security Foundations
  2. Identity and Access Management
  3. Detection
  4. Infrastructure protection
  5. Data protection
  6. Incident response
  7. Application security
30
Q

What are the 5 Design Principles for the WAF Reliability pillar?

A
  1. Automatically recover from failure
  2. Test recovery procedures
  3. Scale horizontally to increase aggregate workload availability
  4. Stop guessing capacity
  5. Manage change in automation
31
Q

What are the 4 Best Practices for the WAF Reliability pillar?

A
  1. Foundations
  2. Workload architecture
  3. Change management
  4. Failure management
32
Q

What are the 5 Design Principles for the WAF Performance Efficiency pillar?

A
  1. Democratize advanced technologies
  2. Go global in minutes
  3. User serverless architectures
  4. Experiment more often
  5. Consider mechanical sympathy
33
Q

What are the 4 Best Practices for the WAF Performance Efficiency pillar?

A
  1. Selection
  2. Review
  3. Monitoring
  4. Tradeoffs
34
Q

What are the 5 Design Principles for the WAF Cost Optimization pillar?

A
  1. Implement Cloud Financial Management
  2. Adopt a consumption model
  3. Measure overall efficiency
  4. Stop spending money on undifferentiated heavy lifting
  5. Analyze and attribute expenditure
35
Q

What are the 5 Best Practices for the WAF Cost Optimization pillar?

A
  1. Practice cloud financial management
  2. Expenditure and usage awareness
  3. Cost-effective resources
  4. Manage demand and supply resources
  5. Optimize over time
36
Q

What are the 6 Design Principles for the WAF Sustainability pillar?

A
  1. Understand your impact
  2. Establish sustainability goals
  3. Maximize utilization
  4. Anticipate and adopt new, more efficient hardware and software offerings
  5. Use managed services
  6. Reduce the downstream impact of your cloud workloads
37
Q

What are the 6 Best Practices for the WAF Sustainability pillar?

A
  1. Region selection
38
Q
A