




Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Linux Foundation Kubernetes and Cloud Native Associate (KCNA) rated A.pdf
Typology: Exams
1 / 8
This page cannot be seen from the preview
Don't miss anything!





CSI Container Storage Interface - correct answer ✅A standard for exposing arbitrary block and file storage systems to containerized workloads on Container Orchestration Systems (COs) like Kubernetes. PersistentVolumes (PV) - correct answer ✅An abstract description for a slice of storage. The object configuration holds information like type of volume, volume size, access mode and unique identifiers and information how to mount it. PersistentVolumeClaims (PVC) - correct answer ✅A request for storage by a user. Allows the user to reserve a persistent volume in cases where multiple volumes exist. Cloud Native Computing Foundation (CNCF) - correct answer ✅An open source software foundation under the Linux Foundation umbrella dedicated to making cloud native computing universal and sustainable. This organization serves as a vendor-neutral home for many of the fastest-growing projects on GitHub, including Kubernetes, Prometheus, and Envoy, fostering collaboration between the industry's top developers, end users and vendors. Cloud Native Characteristics - correct answer ✅A architecture model characterized by
OCI - correct answer ✅A Linux Foundation project, started in June 2015 by Docker, to design open standards for operating-system-level virtualization, most importantly Linux containers. 4 Cs of Cloud Native Security - correct answer ✅Code, Container, Cluster, Cloud Architecture of Container Orchestration - correct answer ✅Most container orchestration systems consist of two parts: a control plane that is responsible for the management of the containers and worker nodes that actually host the containers. Container Network Interface (CNI) - correct answer ✅A standard that can be used to write or configure network plugins and makes it very easy to swap out different plugins in various container orchestration platforms. Control plane node(s) - correct answer ✅The brains of the K8s operation. Nodes that contain various components which manage the cluster and control various tasks like deployment, scheduling and self-healing of containerized workloads. Worker nodes - correct answer ✅The type of node on which applications run in your cluster. Their behavior, like if they should start a container, is completely controlled by the control plane node. kube-apiserver - correct answer ✅The centerpiece API of Kubernetes. All other components interact with this API and this is where users would access the cluster.
kube-proxy - correct answer ✅A network proxy that handles inside and outside communication of your cluster. Instead of managing traffic flow on it's own, this process tries to rely on the networking capabilities of the underlying operating system if possible. kubectl - correct answer ✅K8s CLI Pod - correct answer ✅A unit of one or more containers that share an isolation layer of namespaces and cgroups. It is the smallest deployable unit in Kubernetes, which also means that Kubernetes is not interacting with containers directly. K8s Object: ReplicaSet - correct answer ✅A controller object that ensures a desired number of pods is running at any given time. This object can be used to scale out applications and improve their availability. They do this by starting multiple copies of a pod definition. K8s Object: Deployment - correct answer ✅The most feature-rich object in Kubernetes.This object can be used to describe the complete application lifecycle, they do this by managing multiple ReplicaSets that get updated when the application is changed by providing a new container image, for example. Instances of this object are perfect to run stateless applications in Kubernetes. K8s Object: StatefulSet - correct answer ✅Considered a bad practice for a long time, instances of this object can be used to run stateful applications like databases on Kubernetes. Stateful applications have special requirements that don't fit the ephemeral nature of pods and containers. In contrast to Deployments, this object tries to retain IP addresses of pods and gives them a stable name, persistent storage and more graceful handling of scaling and updates.
K8s Object: DaemonSet - correct answer ✅Ensures that a copy of a Pod runs on all (or some) nodes of your cluster. This object is perfect to run infrastructure- related workloads, for example monitoring or logging tools. K8s Object: Job - correct answer ✅Creates one or more Pods that execute a task and terminate afterwards. These objects are perfect to run one-shot scripts like database migrations or administrative tasks. K8s Object: CronJob - correct answer ✅These objects add a time-based configuration to jobs. This allows running Jobs periodically, for example doing a backup job every night at 4am. ClusterIP - correct answer ✅The most common service type. This service is a virtual IP inside Kubernetes that can be used as a single endpoint for a set of pods. This service type can be used as a round-robin load balancer. NodePort - correct answer ✅This service type extends the ClusterIP by adding simple routing rules. It opens a port (default between 30000-32767) on every node in the cluster and maps it to the ClusterIP. This service type allows routing external traffic to the cluster. LoadBalancer - correct answer ✅This service type extends the NodePort by deploying an external instance that spreads traffic across multiple objects. This will only work if you're in an environment that has an API to configure an instance, like GCP, AWS, Azure or even OpenStack.
Vertical Pod Autoscaler - correct answer ✅This autoscaler type is relatively new and allows Pods to increase the resource requests and limits dynamically. This autoscaler's abilities is limited by the node capacity. Git - correct answer ✅an open-source distributed version control system Infrastructure as code (iac) - correct answer ✅A provisioning architecture in which deployment of resources is performed by scripted automation and orchestration. GitOps - correct answer ✅Integrates the provisioning and change process of infrastructure with version control operations. Push-based gitops - correct answer ✅The version of gitops that kicks off when the pipeline is started. The pipeline is started and runs tools that make the changes in the platform. Changes can be triggered by a commit or merge request. Pull-based gitops - correct answer ✅The version of gitops where an agent watches the git repository for changes and compares the definition in the repository with the actual running state. If changes are detected, the agent applies the changes to the infrastructure. Logs - correct answer ✅These are messages that are emitted from an application when errors, warnings or debug information should be presented. A simple log entry could be the start and end of a specific task that the application performed.
Metrics - correct answer ✅Metrics are quantitative measurements taken over time. This could be the number of requests or an error rate. Traces - correct answer ✅They track the progression of a request while it's passing through the system. Traces are used in a distributed system that can provide information about when a request was processed by a service and how long it took. Flux - correct answer ✅CNCF graduated project. Provides a set of continuous and progressive delivery solutions for K8s. Developed by Weaveworks. Argo CD - correct answer ✅CNCF graduated project. A declarative GitOps tool for K8s. Developed in party by Intuit. Rook - correct answer ✅CNCF graduated project. Provides cloud native storage orchestration. Integrates with Ceph. Used to operate storage clusters directly in Kubernetes. KEDA - correct answer ✅Autoscaler project created by Microsoft and Red Hat. Allows for auto scaling in response to events rather than metrics. Also, allows auto scaling of non-standard Kubernetes objects (like jobs)