Well Architected FrameWork

Question 1

Business Benefits of the cloud

Answer 1

1) Almost zero upfront infrastructure cost.
2) Just in time infrastructure
3) More Efficient resource utilisation
4) Usage-based costing
5) Reduced time to market.

Question 2

Technical Benefits of the cloud

Answer 2

1) Automation - scriptable infrastructure
2) Auto-scaling
3) Proactive scaling
4) More efficient development lifecycle
5) improved testability
6) DR and BCP
7) Overflow to cloud/hybrid

Question 3

Design for failure

Answer 3

1) Be a pessimist when designing architectures in the cloud. assume things will fail, and plan for that.

Question 4

Implementing Elasticity

Answer 4

1) Proactive cyclic scaling - scaling at fixed intervals.
2) Proactive Event based scaling - scaling for an event.
3) Auto-scaling based on demand. (leverage monitoring services to trigger scaling based on metrics)

Question 5

5 pillars of the well-architected framework

Answer 5

1) Security
2) Reliability
3) Performance Efficiency
4) Cost Optimisation
5) Operational Excellence

Question 6

General Design Principles:

Answer 6

1) stop guessing your capacity
2) test systems at production scale.
3) Automate to make architectural experimentation easier.
4) allow for evolutionary architectures
5) data-driven architectures
6) improve through “Game days” to simulate events in production.

Question 7

Well Architected Framework | Pillar 1 | Security

Answer 7

1) Apply security at all levels.
2) Enable Traceabiliy
3) Automate responses to security events (leverage SNS)
4) Focus on securing your system
5) automate security best practices.

Question 8

AWS Shared Responsibility model | AWS

Answer 8

• Compute
• Storage
• Database
• Networking
  Regions
  availability Zones
  Edge Locations

Question 9

AWS Shared Responsibility model | Customer

Answer 9

• Customer (Your) Data
• Platform, Applications, I&M
• OS, Network and Firewall Configuration
• Client side data encryption, integrity and authentication.
• Server Side Encryption (file system and/or data)
• Network Traffic Protection (Encryption, Integrity, Identity)

Question 10

AWS Security Pillar | Definition:

Answer 10

It has 4 areas:

1) Data Protection (data classification, least privilege access, encrypt everything)
2) Privilege Management (ACL,RBAC,password mgmt)
3) Infrastructure Protection (VPC protection)
4) Detective Controls (cloud(trail|watch), aws config.

Question 11

AWS Reliability Pillar | design principles:

Answer 11

1) Test recovery procedures
2) automatically recover from failure.
3) scale horizontally to increase aggregation system availability.
4) stop guessing capacity.

Question 12

AWS Reliability Pillar | key AWS Services

Answer 12

Foundation - IAM, VPC
Change Management - AWS CloudTrail
Failure Management - AWS Cloud Formation

Question 13

AWS Reliability Pillar | 3 key Areas

Answer 13

1) Foundation
2) Change Management
3) Failure Management

Question 14

What is the AWS Performance Efficiency Pillar

Answer 14

Focuses on how to use compute resources efficiently to meet your requirements.

Question 15

AWS Performance Efficiency Pillar | Design Principles

Answer 15

1) Democratize advanced technologies
2) Go Global in Minutes
3) Use Server-less architectures
4) Experiment more Often

Question 16

AWS Performance Efficiency Pillar | 4 areas

Answer 16

1) Compute (right server for the job)
2) Storage (access method, patterns of access, frequency)
3) Database (right DB for the job)
4) Space-time trade off

Question 17

What is the AWS Cost Optimisation Pillar

Answer 17

Cost reduction and minimalism

Question 18

AWS Cost Optimisation Pillar | Design Principles

Answer 18

1) Transparently attribute expenditure
2) Use Managed Services to reduce cost of ownership
3) trade CapEx for OpEx
4) Benefit from economies of scale (AWS purchasing)
5) Stop spending money on data centre operations

Question 19

AWS Cost Optimisation Pillar | 4 Areas

Answer 19

1) Matched supply and demand (provision vs scale)
2) cost-effective resources (cost instance type)
3) expenditure awareness
4) optimisation over time. (hundreds of new services per year (best service today is not the best tomorrow))

Question 20

What is the AWS Operational Excellence Pillar?

Answer 20

1) Operational practices.
2) Operation procedures used to manage production workloads.
3) planned vs unplanned changes
4) Change execution and responses.

Question 21

AWS Operational Excellence Pillar | Design Principal

Answer 21

1) Perform Operations with code when repeatable
2) Align operational processes to business objectives
3) Make regular, small incremental changes
4) Test for responses to unexpected events
5) learn from operational events and failures
6) Keep operational procedures up to date.

Question 22

AWS Operational Excellence Pillar | Definition

Answer 22

The three best practise areas for operational excellence in the cloud:

1) Preparation (checklists, run books - daily tasks, play books)
2) Operation
3) Response

Question 23

AWS Operational Excellence Pillar | practice to service map.

Answer 23

Preparation - autoscaling, AWS config, tagging, service catalogue.
Operation - CI/CD pipelines. aws code commit, code deploy, code pipeline.
Response - cloudwatch + alarms + SNS