All images with their tags are unique

The image ID is what really makes an image unique, we can have an Image ID with many names and tags, but they will all reference the same layers and meta-information

Only base images on the root registry namespace are unique because all other images are based on these

All the preceding answers are correct

Data Plane

Control Plane

Global Plane

None of the Above

We can build images from containers, committing their read-write layers on top of read-only ones

We can use a Dockerfile, starting with a base image

We can start from an empty one, known as scratch

All of the above

kube-apiserver

kube scheduler

kube-controller-manager

etcd

Pod

New Cluster

User

Cluster

Replicas

Readiness

Cluster Autoscaler

Liveness Probes

Load Balance

No node will expose a service on port 8080.

All nodes will publish port 8080.

We should use privileged containers to expose port 8080.

We must use --network=host to publish ports below port 30000.

It consists of a relatively high number of relatively big objects

it allows you to declare or specify the desired state of your resource and tries to keep the current state of Kubernetes objects in sync with the desired state.

Humans often need to read and write the objects

Transactions across objects are required

kube-proxy

kubelet

kube-scheduler

kube-controller-manager