Cloud Native Introduction Flashcards

(45 cards)

1
Q

What does it mean for something to be “Cloud Native”? How does it apply?

A

Applications are designed to be scalable, resilient, and flexible

Cloud Native applies to all cloud offerings including Public, Private, and Hybrid Clouds

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

What is the CNCF? What does it stand for? What is its purpose?

A

Cloud Native Computing Foundation

Purpose is to make cloud-native computing universal and sustainable

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

Who created the Kubernetes project? Who was the original developer?

A

Google

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

In what way is Kubernetes associated with the CNCF?

A

Kubernetes was the first submission to the CNCF and was created by Google

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

What was the first-ever project submission to the CNCF?

A

Kubernetes

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

What is the significance of the Linux Foundation in relation to Cloud Native?

A

The Linux Foundation is responsible for hosting significant projects like:
- The Linux Kernel
- Kubernetes
- The CNCF

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

When was the Linux Foundation founded?

A

In the year 2000

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

What is “Cloud Native Architecture”?

A

Applications built using Cloud Native best practices to run across all Cloud Native Systems

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

What is the role of container technologies in the Cloud Native ecosystem?

A

Containers are beneficial from an application management perspective.
Containers are also a positive step towards Cloud Native.

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

How does Cloud Native differ from a legacy deployment in terms of application development?

A

Cloud Native applications:
- Are designed for high availability and fault tolerance
- Leverage the infrastructure provided by cloud service providers
- Built using infrastructure-as-code tools like Terraform for flexible and vendor-agnostic management

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

What are some example benefits from Cloud Infrastructure compared to legacy?

A

Cost savings and scalability

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

What are some questions to ask in helping determine if an application is Cloud Native?

A
  • Is the application automated in its setup and delivery?
  • Has the application been designed with resilience to protect from failure?
  • Can the application automatically scale based on workload?
  • Is the application secure by default?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the three kinds of autoscaling?

A

Reactive Autoscaling: to scale according to workload

Scheduled Autoscaling

Predictive Autoscaling: schedule with AI / Machine learning

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

What is the difference between Automatic and Automated?

A

Automatic describes anything that works independently

Automated means to make a process independent of human intervention

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

What are vertical and horizontal scaling? What are their differences?

A

Vertical scaling: increase the capacity of a single server by adding resources to it.

Horizontal scaling: adding more servers / instances
- Hardware agnostic
- Cloud Native
- Automation
- Testing

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

What is the Kubernetes Cluster Autoscaler? What is its functionality and role?

A

A tool that automatically adjusts the size of a K8s cluster when there are pods that fail to run, owing to insufficient resources OR there are nodes that have been under-utilized so pods can be placed onto other existing nodes

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

What is KEDA? What are ScaledObjects? What capability does KEDA have?

A

Kubernetes Event Driven Autoscaler: uses the ScaledObject definition to define how an application should scale and what its triggers are
- Can scale a deployment to ZERO

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

What are the differences between the Vertical Pod Autoscaler (VPA) and Horizontal Pod Autoscaler (HPA)?

A

Vertical Pod Autoscaler: scale the resource requests and limits of a pod

Horizontal Pod Autoscaler: scaled the number of replicas on an application

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

What are Serverless computing services?

A

Services managed by the computing service itself like AWS Lambda or Azure functions. This includes maintenance such as provisioning, scaling, and patching.

20
Q

What is the Serverless pattern in Cloud Native architecture? What is the rationale behind adopting it?

A

Serverless architecture is event-driven making it highly efficient and cost-effective.

AWS Lambda is an example of FaaS (Function as a Service)

21
Q

What is one of the challenges posed by Serverless solutions from a Cloud Native viewpoint?

A

Vendor lock-in due to lack of standardized APIs. Each cloud provider has its own set of APIs, features, and service integrations which can make it difficult to migrate off of them or integrate with another provider.

22
Q

What is the scaling model referred to as when using Serverless and its event-driven architecture?

A

Scale to Zero.

Serverless service can automatically scale down to zero when not in use

23
Q

What open source solutions provide Serverless functionality on top of Kubernetes?

A

Knative and OpenFaas

24
Q

What are CloudEvents? What are their significance and impact within Cloud Native ecosystems?

A

They specification provides a standardized way of describing event data across different services, platforms, and systems.
This helps ensure interoperability and consistency in how events are produced, transmitted, and consumed in cloud-native environments. (Hosted by the CNCF)

25
What does provisioned concurrency in Serverless offerings refer to?
The number of instances that can be run simultaneously
26
What is a possible disadvantage of using Serverless architecture?
May incur latency when the application is less active
27
Which feature of Serverless offerings helps monitor and control spending?
Budget thresholds
28
What is the CNCF mission?
To make cloud native computing ubiquitous
29
What is the sequence of the CNCF project maturity levels?
Sandbox > Incubated > Graduated Projects being in the SANDBOX to experiment and gain community support, move to INCUBATION as they mature and demonstrate traction, and then finally achieve GRADUATION when they are widely adopted and meet stability and security criteria
30
The "Chasm" phase in the CNCF Project Maturity levels represents the bridge to which user category?
Early Majority
31
How is conflict resolution handled in the various CNCF groups?
32
What is the meaning of the different acronyms commonly used?
33
What is the core role of the CNCF TOC?
The role of the Technical Oversight Committee (TOC) is to evaluate maturity of the CNCF projects. Should projects move between stages, etc.
34
What is the acronym SIG? What does it represent? What was the acronym changed to?
SIG stands for Special Interest Group, which represents a community-driven initiative focused on specific areas of interest within the cloud-native ecosystem. SIG was changed to TAG (Technical Advisory Group).
35
What does TAG stand for within the CNCF?
Technical Advisory Group
36
What does the CNCF Technical Oversight Committee consider to establish a project's maturity?
Demonstrating adoption, healthy rate of changes, external committers from different organizations, and implementation of the CNCF Code of Conduct
37
How is conflict resolution generally handled within CNCF governance?
Through discussion and voting?
38
What are the "TOC" and "SIG" acronyms in the context of CNCF?
TOC: Technical Oversight Committee SIG: Special Interest Group
39
What are the following as they associate with the role of SRE: - SLA - SLO - SLI
SLA (Service Level Agreement): a formal, external contract with a customer. SLO (Service Level Objectives): an internal, specific, and measurable goal set by a team to meet the promise in the SLA. SLI (Service Level Indicators): Indicators that provide an insight into the success of SLAs and SLOs
40
How does the role of SRE differ from DevOps?
SRE (Site Reliability Engineer) is focused on uptime, availability, scalability, resilience, robustness, and the ability to resolve unforeseen problems
41
What is the role of FinOps? How does it relate to financial accountability?
FinOps or Cloud Financial Management is a practice that aims to bring financial accountability to the variable spend model of the cloud, enabling distributed teams to make business trade-offs between speed, cost, and quality.
42
What is the role of the Open Container Initiative (OCI)?
To develop specifications that ensure container portability across different platforms by defining how container images are built, distributed, and executed
43
What is the difference between the OCI Image Specification, Runtime Specification, and Distribution Specification?
Image Specification: how to bundle a filesystem into an image, tools including Docker, Buildkit, Podman, and Buildah Runtime Specification: the reference implementation of an OCI compliant runtime. runC is the reference Distribution Specification: open standards and API protocols for distribution of content
44
What is the reference implementation of the OCI runtime specification?
runC Docker's underlying runtime. The Runtime Specification defines how a filesystem bundle should be executed as a container runtime environment.
45
What are the different types of Open Standards, i.e. CNI, CRI, CSI, SMI
CNI: Container Network Interface is a standard for configuring network interfaces to ensure containers can be connected to a network CRI: Container Runtime Interface allows the kubelet to use a wide variety of container runtimes CSI: Container Storage Interface is a standard specification that allows container orchestration systems to expose various block and file storage systems to containerized applications SMI: Service Mesh Interface is a standard specification for defining a common set of APIs for service meshes on Kubernetes, aiming to improve interoperability between different implementations