Cloud Architecture Terms

Question 1

Solutions Architect

Answer 1

A role in a technical organization that architects a technical solution using multiple systems via researching, documentation, experimentation.

Question 2

Solutions Architect needs to answer these questions

Answer 2

1. How secure is this solution? (Security)
2. How much is this going to cost? (Cost)

Question 3

Cloud Architect

Answer 3

A solutions architect that is focused solely on architecting technical solutions using Cloud services.

Question 4

A Cloud Architect needs to understand the following

Answer 4

Availability, Scalability, Elasticity, Fault Tolerance, Disaster Recovery

Question 5

High Availability

Answer 5

Your ability for your service to remain available by ensuring there is no single point of failure (have backups or a plan) and/or ensure a certain level of performance (quality).

Question 6

Elastic Load Balancer

Answer 6

Allows you to evenly distribute traffic to multiple servers in one or more datacenters. If a datacenter or server becomes unavailable (unhealthy) the load balancer will route the traffic to only available datacenters within servers. Based on the demand of traffic.

Question 7

High Scalability

Answer 7

Ability to increase your capacity based on the increasing demand of traffic, memory, and computing power. Vertical Scale: Scale Up to upgrade to a bigger server. Horizontal Scale: Scale Out which adds more servers of the same size.

Question 8

High Elasticity

Answer 8

The ability to automatically increase/decrease your capacity based on the current demand of traffic, memory, and computing power.

Question 9

Horizontal Scaling

Answer 9

Scaling Out: Add more of the same size servers
Scaling In: Remove the underutilized same size servers

Question 10

Vertical Scaling

Answer 10

Scaling Up: to upgrade to a bigger server.
Scaling Down: generally hard for traditional architecture so you will see more of horizontal scaling.

Question 11

ASG - Auto Scaling Groups

Answer 11

An AWS feature that will automatically add/remove servers based on the scaling rules set by you.

Question 12

High Fault Tolerance

Answer 12

The ability to ensure there is no single point of failure. Preventing the chance of failure.

Question 13

Fail-Overs

Answer 13

Is when you have a plan to shift traffic to a redundant system in case the primary system fails. So the traffic would go to the secondary/backup system.

Question 14

RDS Multi-AZ

Answer 14

When you run a duplicate standby database in another AZ in case your primary database fails.

Question 15

Highly Durable

Answer 15

Ability to recover from a disaster and prevent the loss of data.

Question 16

Disaster Recovery

Answer 16

Solutions that help recover from a disaster.

Question 17

Cloud Endure DR:

Answer 17

Continuously replicates your machine into a low-cost staging area in your target AWS account and preferred Region enabling fast and reliable recovery in case of IT data center failures.

Question 18

BCP - Business Continuity Plan

Answer 18

A document that outlines how a business will continue operating during an unplanned disruption in services.

Question 19

RPO - Recovery Point Objective

Answer 19

The max acceptable amount of data loss after an unplanned data-loss incident, expressed as an amount of time. How much data are you willing to lose?

Question 20

RTO - Recovery Time Objective

Answer 20

The max acceptable amount of downtime you business can tolerate without incurring a significant financial loss. How much time are you willing to go down?

Question 21

Disaster Recovery Options

Answer 21

It is based on Cost vs Time.
- Backup & Restore
- Pilot Light
- Warm Standing
- Multi-Site Active/Active

Question 22

Backup & Restore

Answer 22

You backup data and restore to a new infrastructure.
- lower priority
- cost effective $
- restore data after event
- deploy resources after event
- RPO/RTO Hours

Question 23

Pilot Light

Answer 23

Your data is replicated to another region with minimal services running.
- less stringent RPO/RTO
- core services
- start & scale resources after event
- more costly $$
- RPO/RTO 10 minutes

Question 24

Warm Standing

Answer 24

Scaled down copy of your infrastructure running ready to scale up
- business critical services
- scale resources after event
- even more costly $$$
- RPO/RTO minutes

Question 25

Multi-Site Active/ Active

Answer 25

Scaled up copy of your infrastructure architecture in another region.
- zero down time
- near zero loss
- mission critical services
- highhh cost $$$$
- RPO/RTO real time