Cloud Native Architecture

Question 1

vertical scaling

Answer 1

same number of servers but stronger

Question 2

horizontal scaling

Answer 2

servers with same hardware but more of them

Question 3

Characteristics of cloud native architecture

Answer 3

Self-healing
Scalable
High level of automation
(Cost-) Efficient
Easy to maintain
Secure by default

Question 4

What’s a 12 factor app?

Answer 4

A guideline for developing cloud native applications.

Question 5

Benefits of autoscaling

Answer 5

Cost-effectiveness, we use only as much compute power as we need.

Question 6

Benefits of serverless

Answer 6

Relieves developers of complicated devOps tasks.
Very fast deployments.
Precise billing.

Question 7

Based on what serverless functions are scaled?

Answer 7

Incoming events

Question 8

Is there an industry standard for serverless?

Answer 8

There is an initiative to standardise events. It’s called CloudEvents. Still in development.

Question 9

What CloudEvents is trying to achieve

Answer 9

Standardise how data is described in events

Question 10

Are servers required to run serverless function?

Answer 10

Yes, serverless runs on servers but you don’t have to touch it.

Question 11

What defines how to build and package container images

Answer 11

Open Container Initiative(OCI) image-spec

Question 12

What specifies the configuration, execution environment and lifecycle of containers

Answer 12

Open Container Initiative(OCI) runtime-spec

Question 13

What provides a standard for the distribution of content in general and container images in particular

Answer 13

Open Container Initiative(OCI) distribution-spec

Question 14

What’s in the OCI Spec

Answer 14

image-spec
runtime-spec
distribution-spec

Question 15

Metrics SRE uses

Answer 15

Service Level Objectives (SLO)
Service Level Indicators (SLI)
Service Level Agreements (SLA)

Question 16

Service Level Objectives(SLO)

Answer 16

“Specify a target level for the reliability of your service.” - A goal that is set, for example reaching a service latency of less that 100ms.

Question 17

Service Level Indicators (SLI)

Answer 17

A carefully defined quantitative measure of some aspect of the level of service that is provided” - For example how long a request actually needs to be answered.

Question 18

Service Level Agreements (SLA)

Answer 18

“An explicit or implicit contract with your users that includes consequences of meeting (or missing) the SLOs they contain. The consequences are most easily recognized when they are financial – a rebate or a penalty – but they can take other forms.” - Answers the question what happens if SLOs are not met.

Question 19

What’s an error budget?

Answer 19

defines the amount (or time) of errors your application can have, before actions are taken, like stopping deployments to production.

Question 20

Cloud Architect job

Answer 20

Adopting cloud technologies, designing application landscape and infrastructure, with a focus on security, scalability and deployment mechanisms.

Question 21

DevOps Engineer

Answer 21

combination of developer and administrator.

Question 22

DevSecOps Engineer

Answer 22

build bridges between between more traditional development and security teams

Question 23

Data Engineer

Answer 23

collect, store, analyse data

Question 24

Full-stack Developer

Answer 24

Front+Back+Basics of DevOps

Question 25

Site Reliability Engineer

Answer 25

create and maintain software that is reliable and scalable, uses software engineering approaches to solve operational problems and automate operation tasks

Question 26

Cloud native roles

Answer 26

Cloud Architect
Security Engineer
DevOps Engineer
DevSecOps Engineer
Data Engineer
Full-stack Developer
Site Reliability Engineer

Question 27

CNCF project stages

Answer 27

sandbox
incubation
graduate