KCNA Question 33

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A1

  ny Kubernetes object definition, typically expressed in a YAML file, must include the following four top-level fields: apiVersion: Specifies the version of the Kubernetes API that the object belongs to. This determines the schema and available fields for the object. Examples include v1 for core objects like Pods, or apps/v1 for Deployments. kind: Defines the type of Kubernetes object being created. This could be Pod, Deployment, Service, Namespace, etc. metadata: Contains data that uniquely identifies the object and provides administrative information. This typically includes: name: A unique name for the object within its namespace. namespace (optional): The namespace the object belongs to. If not specified, it defaults to the default namespace. labels (optional): Key-value pairs used to organize and select objects. annotations (optional): Unstructured key-value pairs for attaching arbitrary non-identifying metadata.

• 5

  A. apiVersion, kind, metadata Explanation: In any Kubernetes object definition file, there are three mandatory fields that must exist: apiVersion: Specifies the version of the Kubernetes API that the object uses. This field ensures compatibility and defines the structure of the object. kind: Specifies the type of Kubernetes object being defined, such as Pod, Service, Deployment, etc. This field determines the behavior and functionality of the object. metadata: Contains metadata about the object, such as its name, namespace, labels, and annotations. This metadata is used by Kubernetes to identify and manage the object within the cluster. These fields are essential for Kubernetes to interpret and process the object correctly. The other options do not include all three mandatory fields or contain fields that are not universally required in every Kubernetes object.