Architected Framework Flashcards

1
Q

Architected Framework general guiding principle

A
  • stope guessing your capacity
  • Test systems at production scale
  • Automate to make architectural experimentation easier
  • Allow for evolutionary architectures ( change requirement )
  • Drive architecture using data
  • Improve through game days
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

AWS cloud best particles - design principles

A
  • Scalability : vertical & horizontal
  • Disposable resources: servers should be disposable & easily configured
  • automation : serverless, infrastructure as a service, auto scaling
  • Loose coupling
  • Services not servers:
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

architected framework 5 pillars

A
  1. Operational excellence
    - Perform operation as code
  • Annotate documentation
  • Make frequent, small, reversible changes
  • Refine operation procedures frequently
  • Anticipate failure
  • Learn from all operational failures
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

5 pillars

A
  1. Security

Design Principle

  • Implement a strong identity foundation
  • Enable traceability
  • Apply security at all layers
  • Automate security best practices
  • Protect data in transit and at rest
  • Keep people away from data
  • Prepare for security events

Implementing Security Groups, NACLs, KMS, or CloudTrail reflects which Well-Architected Framework Pillar?

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

5 pillars

A
  1. Reliability

Design Principle

  • Test recovery procedure
  • Automatically recover from failure
  • Scale horizontally to increases aggregate system availability
  • Stop guessing capacity
  • Manage change in automation
  • Testing recovery procedures, stopping guessing capacity, and managing changes in automation are design principles of Reliability. Performance Efficiency design principles include: democratize advanced technologies, go global in minutes, use serverless architecture, experiment more often, mechanical sympathy.

Testing recovery procedures, stopping guessing capacity, and managing changes in automation are design principles of Performance Efficiency.
false

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

5 pillars

A
  1. Performance efficiency

Design principles

  • Democratize advanced technologies
  • Go global in minutes
  • Use serverless architectures
  • Experiment more often
  • Mechanical sympathy

Which of the following are design principles of Performance Efficiency?
go global in minute & experiment more often

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

5 pillars

A
  1. Cost optimization

Design Principles

  • Adopt a consumption mode
  • Stop spending money on data center operations
  • Analyze and attribute expenditure
  • Use managed and application level services to reduces cost ownership

AWS Cost Explorer and AWS Trusted Advisor are services examples of which Well-Architected Framework pillar?

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

AWS well architected tool

A

Free tools review your architecture against the 5 pillars well architected framework and adopt architecture best practices

  • can provide guidance against the 5 Well-Architected pillars and architectural best practices.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

AWS right Sizing

A
  • scale up over time, start small, before cloud migration, and continuously in the cloud
  • Elastic
  • At the lowest possible cost
  • Scaling up is easy so always start small ( scale up overtime)
    It important to right size
  • Before a cloud migration
  • Continuously after the cloud onboarding process (requirements change over time)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

AWS Ecosystem - free resources

A

free resource for AWS

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

AWS ecosystem -aws support

A

Developer
- business hours email access to cloud support associate

  • general guidance < 24 business hours

system impaired < 12 business hours

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

Business

A
  • 24x7 phone, email, and chat access to cloud support engineer
  • production system impaired < 4 hours
  • production system down < 1 hours
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Enterrise

A
  • Access to a Technical account manager (TAM)
  • concierge support team (for billing and account best practices
  • business-critical system down: < 15 minutes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

AWS marketplace;

A

Digital catalog with thousands of software listing from dependent software vendors 3rd party

  • can sell yours
  • AWS marketplace goes into your AWS bills
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

AWS training:

A
APN  technology partners 
Apn consulting partners 
APN training partners 
APN competency program 
AWS navigate program

Which of the following is NOT an AWS Partner Network (APN) type?
APN service partner

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

AWS knowledge center

A

Contain the most frequent & common questions and requests

17
Q

Auto Scaling in EC2 and DynamoDB are examples of?

A

Horizontal scaling

18
Q

Which AWS service is the key to Operational Excellence?

A

Cloudformation

19
Q

Which of the following options is NOT a vertical scaling limit?

A

Better fault tolereance: his is an advantage of horizontal scaling.

vertical scaling

  • downtime
  • higher cost
  • capacity limitation