Section 1 AWS and SA Fundamentals

Question 1

Principle

Answer 1

A Person or App that ccan make Authenticated or Anonymous Requests

Question 2

Authentication

Answer 2

Authenticating a Principle against an Identity

Question 3

Identity

Answer 3

Objects that require authentication and are authorized to access resources

Question 4

Authorization

Answer 4

The process of checking and allowing or denying access toa resource for an identity

Question 5

Shared Resposibility Model - Customer

Answer 5

• Customer Data
• Platform
• Applications
• Identity & Access Managment
• OS
• Network & Firewall Configuration
• Encryption
• Network Protection

Question 6

Shared Resposibility Model - AWS

Answer 6

• Software
• Compute
• Storage
• Databse
• Networking
• Hardware
• Regions
• Availibility Zones (AZ)
• Edge Locations

Question 7

Service Model

Answer 7

Defines how a service or product is delivered, how you pay, and what you receive

Question 8

Stack

Answer 8

• Data Center
• Network Storage
• Hosts / Servers
• Virtulization
• Operating System (OS)
• Runtme
• Application
• Data

Question 9

3 types of Service Models

Answer 9

• Infrastructure as a Service (IaaS)
• Platform as a Service (PaaS)
• Software as a Service (SaaS)

Question 10

Infrastructure as a Service (IaaS)

AWS Resposibility

Answer 10

• Data Center
• Network & Storage
• Virtulization

Question 11

Infrastructure as a Service (IaaS)

Client Resposibility

Answer 11

• Operating System (OS)
• Runtime
• Application
• Data

Question 12

Platform as a Service (PaaS)

AWS Resposibility

Answer 12

• Data Center
• Network & Storage
• Virtulization
• Runtime

Question 13

Platform as a Service (PaaS)

Client Resposibility

Answer 13

• Application

- Data

Question 14

Software as a Service (Saas)

AWS Responsibility

Answer 14

• Data Center
• Network & Storage
• Virtulization
• Host / Servers
• Application

Question 15

Software as a Service (Saas)

Client Responsibility

Answer 15

• Data

Question 16

High Availability (HA)

Answer 16

Hardware, Software, and Configuration allowing system to recover quickly in the event of a failure with some User impact

Question 17

Fault Tolerant

Answer 17

System Designed to operate through a failure with no User Impact

Question 18

Recovery Point Objective (RPO)

Answer 18

Max time between a failure and the last successful backup

Question 19

Recovery Time Objective (RTO)

Answer 19

Max amount of time a system is down and recovers

Question 20

Vertical Scaling

Answer 20

Adding additional CPU or Memory

Question 21

Horizontal Scaling

Answer 21

Adding Additional machines into a resource pool

Question 22

3 tiers of Application Design

Answer 22

• Presentation
• Logic
• Data

Question 23

Presentation Application Tier

Answer 23

Interacts with consumer of the App

Question 24

Logic Application Tier

Answer 24

Delivers the App’s functionallity

Question 25

Data Application Tier

Answer 25

Controls interaction with database

Question 26

Monolithic Application

Answer 26

Hard to Scale and has to be sone Vertically

Question 27

Encryption

Answer 27

Process of taking Plaintext and converting it into Ciphertext and vise versa

Question 28

Synnetrical Encryption

Answer 28

Same key is used for encryption and decryption

Question 29

Asymetrical Encryption

Answer 29

Public Key & Private Key

Question 30

Encryption At Rest

Answer 30

Encrypting a file that is stored

Question 31

Encryption In Transit

Answer 31

Encrypting the communication between 2 entities

Question 32

Region

Answer 32

Contains multiple Avalibility Zones (AZs)\

Question 33

Avalibility Zone (AZ)

Answer 33

Seperate and isolated networks

Question 34

Edge Location

Answer 34

Small pocket of AWS compute, storage, and networking close to a major population

Question 35

Well Architected Framework

Answer 35

- Secure - Reliable - Performance Efficiency - Operational Excellence - Cost Optimization

Question 36

Well Architected Framework | Security Design Principle

Answer 36

- Strong Identity Foundation - Enable traceability - Security to all layers - Automated Security - Protect Data In Transit & At Rest - Prepare for Security events

Question 37

Well Architected Framework | Reliability Design Princple

Answer 37

- Test recovery Procedures - Automatically recovery from failure - Scale Horizontally - Stop guessing capacity - Manage Change in Automation

Question 38

Well Architected Framework | Performance Design Princple

Answer 38

- Democratize Advanced Tech - Go Global in Minutes - Use Serverless Architecture - Experiment More Often - Mechanically Sympathy

Question 39

Well Architected Framework | Operation Excellence Design Princple

Answer 39

- Perform Operations as Code - Annotate Documentation - Make Frewuent, Small, Revisable Changes - Refine Operation Procedures Frequently - Anticipate Failure - Learn from All Operational Failures

Question 40

Well Architected Framework | Cost Optimization Design Princple

Answer 40

- Adopt a Consumption Model - Measure Overall Efficiency - Stop Spending Money on Data Center Operations - Analyze & Attribute Expenditures - Use Managed Services to Reduce Cost of Ownership

Question 41

Elastic Scaling

Answer 41

Automation and Horizontal Scaling Used to Match capacity with Demand

Question 42

Simple Storage Service (S3)

Answer 42

Global Object Storage that can be used to store objects

Question 43

S3 Region

Answer 43

Holds Buckets

Question 44

S3 Buckets

Answer 44

Holds Objects

Question 45

Objects

Answer 45

- Similar to Files | - 0 to 5 TB

Question 46

CloudFormation

Answer 46

Infrastructure as Code (IaC) Product

Question 47

CloudFormation can Creat, Manage, and Remove Infrastructure using?

Answer 47

- JSON | - YAMIL