nerdexam
Linux_Foundation

KCNA · Question #176

Which of the following is not the required field to describe Kubernetes objects?

The correct answer is D. Container. Kubernetes objects universally require apiVersion, kind, metadata, and spec fields, while Container is a field within the spec of specific object types like Pods, not a top-level required field for all objects.

Submitted by lukas.cz· May 4, 2026Kubernetes Fundamentals

Question

Which of the following is not the required field to describe Kubernetes objects?

Options

  • Ametadata
  • BapiVersion
  • CKind
  • DContainer
  • Espec

How the community answered

(63 responses)
  • A
    3% (2)
  • B
    5% (3)
  • C
    2% (1)
  • D
    89% (56)
  • E
    2% (1)

Why each option

Kubernetes objects universally require `apiVersion`, `kind`, `metadata`, and `spec` fields, while `Container` is a field within the `spec` of specific object types like Pods, not a top-level required field for all objects.

Ametadata

`metadata` is a required field for all Kubernetes objects, containing information like name, labels, and annotations.

BapiVersion

`apiVersion` is a required field that specifies the version of the Kubernetes API to which the object belongs.

CKind

`Kind` is a required field that specifies what kind of object is being created (e.g., Pod, Deployment, Service).

DContainerCorrect

`Container` is a field defined *within* the `spec` section of a Pod object (or other workload resources) to describe the container to be run. It is not one of the top-level required fields for *all* Kubernetes objects, unlike `apiVersion`, `kind`, `metadata`, and `spec`.

Espec

`spec` is a required field for most Kubernetes objects, describing the desired state of the object.

Concept tested: Kubernetes object required fields

Source: https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/

Topics

#Kubernetes Objects#YAML Structure#API Fields

Community Discussion

No community discussion yet for this question.

Full KCNA Practice