DO180 Red Hat OpenShift Administration I: Operating a Production Cluster Quiz Questions and Answers
Answer :
Services
Explanation :
Services in Kubernetes provide a stable endpoint to access a set of pods, using labels to identify the pods. They facilitate load balancing of network traffic across these pods, helping to ensure high availability.
To segregate resource allocation and provide isolation
Explanation :
Namespaces offer resource allocation and isolation, crucial in a multi-team environment. This ensures team-specific configurations manage resources and workload independently, minimizing conflicts and overload.
A Horizontal Pod Autoscaler automatically adjusts the number of pods in a Kubernetes deployment based on observed metrics, such as CPU or memory usage, to ensure the application can handle demand efficiently.
To guarantee data consistency, performance, and cost-effectiveness.
Explanation :
Understanding storage class parameters helps administrators ensure that the storage supports the application's data consistency needs, meets performance requirements, and stays within budgetary constraints.
Use ConfigMaps and Secrets, separating common configurations from environment-specific ones
Explanation :
Using ConfigMaps and Secrets to isolate environment-specific configurations reduces complexity and enhances management and security across various environments such as development, staging, and production.
Maintain a sufficient number of old pods while new pods are created
Explanation :
By maintaining a sufficient number of old pods during rolling updates, Kubernetes ensures that there is no downtime, thus maintaining application availability while new pods are incrementally created.
It dictates how storage resources are provisioned and managed.
Explanation :
A storage class provides a way to describe different types of storage that can be requested dynamically, influencing how storage resources are automatically provisioned and managed for applications.
Kubernetes CPU allocation uses millicores (m), where 1000m equals 1 CPU. The total CPU requirement is 200m + 500m + 300m = 1000m, equivalent to 1 CPU, but the total depiction of the sum is 1200m.
To automatically replace unhealthy pods to ensure service continuity
Explanation :
Health checks in Kubernetes are pivotal for identifying and automatically replacing unhealthy pods, thereby ensuring continuous service availability and reliability without manual intervention.
Long-lived applications require StatefulSets; short-lived applications use Jobs.
Explanation :
Long-lived applications often need persistence and scaling, which StatefulSets provide. Short-lived applications usually perform tasks and exit, which aligns with Jobs managed by Kubernetes.
