Well Arch Framework

Question 1

The pillars of the AWS Well-Architected Framework

Answer 1

— operational excellence
— security
— reliability, 
— performance efficiency
— cost optimization

Question 2

General Design Principles

Answer 2

• Stop guessing your capacity needs
• Test systems at production scale
• Automate to make architectural experimentation easier
• Allow for evolutionary architectures
• Drive architectures using data

Question 3

________________ 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 across all regions and accounts. This gives you a single source of truth for your AWS and third party resource

Answer 3

AWS CloudFormation
Provides a common language for you to model and provision AWS and third party application resources in your cloud environment.

Question 4

Components of Security Pillar

Answer 4

— Identify and Access management (IAM): Authorized and Authentication using user/group/role/access policy
— Detective Control: Capture, Analyze logs. Audit controls
— Infrastructure protection: firewalls and gateways
— Data Protection: Classification, Encryption (rest and transit), Backup, Recovery as needed
— Incidence Response

Question 5

Security Design Principles

Answer 5

— Implement security at all layers
— Enable traceability - Logging
— least privilege principle
— Focus on securing your system (App/OS/Data), let AWS secure the rest 
— Automate security best practice

Question 6

Reliability Pillar

Answer 6

— Recover from infra and service failure
— Dynamically acquire resources to meet demand
— Apply best practices:
**** Foundations
**** Change Management
**** Failure Management
— Anticipate and prevent failure

Question 7

Reliability Design Principles

Answer 7

— Test recovery procedure
— Auto recover (using alarms and lambda fnc)
— Scale horizontally
— Stop guessing capacity
— Manage change in automation - Arch & Infra change should be made using automation

Question 8

Performance Efficiency Pillars

Answer 8

— Select sols: Best tool for the job
— Review : Constantly innovate services
— Monitor : Watch performance to remediate issues. using Cloud watch, Kenisis, SQS, Lambda etc.
— Consider trade-off

Question 9

Performance Design Principles

Answer 9

— Democratize Advance tech : Let AWS do it instead of internal IT
— Global in mins
— Use Server-less Arch - Lower server mgmt, lower txn costs by consolidating IT spend to provision and manage
— Mechanical Sympathy - Use the best tech for the job

Question 10

Cost Optimization Pillar

Answer 10

— Use cost effective resources (most optimal services, resources etc.)
— Match supply with demand - Using AWS’s Elastic feature
— Expenditure awareness (drill on current and project future cost)
— Optimize Arch over time looking at data

Question 11

Cost Optimization Design Principles

Answer 11

— Adopt consumption model
— Measure overall efficiency
— Reduce spending on DC (data centers) ops
— Analyze and attribute expense (identify ROI using detailed cost analysis)
— Use managed services

Question 12

Ops Excellence Pillar

Answer 12

— Manage and automate change
— Respond to events
— Define standards

Question 13

How to achieve fault tolerance?

Answer 13

Build in redundancies of apps components

Question 14

_________ Ability of system to remain operational even when some components of system fail

Answer 14

Fault Tolerant

Question 15

High Availability Tools

Answer 15

— Elastic Load Balancers (ELB):
Distribute traffic -> send metric to CloudWatch
Triggers - High latency/Over utilization
— Elastic IP addresses:
Static IP, Mask failure by using same IP addresses using different resources
— Route 53: DNS for simple, latency etc. based routing
— Auto Scaling: Terminate/launch resources based on triggers/schedule
— Amazon CloudWatch: Stats gathering system, tracks metrics, used for trigger AutoScaling

Question 16

Fault Tolerant Tools

Answer 16

— Simple queue service (Ensure messaging queue is always available)
— Simple storage service (S3 stores data across multiple devices across facilities in region)
— Relational DB service (RDS) (Auto backup, snapshots, multi- AZ deployments)