Question 51 · 282 in bank
Which of these is a valid container restart policy?
Show answer
Answer: D
Kubernetes and Cloud Native Associate282 questions across 29 pages are complete and free, with no account or card.
282 questions in this bank
Free access · progress saved on this device
Which of these is a valid container restart policy?
Answer: D
Which of the following characteristics is associated with container orchestration?
Answer: B
Which of the following workload require a headless service while deploying into the namespace?
Answer: A
A. StatefulSet Explanation: StatefulSets are used for applications that maintain a persistent state or have a unique identity, such as databases. Each pod in a StatefulSet typically has a unique name, and it's necessary to ensure discovery and communication between these pods consistently, even when they are scaled up or down. An analogy for StatefulSets could be managing a team of employees in an organization. Each employee has a unique name and a specific role. Even as the team grows or shrinks, it's important to maintain consistent communication among them. Therefore, you need a communication system (service) that can reliably locate each employee, regardless of changes in the team.
Source: Adapted from community discussion — phcunha
What is Helm?
Answer: B
Which API object is the recommended way to run a scalable, stateless application on your cluster?
Answer: B
ReplicaSet for statefull applications Deployment is for stateless applications DaemonSet is for application that has to be on every node. Pod is created as part of replicaset, deployment, daemonset
Source: Adapted from community discussion — Saireddybonthu
Which is the correct kubectl command to display logs in real time?
Answer: D
How to load and generate data required before the Pod startup?
Answer: A
A. Use an init container with shared file storage. Explanation: Init containers are executed before the main containers in a Pod are started. They are designed to perform initialization tasks, such as loading and generating data required before the main containers start. Init containers can share file storage with the main containers in the Pod, allowing them to perform tasks like data loading or generation and then making that data available to the main containers. An analogy for using an init container could be preparing ingredients before cooking a meal. Just as you might prepare ingredients like chopping vegetables or marinating meat before starting to cook, init containers prepare data or perform tasks necessary for the main containers to function properly before the main containers start running.
Source: Adapted from community discussion — phcunha
What is the core functionality of GitOps tools like Argo CD and Flux?
Answer: D
An analogy for this functionality could be a thermostat in a room. The desired temperature set on the thermostat represents the configuration defined in Git, while the actual temperature in the room represents the production state. If the actual temperature deviates from the desired temperature, the thermostat (GitOps tool) will automatically adjust the heating or cooling systems to bring the room temperature back to the desired level. Similarly, GitOps tools ensure that the production state of the cluster matches the desired state defined in Git.
Source: Adapted from community discussion — phcunha
Which Kubernetes resource workload ensures that all (or some) nodes run a copy of a Pod?
Answer: C
C. DaemonSet Explanation: A DaemonSet ensures that all (or some) nodes run a copy of a Pod. It's typically used for system daemons or cluster services that must run on every node. Each node in the cluster will have exactly one instance of the Pod managed by the DaemonSet. An analogy for a DaemonSet could be streetlights in a city. Just as streetlights are deployed at specific intervals along every street in a city to ensure adequate lighting, DaemonSets ensure that specific Pods are deployed on every node in a Kubernetes cluster to provide essential services or functionalities uniformly across the cluster.
Source: Adapted from community discussion — phcunha
We can extend the Kubernetes API with Kubernetes API Aggregation Layer and CRDs. What is CRD?
Answer: A
A. Custom Resource Definition Explanation: CRD stands for Custom Resource Definition. It's a Kubernetes extension mechanism that allows users to define their custom resources and their schema, effectively extending the Kubernetes API. Once defined, these custom resources can be managed and interacted with using standard Kubernetes API operations, just like built-in resources like Pods or Deployments. An analogy for CRD could be creating a new type of item in a game. In a video game, developers might introduce custom items that players can collect or use within the game world. These custom items have their unique properties and behaviors, defined by the game developers. Similarly, with CRDs, Kubernetes users can define custom resources with specific properties and behaviors tailored to their application needs.
Source: Adapted from community discussion — phcunha
Keyboard:J Kmove between questionsA–Dselect an answerRshow or hide the answer← →change page
KCNA practice, question 51. 282 questions available.
Version 1.0.0. How we source questions