A new administrator is reviewing the architecture of an OpenShift cluster. They see that some nodes are labeled as 'control-plane' and others as 'worker'. What is the primary difference between these two node types?

Control plane nodes are used for storage, while worker nodes are used for compute.

Control plane nodes are physical servers, while worker nodes are virtual machines.

Control plane nodes are for management, while worker nodes are for networking.

Control plane nodes run the Kubernetes API and etcd, while worker nodes run user applications.

An organization is planning a production OpenShift deployment. They expect steady growth and want to ensure that the cluster remains available even if one of the primary management components fails. Which node deployment strategy best meets this requirement?

Deploy one control plane node and one provisioner node.

Deploy a single control plane node and multiple provisioner nodes.

Deploy three control plane nodes and two provisioner nodes.

Deploy five control plane nodes and no dedicated provisioner nodes.

A company is running a batch processing workload that is CPU-intensive and memory-hungry. They are planning an OpenShift cluster and want to ensure that these workloads do not interfere with cluster management operations. What is the most appropriate node configuration?

Dedicate provisioner nodes with high CPU and memory specifications for the batch workloads.

Deploy the batch workloads on a separate, non-OpenShift platform.

Run the batch workloads on the control plane nodes to utilize their spare capacity.

Use the same nodes for both control plane and provisioner roles to simplify management.

What is a key characteristic of provisioner nodes in OpenShift?

They are dedicated to running infrastructure components like the registry and router.

They are responsible for storing cluster configuration in etcd.

They are the primary nodes that users interact with via the API.

They are the nodes where user applications and pods are scheduled.

Juniper NetworksCertified Associate, Cloud

Domain 7Objective 3

Node Types (Provisioner and Control Plane) JN0-214 Practice Questions (Page 4)

Part of the Cloud Orchestration with OpenShift domain, which makes up ~10% of our current practice bank. Juniper Networks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~4–6 in this domain), expect 1–2 from this objective — we provide 27 practice questions to prepare you well beyond it. (estimate)

27questions here

6free pages

5concepts

Questions 16–20

16application · medium
A company is deploying OpenShift for a production environment. They have a limited budget and want to minimize the number of nodes while still ensuring high availability for the control plane. What is the minimum number of control plane nodes they should deploy?
Select an answer first
17application · easy
A new administrator is reviewing the architecture of an OpenShift cluster. They see that some nodes are labeled as 'control-plane' and others as 'worker'. What is the primary difference between these two node types?
Select an answer first
18application · medium
An organization is planning a production OpenShift deployment. They expect steady growth and want to ensure that the cluster remains available even if one of the primary management components fails. Which node deployment strategy best meets this requirement?
Select an answer first
19application · medium
A company is running a batch processing workload that is CPU-intensive and memory-hungry. They are planning an OpenShift cluster and want to ensure that these workloads do not interfere with cluster management operations. What is the most appropriate node configuration?
Select an answer first
20foundation · easy
What is a key characteristic of provisioner nodes in OpenShift?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to JN0-214

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Juniper Networks. “JN0-214” is a trademark of its owner, used for identification only.