Kubernetes and Cloud Native Associate practice questions

Try 25 supported questions from the 138-question bank. Check each answer when you are ready and keep this preview’s progress privately in your browser.

Back to the KCNA exam guide Switch to a timed mock

Free preview

25 of 138 questions are open

This sample includes answers, available explanations, official references and curated community discussion. An Exam Pass unlocks the private complete bank for this exam.

See Exam Pass pricing

Answer support

What is available on this page

5 contested answers

Questions: 25
Explanations: 25
Candidate context: 25
Question citations: 15

25 questions in this bank

Question 1 of 25
How many different Kubernetes service types can you define?
Show answer
Correct answer: C
How others answered
C80%
D20%
Explanation
The correct answer is: C. 4 Explanation: Kubernetes supports four different service types: ClusterIP: The default service type, which exposes the service on a cluster-internal IP. It is accessible only within the cluster. NodePort: Exposes the service on each node's IP at a static port. This makes the service accessible outside the cluster via : . LoadBalancer: Exposes the service externally using a cloud provider's load balancer. This service type automatically provisions a load balancer for the service. ExternalName: Maps the service to a DNS name by returning a CNAME record, redirecting traffic to an external service outside the Kubernetes cluster. These are the four primary service types in Kubernetes.
Adapted from community discussion by miskill · 2024-09-23 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 1 Report an issue
Candidate context
Question 1 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
M
miskill
2024-09-23
Selected C3 upvotes
The correct answer is: C. 4 Explanation: Kubernetes supports four different service types: ClusterIP: The default service type, which exposes the service on a cluster-internal IP. It is accessible only within the cluster. NodePort: Exposes the service on each node's IP at a static port. This makes the service accessible outside the cluster via : . LoadBalancer: Exposes the service externally using a cloud provider's load balancer. This service type automatically provisions a load balancer for the service. ExternalName: Maps the service to a DNS name by returning a CNAME record, redirecting traffic to an external service outside the Kubernetes cluster. These are the four primary service types in Kubernetes.
J
jafg22
2024-09-14
2 upvotes
The correct answer its C ClusterIP: The default type, exposes the Service on a cluster-internal IP. NodePort: Exposes the Service on each Node’s IP at a static port. LoadBalancer: Exposes the Service externally using a cloud provider's load balancer. ExternalName: Maps a Service to an external DNS name.
S
shahy0
2025-03-01
Selected C1 upvote
Kubernetes supports four different Service types: ClusterIP, NodePort, LoadBalancer, and ExternalName. Each Service type serves a specific purpose and use case, allowing you to expose applications running in Pods to other applications or users, both inside and outside the cluster.
D
Darkren4eveR
2024-09-12
1 upvote
c https://kubernetes.io/docs/concepts/services-networking/service/
Question 2 of 25
Which component of the node is responsible to run workloads?
Show answer
Correct answer: D
How others answered
D55%
A45%
Only 55% agreed on this answer — treat it as contested rather than settled.
Explanation
The component of the node responsible for running workloads is the kubelet. While the container runtime (like Docker, containerd, or CRI-O) is crucial for actually running the containers, the kubelet is the orchestrator that ensures the containers are running as specified by the Kubernetes control plane.
Adapted from community discussion by mc2301 · 2024-10-02 · 5 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 2 Report an issue
Candidate context
Question 2 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
M
mc2301
2024-10-02
5 upvotes
The component of the node responsible for running workloads is the kubelet. While the container runtime (like Docker, containerd, or CRI-O) is crucial for actually running the containers, the kubelet is the orchestrator that ensures the containers are running as specified by the Kubernetes control plane.
4
4532da9
2024-09-15
Selected D3 upvotes
The container runtime is responsible for running the containers that make up the workloads on the node. The kubelet interacts with the container runtime to start, stop, and manage containers, but it is the container runtime itself that actually runs the workloads.
Y
yoyo2424
2025-01-20
Selected D1 upvote
are D....The container runtime is responsible for running the workloads (containers) on a node in Kubernetes. It pulls container images from a registry and manages the lifecycle of containers. Examples of container runtimes include Docker, containerd, and CRI-O.
2
2211094
2025-01-15
Selected D1 upvote
Kubelet manage entire life cycle of the containers, while container runtime manages the runtime of the workload. So the answer is D
Question 3 of 25
Which of the following workload require a headless service while deploying into the namespace?
Show answer
Correct answer: A
How others answered
A100%
Explanation
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.
Adapted from community discussion by phcunha · 2024-09-22 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 3 Report an issue
Candidate context
Question 3 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
P
phcunha
2024-09-22
3 upvotes
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.
D
dadaarce
2024-09-26
Selected A2 upvotes
Headless services are not typically required for the other workload types listed: CronJob: Executes Jobs at a scheduled time, but doesn't necessarily require a headless service. Deployment: Manages stateless applications and can use a standard service for load balancing. DaemonSet: Ensures that a copy of a pod runs on each node in the cluster, but doesn't require a headless service for normal operation.
P
pulsefire
2024-09-06
2 upvotes
A. https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#:~:text=StatefulSets%20currently%20require%20a%20Headless%20Service%20to%20be%20responsible%20for%20the%20network%20identity%20of%20the%20Pods.%20You%20are%20responsible%20for%20creating%20this%20Service.
S
shahy0
2025-02-28
Selected A1 upvote
A headless service is typically used in Kubernetes for workloads that require direct access to individual pods without load balancing.
Question 4 of 25
What is the core functionality of GitOps tools like Argo CD and Flux?
Show answer
Correct answer: D
How others answered
D100%
Explanation
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.
Adapted from community discussion by phcunha · 2024-09-22 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 4 Report an issue
Candidate context
Question 4 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
P
phcunha
2024-09-22
3 upvotes
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.
P
phcunha
2024-09-22
2 upvotes
D. They continuously compare the desired state in Git with the actual production state and notify or act upon differences. Explanation: GitOps tools like Argo CD and Flux are designed to manage Kubernetes clusters by using Git repositories as the source of truth for cluster configuration. The core functionality of these tools involves continuously comparing the desired state of the cluster, as defined in Git, with the actual state of the cluster running in production. If there are differences between the desired and actual states, these tools will automatically reconcile those differences by either updating the production state to match the desired state or notifying operators of any discrepancies.
S
shahy0
2025-02-28
Selected D1 upvote
The core functionality of GitOps tools like Argo CD and Flux is to enable continuous delivery and deployment of applications to Kubernetes clusters using Git as the single source of truth. These tools automate the process of synchronizing the desired state of the Kubernetes cluster, as defined in Git repositories, with the actual state of the cluster
Question 5 of 25
Which Kubernetes resource workload ensures that all (or some) nodes run a copy of a Pod?
Show answer
Correct answer: C
How others answered
C100%
Explanation
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.
Adapted from community discussion by phcunha · 2024-09-22 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 5 Report an issue
Candidate context
Question 5 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
P
phcunha
2024-09-22
3 upvotes
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.
P
phcunha
2024-09-22
1 upvote
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.
S
shahy0
2025-02-28
Selected C1 upvote
A DaemonSet ensures that a copy of a Pod runs on all (or some) nodes in the Kubernetes cluster.
Question 6 of 25
The Kubernetes project work is carried primarily by SIGs. What does SIG stand for?
Show answer
Correct answer: A
How others answered
A100%
Explanation
A. Special Interest Group Explanation: SIG stands for Special Interest Group. In the context of Kubernetes, SIGs are groups of contributors focused on specific areas or domains within the project. Each SIG is responsible for overseeing and contributing to the development, maintenance, and improvement of its designated area, such as networking, storage, scalability, or documentation. An analogy for SIGs could be departments within an organization. In a company, different departments (such as marketing, sales, or engineering) focus on specific areas of expertise and collaborate to achieve common goals. Similarly, SIGs in Kubernetes focus on specific aspects of the project and work together to advance the development and functionality of those areas.
Adapted from community discussion by phcunha · 2024-09-22 · 4 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
cncf.io documentation
Permanent link to question 6 Report an issue
Candidate context
Question 6 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
P
phcunha
2024-09-22
4 upvotes
A. Special Interest Group Explanation: SIG stands for Special Interest Group. In the context of Kubernetes, SIGs are groups of contributors focused on specific areas or domains within the project. Each SIG is responsible for overseeing and contributing to the development, maintenance, and improvement of its designated area, such as networking, storage, scalability, or documentation. An analogy for SIGs could be departments within an organization. In a company, different departments (such as marketing, sales, or engineering) focus on specific areas of expertise and collaborate to achieve common goals. Similarly, SIGs in Kubernetes focus on specific aspects of the project and work together to advance the development and functionality of those areas.
E
EzBL
2024-09-16
Selected A2 upvotes
In the Kubernetes project, SIG stands for Special Interest Group. SIGs are responsible for focused areas of the project and coordinate efforts related to those areas. Each SIG has its own scope, responsibilities, and channels for communication, and they play a crucial role in the development, maintenance, and evolution of Kubernetes. Examples of SIGs include SIG-CLI, SIG-Storage, SIG-Network, etc.
A
aouihw
2024-03-04
Selected A2 upvotes
Correct https://www.cncf.io/announcements/2019/09/12/cloud-native-computing-foundation-announces-application-delivery-sig/
S
shahy0
2025-02-28
Selected A1 upvote
SIG stands for Special Interest Group. SIGs are responsible for specific areas of the Kubernetes project. They focus on particular aspects of the project, such as networking, storage, or security.
Question 7 of 25
Which statement about Ingress is correct?
Show answer
Correct answer: D
How others answered
D100%
Explanation
D. Ingress exposes routes from outside the cluster to services in the cluster. Explanation: Ingress in Kubernetes is an API object that manages external access to services within a cluster. It provides HTTP and HTTPS routing to services based on incoming requests' hostnames, paths, or other criteria. Ingress exposes routes from outside the cluster to services inside the cluster, acting as an entry point for external traffic to reach services. An analogy for Ingress could be a building's main entrance gate. Just as a main entrance gate controls access to different sections or floors within a building, Ingress controls access to different services within a Kubernetes cluster based on defined routing rules.
Adapted from community discussion by phcunha · 2024-09-22 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 7 Report an issue
Candidate context
Question 7 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
P
phcunha
2024-09-22
2 upvotes
D. Ingress exposes routes from outside the cluster to services in the cluster. Explanation: Ingress in Kubernetes is an API object that manages external access to services within a cluster. It provides HTTP and HTTPS routing to services based on incoming requests' hostnames, paths, or other criteria. Ingress exposes routes from outside the cluster to services inside the cluster, acting as an entry point for external traffic to reach services. An analogy for Ingress could be a building's main entrance gate. Just as a main entrance gate controls access to different sections or floors within a building, Ingress controls access to different services within a Kubernetes cluster based on defined routing rules.
A
AbhishekJoshi
2024-06-17
Selected D3 upvotes
https://kubernetes.io/docs/concepts/services-networking/ingress/#:~:text=Ingress%20exposes%20HTTP%20and%20HTTPS,defined%20on%20the%20Ingress%20resource.&text=An%20Ingress%20may%20be%20configured,offer%20name%2Dbased%20virtual%20hosting.
S
shahy0
2025-02-28
Selected D1 upvote
In Kubernetes, an Ingress is an API object that manages external access to services within a cluster, typically HTTP and HTTPS. It provides a way to define rules for routing traffic from outside the cluster to the appropriate services inside the cluster.
Question 8 of 25
What components are common in a service mesh?
Show answer
Correct answer: D
How others answered
D100%
Explanation
In a service mesh architecture, service proxies (such as Envoy, Linkerd proxy, or Istio sidecar) are deployed alongside each service instance to handle communication between services. The control plane consists of various components responsible for configuring, managing, and monitoring the behavior of the service proxies, including features like traffic routing, load balancing, encryption, authentication, and observability. Together, these components enable advanced traffic management, security, and observability capabilities in a distributed microservices environment.
Adapted from community discussion by EzBL · 2024-09-19 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 8 Report an issue
Candidate context
Question 8 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
E
EzBL
2024-09-19
Selected D2 upvotes
In a service mesh architecture, service proxies (such as Envoy, Linkerd proxy, or Istio sidecar) are deployed alongside each service instance to handle communication between services. The control plane consists of various components responsible for configuring, managing, and monitoring the behavior of the service proxies, including features like traffic routing, load balancing, encryption, authentication, and observability. Together, these components enable advanced traffic management, security, and observability capabilities in a distributed microservices environment.
P
PinkAndBlack
2024-06-15
3 upvotes
I can confirn that D is the corrct answer, anyway the question is a bit tricky, because the data plan can be considered as the set of service proxies so even the C answer could be considered
S
shahy0
2025-02-28
Selected D1 upvote
A service mesh typically includes the following common components: Data Plane: Sidecar proxies for traffic management. Control Plane: Configuration management, service discovery, policy management, and telemetry. Security: mTLS, authentication, and authorization. Traffic Management: Routing, load balancing, retries, and timeouts.
Question 9 of 25
What are the initial namespaces that Kubernetes starts with?
Show answer
Correct answer: A
How others answered
A100%
Explanation
B. default, system, kube-public Incorrect. The namespace "system" is not a standard namespace in Kubernetes. C. kube-default, kube-system, kube-main, kube-node-lease Incorrect. The namespaces "kube-default" and "kube-main" are not standard namespaces in Kubernetes. D. kube-default, system, kube-main, kube-primary Incorrect. The namespaces "kube-default", "system", "kube-main", and "kube-primary" are not standard namespaces in Kubernetes.
Adapted from community discussion by shahy0 · 2025-02-28 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 9 Report an issue
Candidate context
Question 9 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
S
shahy0
2025-02-28
Selected A2 upvotes
B. default, system, kube-public Incorrect. The namespace "system" is not a standard namespace in Kubernetes. C. kube-default, kube-system, kube-main, kube-node-lease Incorrect. The namespaces "kube-default" and "kube-main" are not standard namespaces in Kubernetes. D. kube-default, system, kube-main, kube-primary Incorrect. The namespaces "kube-default", "system", "kube-main", and "kube-primary" are not standard namespaces in Kubernetes.
E
Error_2k
2024-07-28
2 upvotes
correct: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
Question 10 of 25
What is a probe within Kubernetes?
Show answer
Correct answer: C
How others answered
C100%
Explanation
Within Kubernetes, a "probe" refers to a diagnostic mechanism used by the kubelet to check the health of containers running within pods.Probes are configured within the PodSpec of Kubernetes pods and are used to determine if the containers within the pod are healthy and ready to serve traffic. There are three types of probes: Liveness Probe: Determines if the container is still running and healthy. If the liveness probe fails, Kubernetes restarts the container. Readiness Probe: Determines if the container is ready to serve traffic. If the readiness probe fails, the pod is removed from load balancers, and no traffic is routed to it. Startup Probe: Similar to the liveness probe, but only runs during the initial startup of a container. It helps delay the liveness and readiness probes until the application inside the container has started.
Adapted from community discussion by SeaH0rse66 · 2024-11-17 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 10 Report an issue
Candidate context
Question 10 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
S
SeaH0rse66
2024-11-17
Selected C3 upvotes
Within Kubernetes, a "probe" refers to a diagnostic mechanism used by the kubelet to check the health of containers running within pods.Probes are configured within the PodSpec of Kubernetes pods and are used to determine if the containers within the pod are healthy and ready to serve traffic. There are three types of probes: Liveness Probe: Determines if the container is still running and healthy. If the liveness probe fails, Kubernetes restarts the container. Readiness Probe: Determines if the container is ready to serve traffic. If the readiness probe fails, the pod is removed from load balancers, and no traffic is routed to it. Startup Probe: Similar to the liveness probe, but only runs during the initial startup of a container. It helps delay the liveness and readiness probes until the application inside the container has started.
P
phcunha
2024-09-22
1 upvote
Think of a probe in Kubernetes like a heart rate monitor attached to a patient in a hospital. Just as the heart rate monitor continuously checks the patient's heart rate to ensure they are alive and functioning correctly, Kubernetes probes continuously monitor the health of containers to ensure they are running and capable of serving traffic. If the heart rate monitor detects irregularities or a lack of heartbeat, medical staff take action to revive or stabilize the patient. Similarly, if Kubernetes probes detect issues with a container, Kubernetes takes action to restart or replace the container, ensuring the application remains available and responsive.
S
shahy0
2025-02-28
Selected C1 upvote
Probes are used to determine if a container is running correctly and if it is ready to serve traffic. Kubernetes supports three types of probes: Liveness Probe Readiness Probe Startup Probe
Question 11 of 25
Which Kubernetes feature would you use to guard against split brain scenarios with your distributed application?
Show answer
Correct answer: D
How others answered
D56%
B44%
Only 56% agreed on this answer — treat it as contested rather than settled.
Explanation
D. StatefulSet While consensus protocols are generally used to prevent split brain scenarios in distributed systems, the provided information highlights that StatefulSets are specifically designed to ensure the stability and integrity of distributed and clustered applications. StatefulSets maintain "at most one" semantics, which helps prevent multiple instances of the same identity, reducing the risk of split brain scenarios and data loss in quorum-based systems. StatefulSets are well-suited for applications that require stable network identity and storage, providing mechanisms to manage pod identities, persistent storage, and ordered deployment and scaling. Therefore, StatefulSets are the most appropriate Kubernetes feature to mitigate the risk of split brain scenarios in this context.
Adapted from community discussion by SeaH0rse66 · 2024-05-17 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 11 Report an issue
Candidate context
Question 11 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
S
SeaH0rse66
2024-05-17
Selected D3 upvotes
D. StatefulSet While consensus protocols are generally used to prevent split brain scenarios in distributed systems, the provided information highlights that StatefulSets are specifically designed to ensure the stability and integrity of distributed and clustered applications. StatefulSets maintain "at most one" semantics, which helps prevent multiple instances of the same identity, reducing the risk of split brain scenarios and data loss in quorum-based systems. StatefulSets are well-suited for applications that require stable network identity and storage, providing mechanisms to manage pod identities, persistent storage, and ordered deployment and scaling. Therefore, StatefulSets are the most appropriate Kubernetes feature to mitigate the risk of split brain scenarios in this context.
S
shahy0
2025-02-28
Selected D1 upvote
A. Replication controllers: Manage the number of replicas of a pod but do not provide the stable network identities or ordered deployment required to prevent split-brain scenarios. B. Consensus protocols: While consensus protocols (like Raft or Paxos) are used within distributed systems to prevent split-brain, they are not a Kubernetes feature. They are implemented within the application itself. C. Rolling updates: Ensure that updates to applications are done gradually to avoid downtime, but they do not address the stable identities or ordered scaling needed to prevent split-brain scenarios. By using StatefulSets, you can effectively manage stateful applications and guard against split-brain scenarios in your distributed applications running on Kubernetes.
P
pulsefire
2024-03-07
Selected D3 upvotes
https://kubernetes.io/docs/tasks/run-application/force-delete-stateful-set-pod/#:~:text=split%20brain%20scenario%20in%20quorum%2Dbased%20systems
S
SeaH0rse66
2024-05-17
1 upvote
chatGPT is wrong...D. StatefulSet While consensus protocols are generally used to prevent split brain scenarios in distributed systems, the provided information highlights that StatefulSets are specifically designed to ensure the stability and integrity of distributed and clustered applications. StatefulSets maintain "at most one" semantics, which helps prevent multiple instances of the same identity, reducing the risk of split brain scenarios and data loss in quorum-based systems. StatefulSets are well-suited for applications that require stable network identity and storage, providing mechanisms to manage pod identities, persistent storage, and ordered deployment and scaling. Therefore, StatefulSets are the most appropriate Kubernetes feature to mitigate the risk of split brain scenarios in this context.
Question 12 of 25
What feature must a CNI support to control specific traffic flows for workloads running in Kubernetes?
Show answer
Correct answer: D
How others answered
D100%
Explanation
Think of Network Policies in Kubernetes as security checkpoints at different entrances to a building. Just as security personnel at each entrance check IDs and verify permissions before allowing individuals to enter specific areas of the building, Network Policies control the flow of network traffic within the Kubernetes cluster, ensuring that only authorized Pods can communicate with each other and that access to sensitive services is restricted according to defined rules.
Adapted from community discussion by phcunha · 2024-09-22 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 12 Report an issue
Candidate context
Question 12 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
P
pulsefire
2024-09-07
Selected D3 upvotes
https://kubernetes.io/docs/concepts/services-networking/network-policies/#:~:text=Network%20Policies-,Network%20Policies,might%20consider%20using%20Kubernetes%20NetworkPolicies%20for%20particular%20applications%20in%20your%20cluster.,-NetworkPolicies%20are%20an
P
phcunha
2024-09-22
2 upvotes
Think of Network Policies in Kubernetes as security checkpoints at different entrances to a building. Just as security personnel at each entrance check IDs and verify permissions before allowing individuals to enter specific areas of the building, Network Policies control the flow of network traffic within the Kubernetes cluster, ensuring that only authorized Pods can communicate with each other and that access to sensitive services is restricted according to defined rules.
S
shahy0
2025-02-28
Selected D1 upvote
Network Policies are a Kubernetes feature that allows you to control the traffic flow to and from pods. They enable you to define rules for how pods can communicate with each other and with other network endpoints. This is essential for securing workloads and controlling specific traffic flows within a Kubernetes cluster.
Question 13 of 25
What is the main role of the Kubernetes DNS within a cluster?
Show answer
Correct answer: D
How others answered
D100%
Explanation
Kubernetes DNS provides DNS resolution services within a Kubernetes cluster. It ensures that Pods and Services can be discovered and accessed by other Pods and Services using consistent DNS names. This enables seamless communication between different components within the Kubernetes cluster, regardless of their underlying network configurations.
Adapted from community discussion by SeaH0rse66 · 2024-11-17 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 13 Report an issue
Candidate context
Question 13 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
S
SeaH0rse66
2024-11-17
Selected D2 upvotes
Kubernetes DNS provides DNS resolution services within a Kubernetes cluster. It ensures that Pods and Services can be discovered and accessed by other Pods and Services using consistent DNS names. This enables seamless communication between different components within the Kubernetes cluster, regardless of their underlying network configurations.
S
shahy0
2025-02-28
Selected D1 upvote
The main role of Kubernetes DNS within a cluster is to provide consistent DNS names for pods and services, enabling reliable communication between workloads. This service discovery mechanism allows applications and services to locate and communicate with each other using DNS names rather than IP addresses, which can change over time.
P
phcunha
2024-09-22
1 upvote
Think of Kubernetes DNS as the address book in a large office building. Just as the address book provides a consistent reference for finding the location of different departments or individuals within the building, Kubernetes DNS provides consistent DNS names for Pods and Services, allowing workloads within the cluster to discover and communicate with each other efficiently, regardless of their dynamic IP addresses or locations.
Question 14 of 25
Scenario: You have a Kubernetes cluster hosted in a public cloud provider. When trying to create a Service of type LoadBalancer, the external-ip is stuck in the "Pending" state. Which Kubernetes component is failing in this scenario?
Show answer
Correct answer: A
How others answered
A100%
Explanation
B,C,D are not standards of Kubernetes. The Cloud Controller Manager is a Kubernetes component responsible for managing cloud-specific resources and integrations, including load balancers provided by the cloud provider. It interacts with the cloud provider's API to provision, configure, and manage resources such as load balancers. If the Service's external IP address remains in the "Pending" state, it suggests that there may be an issue with the Cloud Controller Manager's ability to communicate with the cloud provider's API or to provision the necessary resources.
Adapted from community discussion by SeaH0rse66 · 2024-11-17 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 14 Report an issue
Candidate context
Question 14 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
S
SeaH0rse66
2024-11-17
Selected A2 upvotes
B,C,D are not standards of Kubernetes. The Cloud Controller Manager is a Kubernetes component responsible for managing cloud-specific resources and integrations, including load balancers provided by the cloud provider. It interacts with the cloud provider's API to provision, configure, and manage resources such as load balancers. If the Service's external IP address remains in the "Pending" state, it suggests that there may be an issue with the Cloud Controller Manager's ability to communicate with the cloud provider's API or to provision the necessary resources.
S
shahy0
2025-02-28
Selected A1 upvote
The Cloud Controller Manager is a Kubernetes component that integrates with the cloud provider's API to manage resources such as load balancers, nodes, and storage. When you create a Service of type LoadBalancer, the Cloud Controller Manager is responsible for provisioning the external load balancer and assigning an external IP address.
S
sad_schedule
2024-07-12
2 upvotes
https://kubernetes.io/docs/concepts/architecture/cloud-controller/#service-controller
Question 15 of 25
What are the characteristics for building every cloud-native application?
Show answer
Correct answer: D
How others answered
D75%
A25%
Explanation
A cloud native application is engineered to run on a platform and is designed for resiliency, agility, operability, and observability. Resiliency embraces failures instead of trying to prevent them; it takes advantage of the dynamic nature of running on a platform. Agility allows for fast deployments and quick iterations. Operability adds control of application life cycles from inside the application instead of relying on external processes and monitors. Observability provides information to answer questions about application state. https://www.oreilly.com/library/view/cloud-native-infrastructure/9781491984291/ch01.html
Adapted from community discussion by alex78 · 2024-11-02 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
cncf.io documentation
Permanent link to question 15 Report an issue
Candidate context
Question 15 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
A
alex78
2024-11-02
Selected D2 upvotes
A cloud native application is engineered to run on a platform and is designed for resiliency, agility, operability, and observability. Resiliency embraces failures instead of trying to prevent them; it takes advantage of the dynamic nature of running on a platform. Agility allows for fast deployments and quick iterations. Operability adds control of application life cycles from inside the application instead of relying on external processes and monitors. Observability provides information to answer questions about application state. https://www.oreilly.com/library/view/cloud-native-infrastructure/9781491984291/ch01.html
S
shahy0
2025-02-28
Selected D1 upvote
Resiliency: The ability of an application to recover from failures and continue to function. This includes handling transient faults, ensuring data consistency, and maintaining service availability. Agility: The ability to quickly develop, test, and deploy new features and updates. This often involves practices like continuous integration and continuous deployment (CI/CD), as well as the use of microservices architecture. Operability: The ease with which an application can be managed, monitored, and maintained in production. This includes aspects like automated deployments, scaling, and self-healing capabilities. Observability: The ability to gain insights into the internal state of an application through metrics, logs, and traces. This helps in monitoring the health of the application, diagnosing issues, and improving performance.
H
hovnival
2024-11-01
Selected D2 upvotes
Folks I ran the same questions again in Copilot and week after it says correct answer is D. I am very sorry about that Apologies. Confirmed by ChatGPT answer is D. It is a bit frustrating that copilot is not consistent in aswer as I did copy paste like last time.
E
EzBL
2024-09-19
Selected D2 upvotes
Availability is highly desirable, but it's a consequence of achieving resiliency through proper design and implementation.
Question 16 of 25
Kubernetes supports multiple virtual clusters backed by the same physical cluster. These virtual clusters are called:
Show answer
Correct answer: A
How others answered
A100%
Explanation
https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/ "Namespaces are intended for use in environments with many users spread across multiple teams, or projects. For clusters with a few to tens of users, you should not need to create or think about namespaces at all. Start using namespaces when you need the features they provide."
Adapted from community discussion by SeaH0rse66 · 2024-11-17 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 16 Report an issue
Candidate context
Question 16 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
S
SeaH0rse66
2024-11-17
Selected A2 upvotes
https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/ "Namespaces are intended for use in environments with many users spread across multiple teams, or projects. For clusters with a few to tens of users, you should not need to create or think about namespaces at all. Start using namespaces when you need the features they provide."
S
shahy0
2025-02-28
Selected A1 upvote
Namespaces in Kubernetes are virtual clusters that provide resource isolation, access control, and organization within a single physical cluster. They enable multiple teams or projects to share the same physical cluster without interfering with each other.
P
phcunha
2024-09-22
1 upvote
Think of namespaces in Kubernetes as different floors in a large office building. Each floor represents a separate workspace for different teams or departments within the organization. Just as each floor has its own set of offices, meeting rooms, and facilities, each namespace in Kubernetes has its own set of resources, configurations, and access controls, providing isolation and organization within the cluster.
U
unkun
2024-07-31
2 upvotes
https://jamesdefabia.github.io/docs/user-guide/namespaces/ Answer is correct "A"
Question 17 of 25
How can you monitor the progress for an updated Deployment/DaemonSets/StatefulSets?
Show answer
Correct answer: D
How others answered
D62%
A38%
Only 62% agreed on this answer — treat it as contested rather than settled.
Explanation
Option A (kubectl rollout watch) is not the correct choice because the kubectl rollout watch command is used to continuously monitor the rollout progress of a deployment, allowing you to watch for changes in the rollout status in real-time. However, it is specifically designed for monitoring deployments and does not directly apply to DaemonSets or StatefulSets. While you could use kubectl rollout watch for deployments, it may not provide accurate or relevant information for DaemonSets or StatefulSets. Therefore, option A is not the most suitable command for monitoring the progress of updates to DaemonSets or StatefulSets. On the other hand, option D (kubectl rollout status) is a more generic command that works for all types of rollouts, including deployments, DaemonSets, and StatefulSets. It provides detailed information about the status of the rollout, making it a better choice for monitoring the progress of updates across different types of workload controllers in Kubernetes.
Adapted from community discussion by SeaH0rse66 · 2024-05-17 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 17 Report an issue
Candidate context
Question 17 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
S
SeaH0rse66
2024-05-17
Selected D2 upvotes
Option A (kubectl rollout watch) is not the correct choice because the kubectl rollout watch command is used to continuously monitor the rollout progress of a deployment, allowing you to watch for changes in the rollout status in real-time. However, it is specifically designed for monitoring deployments and does not directly apply to DaemonSets or StatefulSets. While you could use kubectl rollout watch for deployments, it may not provide accurate or relevant information for DaemonSets or StatefulSets. Therefore, option A is not the most suitable command for monitoring the progress of updates to DaemonSets or StatefulSets. On the other hand, option D (kubectl rollout status) is a more generic command that works for all types of rollouts, including deployments, DaemonSets, and StatefulSets. It provides detailed information about the status of the rollout, making it a better choice for monitoring the progress of updates across different types of workload controllers in Kubernetes.
M
miskill
2024-09-07
Selected D1 upvote
The correct answer to the question "How can you monitor the progress for an updated Deployment/DaemonSets/StatefulSets?" is D. kubectl rollout status. Explanation: The kubectl rollout status command is used to monitor the progress of a rollout for Kubernetes resources such as Deployments, DaemonSets, or StatefulSets. This command provides real-time updates on whether the new Pods are being created correctly and whether the old ones are being terminated. It ensures that the rollout is proceeding as expected and alerts if any issues occur during the update. Other options like kubectl rollout watch, kubectl rollout progress, and kubectl rollout state are not valid Kubernetes commands for monitoring rollout progress. The proper command to use for tracking progress is kubectl rollout status
H
heniabida
2024-11-05
Selected D1 upvote
❯ kubectl rollout watch error: unknown command "watch" Available Commands: history View rollout history pause Mark the provided resource as paused restart Restart a resource resume Resume a paused resource status Show the status of the rollout undo Undo a previous rollout --> So answer is D
S
shahy0
2025-02-28
Selected D1 upvote
The kubectl rollout status command is used to monitor the progress of an updated Deployment, DaemonSet, or StatefulSet in Kubernetes. It provides real-time updates on the status of the rollout, including whether it is complete or if there are any issues.
Question 18 of 25
What is the primary mechanism to identify grouped objects in a Kubernetes cluster?
Show answer
Correct answer: B
How others answered
B56%
C44%
Only 56% agreed on this answer — treat it as contested rather than settled.
Explanation
Labels are key-value pairs that you attach to Kubernetes objects. They define attributes and allow you to "tag" objects to group or identify them. Label Selectors are used to query or filter objects that have certain labels. While selectors allow you to find or match objects based on labels, they don't define the labels themselves. Labels are the mechanism used to mark or identify objects. Without labels, there would be nothing for Label Selectors to query. Label Selectors are only tools to query/filter based on existing labels.
Adapted from community discussion by abitwrong · 2024-12-17 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 18 Report an issue
Candidate context
Question 18 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
A
abitwrong
2024-12-17
Selected B3 upvotes
Labels are key-value pairs that you attach to Kubernetes objects. They define attributes and allow you to "tag" objects to group or identify them. Label Selectors are used to query or filter objects that have certain labels. While selectors allow you to find or match objects based on labels, they don't define the labels themselves. Labels are the mechanism used to mark or identify objects. Without labels, there would be nothing for Label Selectors to query. Label Selectors are only tools to query/filter based on existing labels.
S
SeaH0rse66
2024-05-17
Selected B3 upvotes
Labels and label selectors work hand in hand to identify and group objects, so it's easy to see why it might seem tricky. Labels provide the metadata for identification and grouping, while label selectors enable users to query and select objects based on those labels. Both are essential components of Kubernetes's flexibility and functionality.
M
miskill
2024-09-23
Selected B1 upvote
The correct answer is: B. Labels Explanation: Labels are the primary mechanism used to identify and group objects in a Kubernetes cluster. They are key-value pairs attached to objects (such as Pods, Services, etc.) and can be used to organize, select, and filter resources within the cluster. Although C. Label Selector is also used to query and select objects based on labels, the labels themselves (B) are the mechanism that allows objects to be grouped.
S
shahy0
2025-03-01
Selected B1 upvote
Labels are the primary mechanism to identify and group objects in a Kubernetes cluster. Labels are key-value pairs that can be attached to Kubernetes objects such as Pods, Services, and Deployments. They are used to organize and select subsets of objects based on specific criteria.
Question 19 of 25
Services and Pods in Kubernetes are ______ objects.
Show answer
Correct answer: D
How others answered
D100%
Explanation
Services and Pods in Kubernetes are: D. REST objects In Kubernetes, resources such as Services and Pods are represented as RESTful objects. This means that they can be accessed and manipulated using HTTP methods such as GET, POST, PUT, and DELETE via the Kubernetes API server. While configurations for Kubernetes resources are often written in YAML or JSON format, these formats are used to define the desired state of the objects rather than representing the nature of the objects themselves
Adapted from community discussion by 377ecc2 · 2024-05-23 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 19 Report an issue
Candidate context
Question 19 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
3
377ecc2
2024-05-23
Selected D3 upvotes
Services and Pods in Kubernetes are: D. REST objects In Kubernetes, resources such as Services and Pods are represented as RESTful objects. This means that they can be accessed and manipulated using HTTP methods such as GET, POST, PUT, and DELETE via the Kubernetes API server. While configurations for Kubernetes resources are often written in YAML or JSON format, these formats are used to define the desired state of the objects rather than representing the nature of the objects themselves
P
pulsefire
2024-03-07
Selected D4 upvotes
should be D. REST objects https://docs.openshift.com/container-platform/3.11/architecture/core_concepts/pods_and_services.html#:~:text=Like%20pods%2C%20services%20are%20REST%20objects.
M
mc2301
2024-09-28
2 upvotes
The Kubernetes API is the most important component of a Kubernetes cluster. Without it, communication with the cluster is not possible, every user and every component of the cluster itself needs the api-server. Like many other APIs, the Kubernetes API is implemented as a RESTful interface that is exposed over HTTPS. Through the API, a user or service can create, modify, delete or retrieve resources that reside in Kubernetes. D seems legit
2
2211094
2025-01-12
Selected D1 upvote
B. CRI-O CRI-O is a lightweight container runtime specifically designed for Kubernetes. It implements the Kubernetes Container Runtime Interface (CRI) to enable the use of containers within Kubernetes clusters. It is responsible for running the containers specified by Kubernetes
Question 20 of 25
Which Kubernetes resource uses immutable: true boolean field?
Show answer
Correct answer: C
How others answered
C91%
Explanation
Kubernetes ConfigMap and Secret resources have a field called immutable which, if set to true, ensures that the data of ConfigMap/Secret cannot be updated after the resource is created.
Adapted from community discussion by Debayan · 2024-10-05 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 20 Report an issue
Candidate context
Question 20 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
D
Debayan
2024-10-05
Selected C3 upvotes
Kubernetes ConfigMap and Secret resources have a field called immutable which, if set to true, ensures that the data of ConfigMap/Secret cannot be updated after the resource is created.
A
alex78
2024-11-02
Selected C3 upvotes
https://kubernetes.io/docs/concepts/configuration/configmap/#configmap-immutable
B
Bolgarwow
2024-10-01
3 upvotes
apiVersion: v1 kind: ConfigMap metadata: name: test-immutable labels: app.kubernetes.io/name: kubernetes-hacks-and-tricks app.kubernetes.io/created-by: ssbostan immutable: true ConfigMap
H
hovnival
2024-10-23
Selected C2 upvotes
Copilot says C giving also similiar example like Bolgarwow gave.
Question 21 of 25
Can a Kubernetes Service expose multiple ports?
Show answer
Correct answer: B
How others answered
B54%
C46%
Only 54% agreed on this answer — treat it as contested rather than settled.
Explanation
B is correct: C suggests that only different port numbers are required, but it overlooks the need for a unique name to avoid confusion and conflicts, especially when multiple ports are involved. Therefore, B is correct because, in addition to different port numbers, a unique name for each port is required.
Adapted from community discussion by miskill · 2024-09-23 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 21 Report an issue
Candidate context
Question 21 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
M
miskill
2024-09-23
Selected B3 upvotes
B is correct: C suggests that only different port numbers are required, but it overlooks the need for a unique name to avoid confusion and conflicts, especially when multiple ports are involved. Therefore, B is correct because, in addition to different port numbers, a unique name for each port is required.
M
mc2301
2024-09-28
3 upvotes
Multi-port Services For some Services, you need to expose more than one port. Kubernetes lets you configure multiple port definitions on a Service object. When using multiple ports for a Service, you must give all of your ports names so that these are unambiguous. For example: apiVersion: v1 kind: Service metadata: name: my-service spec: selector: app.kubernetes.io/name: MyApp ports: - name: http protocol: TCP port: 80 targetPort: 9376 - name: https protocol: TCP port: 443 targetPort: 9377
A
abitwrong
2024-12-06
Selected B2 upvotes
https://kubernetes.io/docs/concepts/services-networking/service/#multi-port-services
S
shahy0
2025-03-01
Selected B1 upvote
a Service can expose multiple ports. When defining a Service with multiple ports, you must specify a unique name for each port to avoid ambiguity. This allows the Service to route traffic to different ports on the backend Pods.
Question 22 of 25
Which command provides information about the field replicas within the spec resource of a deployment object?
Show answer
Correct answer: B
How others answered
B100%
Explanation
A. kubectl get deployment.spec.replicas: This command attempts to retrieve the value of replicas directly from the deployment resource. However, it's not a standard way to access nested fields like spec.replicas. B. kubectl explain deployment.spec.replicas: This command is used to get documentation or information about a specific field within a Kubernetes resource definition. It will provide details about what the replicas field represents within the spec of a deployment. C. kubectl describe deployment.spec.replicas: This command describes an existing resource, such as a deployment, but it does not specifically explain the meaning or purpose of a field like replicas within the spec. D. kubectl explain deployment --spec.replicas: This command is close but not entirely correct. It attempts to explain a flag --spec.replicas for the kubectl explain command, rather than directly explaining the replicas field within the spec of a deployment.
Adapted from community discussion by EzBL · 2024-06-28 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 22 Report an issue
Candidate context
Question 22 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
E
EzBL
2024-06-28
Selected B2 upvotes
A. kubectl get deployment.spec.replicas: This command attempts to retrieve the value of replicas directly from the deployment resource. However, it's not a standard way to access nested fields like spec.replicas. B. kubectl explain deployment.spec.replicas: This command is used to get documentation or information about a specific field within a Kubernetes resource definition. It will provide details about what the replicas field represents within the spec of a deployment. C. kubectl describe deployment.spec.replicas: This command describes an existing resource, such as a deployment, but it does not specifically explain the meaning or purpose of a field like replicas within the spec. D. kubectl explain deployment --spec.replicas: This command is close but not entirely correct. It attempts to explain a flag --spec.replicas for the kubectl explain command, rather than directly explaining the replicas field within the spec of a deployment.
H
hovnival
2024-05-03
Selected B2 upvotes
guys this one is totally B. kubectl explain deployment.spec.replicas kubectl explain deployment => info about deployment kubectl explain deployment.spec => info about spec in deployment kubectl explain deployment.spec.replicas => info aout replicas in spec in deployment
M
miskill
2024-09-23
Selected B1 upvote
The correct answer is: B. kubectl explain deployment.spec.replicas Explanation: The command kubectl explain is used to provide detailed information about the fields of Kubernetes objects, including their specifications. The command kubectl explain deployment.spec.replicas specifically provides information about the replicas field within the spec of a deployment object. This is the most appropriate command for getting details about that particular field.
A
alex78
2024-05-03
Selected B2 upvotes
https://kubernetes.io/docs/reference/kubectl/generated/kubectl_explain/
Question 23 of 25
Which kubernetes component is the smallest deployable unit of computing?
Show answer
Correct answer: C
How others answered
C100%
Explanation
Explanation: • In Kubernetes, the smallest deployable unit of computing is a Pod. • A Pod represents a single instance of a running process in your cluster. • It can contain one or more containers that are tightly coupled and share the same network namespace, IPC namespace, and other resources. • Pods are the basic building blocks of Kubernetes applications and are scheduled onto nodes in the cluster.
Adapted from community discussion by EzBL · 2024-03-19 · 3 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Permanent link to question 23 Report an issue
Candidate context
Question 23 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
E
EzBL
2024-03-19
Selected C3 upvotes
Explanation: • In Kubernetes, the smallest deployable unit of computing is a Pod. • A Pod represents a single instance of a running process in your cluster. • It can contain one or more containers that are tightly coupled and share the same network namespace, IPC namespace, and other resources. • Pods are the basic building blocks of Kubernetes applications and are scheduled onto nodes in the cluster.
A
AbhishekJoshi
2023-12-17
Selected C4 upvotes
Container is not a object in k8s, pod is the only smallest unit in k8s
S
SeaH0rse66
2024-05-17
Selected C2 upvotes
A Pod is the smallest deployable unit of computing in Kubernetes. It represents a single instance of a running process in your cluster. Pods can contain one or more containers that are tightly coupled and share resources, such as network and storage, and are scheduled onto nodes in the Kubernetes cluster., this is in a way a "unit of measure" , like the atom of Kubernetes, the container would be like a proton...
M
miskill
2024-09-23
Selected C1 upvote
The correct answer is: C. Pod Explanation: In Kubernetes, the Pod is the smallest deployable unit of computing. A Pod can contain one or more containers, but it is the fundamental unit that Kubernetes deploys, manages, and scales. Containers within a Pod share the same network and storage resources, making the Pod the atomic unit for scheduling and running containers in Kubernetes.
Question 24 of 25
Which of the following capabilities are you allowed to add to a container using the Restricted policy?
Show answer
Correct answer: D
How others answered
D80%
Explanation
https://kubernetes.io/docs/concepts/security/pod-security-standards/ Capabilities (v1.22+) Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability. This is Linux only policy in v1.25+ (.spec.os.name != "windows")
Adapted from community discussion by Andrei_Z · 2024-09-20 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 24 Report an issue
Candidate context
Question 24 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
A
alex78
2024-05-04
Selected D3 upvotes
https://docs.openshift.com/dedicated/authentication/managing-security-context-constraints.html
A
Andrei_Z
2024-09-20
Selected D2 upvotes
https://kubernetes.io/docs/concepts/security/pod-security-standards/ Capabilities (v1.22+) Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability. This is Linux only policy in v1.25+ (.spec.os.name != "windows")
S
shahy0
2025-03-01
Selected D1 upvote
The Restricted policy in Kubernetes is designed to enforce strict security constraints on containers, but it does allow certain capabilities that are considered safe and necessary for common container operations. Among the capabilities listed, NET_BIND_SERVICE is typically allowed under the Restricted policy because it is often needed for binding to network ports below 1024, which is a common requirement for many applications
A
abitwrong
2024-12-06
Selected D1 upvote
Containers must drop ALL capabilities, and are only permitted to add back the NET_BIND_SERVICE capability. Reference: https://kubernetes.io/docs/concepts/security/pod-security-standards/#:~:text=add%20back%20the-,NET_BIND_SERVICE,-capability.%20This
Question 25 of 25
Which of the following options includes valid API versions?
Show answer
Correct answer: C
How others answered
C94%
Explanation
https://kubernetes.io/docs/reference/using-api/ Alpha: The version names contain alpha (for example, v1alpha1) Beta: The version names contain beta (for example, v2beta3). Stable: The version name is vX where X is an integer.
Adapted from community discussion by SeaH0rse66 · 2024-05-18 · 2 community upvotes. Third-party contribution; reviewed by our quality filter, not independently verified.
Supporting references
Kubernetes documentation
Permanent link to question 25 Report an issue
Candidate context
Question 25 discussion
These are quality-filtered excerpts from third-party community discussion. They can be useful reasoning signals, but they are not official answers and have not been independently verified by KCNA or CertExamHQ.
M
miskill
2024-09-23
Selected C2 upvotes
The correct answer is: C. v1alpha1, v2beta3, v2 Explanation: Kubernetes follows a specific convention for API versioning, which includes versions like v1alpha1, v2beta3, and stable versions like v1, v2, etc. The format typically consists of a version (vX), followed by an optional alpha or beta designation with a version number (e.g., alpha1, beta3). This structure is used to represent different stages of API stability, from alpha (experimental) to beta (more stable) to full release (e.g., v1, v2).
S
SeaH0rse66
2024-05-18
Selected C2 upvotes
https://kubernetes.io/docs/reference/using-api/ Alpha: The version names contain alpha (for example, v1alpha1) Beta: The version names contain beta (for example, v2beta3). Stable: The version name is vX where X is an integer.
2
2211094
2025-01-12
Selected C1 upvote
v1alpha1, v2beta3, v2 In Kubernetes, valid API versions follow the format v[MAJOR][MINOR][STABILITY], where: v1alpha1 represents an alpha version of the API, indicating an early stage and potentially unstable version. v2beta3 represents a beta version of the API, indicating a more stable version that is not yet finalized. v2 represents a stable version of the API.
A
andytsangchun
2024-04-29
Selected C2 upvotes
Its C From official docs: https://kubernetes.io/docs/reference/using-api/

Keyboard:J Kmove between questionsA–Dselect an answerRshow or hide the answer← →change page

About this question bank

Community-contributed

Compiled from exam discussions posted publicly by other people on ExamTopics. Copyright in each contribution rests with its original author; it is reproduced here for study. Not verified by us — most items carry no explanation. To request removal, see our content policy.

Compiled from ExamTopics community discussions

Compiled from publicly posted community exam discussions. Contributed by third parties rather than written here, so accuracy varies and most items carry no explanation.

Across the private full bank: 42 explanations, 138 questions with candidate context and 26 questions with direct citations.

Version 1.0.0 · bank updated 2026-08-29. How we source questions