Linux Foundation Kubernetes and Cloud Native Associate - KCNA FREE EXAM DUMPS QUESTIONS & ANSWERS

A. kubectl top B. kubectl cluster-info C. kubectl version D. kubectl api-resources

A. Leverage the Kubernetes Cluster Autoscaler to automatically start and stop nodes as they're needed. B. Commit to a specific level of spending to get discounted prices (with e.g. "reserved instances" or similar mechanisms). C. Use PriorityClasses so that the weekly batch job gets priority over other workloads running on the cluster, and can be completed on time. D. Run a group of nodes with the exact required size to complete the batch on time, and use a combination of taints, tolerations, and nodeSelectors to reserve these nodes to the batch jobs.

A. Privileged, Baseline, Restricted B. Baseline, Restricted, Privileged C. Baseline, Privileged, Restricted D. Privileged, Restricted, Baseline

A. RKE B. OpenShift C. k1s D. k3s

A. CRI-O B. Docker C. lxc D. runc

A. runC B. kata-containers C. gvisor D. runV

A. It is a specification for describing event data in common formats in all cloud providers including major cloud providers. B. It is a specification for describing event data in common formats to provide interoperability across services, platforms and systems. C. It is a Kubernetes specification for describing events data in common formats for iCloud services, iOS platforms and iMac. D. It is a specification for describing event data in common formats for Kubernetes network traffic management and cloud providers.

A. The network configuration for a group of Pods. B. An NGINX load balancer that gets deployed for an application. C. A static network mapping from a Pod to a port. D. A way to expose an application running on a set of Pods.

A. To manage cluster state information and handle all scheduling decisions for workloads. B. To allocate persistent storage volumes and manage distributed data replication for Pods. C. To provide internal DNS resolution and route service traffic between Pods and nodes. D. To ensure that containers defined in Pod specifications are running and remain healthy on the node.

A. Nodes # Cluster # Containers # Pods B. Containers # Pods # Cluster # Nodes C. Pods # Cluster # Containers # Nodes D. Cluster # Nodes # Pods # Containers

A. Run the containers as the user with group ID 0 (root) and any user ID. B. Allow privilege escalation from within a container as the default option. C. Run the containers as the user with user ID 0 (root) and any group ID. D. Disallow privilege escalation from within a container as the default option.

A. To define and attach persistent volumes that store application data across Pod restarts. B. To provide a stable endpoint for accessing Pods even when their IP addresses change. C. To automatically adjust the number of Pods based on CPU or memory utilization metrics. D. To centrally manage and apply runtime configuration values for application components.

A. Helm B. Kubernetes C. Rook D. Container Storage Interface (CSI)

A. When a container is unresponsive. B. When a container is ready to serve traffic. C. When a container exceeds resource limits. D. When a container has started successfully.

A. Forwarding data to the correct endpoints for Services. B. Managing access to the Kubernetes API. C. Managing data egress from the cluster nodes to the network. D. Implementing the Ingress resource type for application traffic.