AWS Cloud Developer: FullStack -Basics

Question 1

Compute

Answer 1

Any computer operation requires some computation on a CPU (central processing unit).

Question 2

Server

Answer 2

A specialized computer for cloud and web services.

Question 3

Instance

Answer 3

A computational unit which may be a physical server or a virtual server that is abstracted by a cloud service.

Question 4

Cluster

Answer 4

A collection of instances which perform the same function. It may be used to distribute workloads.

Question 5

Autoscaling Group

Answer 5

A type of cluster that can increase or decrease the number of instances based on demand.

Question 6

Technical Debt

Answer 6

The cost (in time and resources) of additional code rework caused by choosing an easy solution now instead of using a better approach that would take longer to implement.

Question 7

Microservices

Answer 7

Microservices are individual specialized systems (software deployed on specialized infrastructure) designed to accomplish a specific task. Specific tasks may include things like authentication, image processing, or data management.

Question 8

tightly coupled system

Answer 8

A system where all the subsystems and processes are tightly knit together and dependent on one another

They are quick to set up but might increase technical debt

Loosely-coupled systems might take longer to setup up but they are easier to improve upon later

Question 9

Quick and easy ways to decouple early on

Answer 9

1. Separate database and file system from the server
2. Break application down into individual responsibilities which can be run as microservices (doing so allows you to run each service on a separate server that has been equipped with the specific hardware to support that microservice -like having a graphic GPU on the server that processes image data)

Question 10

5 major categories of HTTP status codes

Answer 10

100 Informational
200 Success
300 Redirection
400 Client Error
500 Server Error

Question 11

Anatomy of an URL address

Answer 11

protocol //subdomain.domainName:port/path?query=parameters#fragment