EX282 sample questions

Question 1

A quantitative trading firm runs latency-critical algorithmic applications on OpenShift Container Platform 4.20 bare-metal worker nodes. The network infrastructure team requires secondary interfaces on pods to connect directly to an external low-latency market data network attached to `ens2f1`.

The upstream switch fabric enforces strict Port Security policies: each switchport is restricted to the single MAC address of the physical server NIC. Any incoming packet presenting an untrusted or newly generated MAC address causes an immediate port shutdown. Furthermore, the application team requires Layer 3 routing handled entirely in the host kernel stack, with pod IP addresses assigned from non-overlapping subnets without bridging overhead.

Which secondary network configuration satisfies the upstream switch port security constraint while routing traffic via the host network stack?

```mermaid
graph LR
subgraph WorkerNode["Worker Node (Bare Metal)"]
subgraph PodNS["Pod Network Namespace"]
net1["Interface: net1
IP: 192.168.50.15/24"]
end
HostStack["Linux Host IP Routing Stack"]
PhysicalNIC["Parent NIC: ens2f1
HWaddr: 52:54:00:ab:cd:ef"]
net1 -->|Shares Parent MAC| HostStack
HostStack --> PhysicalNIC
end
PhysicalNIC --> SwitchPort["ToR Switch Port
(Port Security: 1 MAC)"]
```

Accepted Answer

Create a `NetworkAttachmentDefinition` using the `ipvlan` CNI plugin configured with `mode: "l3"` and `master: "ens2f1"`

Answer

Create a `NetworkAttachmentDefinition` using the `ipvlan` CNI plugin configured with `mode: "l2"` and `master: "ens2f1"`

Answer

Create a `NetworkAttachmentDefinition` using the `macvlan` CNI plugin with `mode: "bridge"` and `master: "ens2f1"`

Answer

Create a `NetworkAttachmentDefinition` using the `bridge` CNI plugin with `bridge: "br-market"` and `macspoofchk: true`

Question 2

A systems administrator is configuring a secondary network attachment definition for pods to receive IP addresses dynamically from an existing external corporate DHCP server. What must be deployed or configured on the OpenShift Container Platform cluster for the secondary network attachment's DHCP IPAM plugin to acquire and renew leases?

Accepted Answer

Enable the DHCP IPAM CNI daemon via the Cluster Network Operator (CNO)

Answer

Deploy an in-cluster DHCP server pod in the `openshift-multus` namespace

Answer

Configure CoreDNS in `openshift-dns` with the `dhcp` Corefile plugin

Answer

Apply the annotation `k8s.v1.cni.cncf.io/dhcp-client: "true"` to each pod specification

Question 3

A cloud architect is designing secondary network attachments across worker nodes using the `whereabouts` IPAM plugin. The cluster does not have access to an external DHCP server. Which TWO statements accurately describe the configuration options and operational constraints of the `whereabouts` CNI plugin in OpenShift Container Platform 4.20? (Select TWO)

Accepted Answer

The parameter `network_name` can be specified across multiple `NetworkAttachmentDefinition` resources to share address pools across overlapping attachments

Accepted Answer

For IPv6 allocations, subnets with prefix lengths of `/64` or shorter must not be used due to uint64 offset calculation limits

Answer

Administrators must manually deploy and manage the `whereabouts-reconciler` CronJob to reclaim unassigned IPs

Answer

IPv6 subnets configured in `whereabouts` must be at least `/64` or wider to allow SLAAC autoconfiguration

Answer

The `whereabouts` plugin only allocates IP addresses from subnets locally bound to each individual node's physical interface

Question 4

A developer needs to isolate a namespace named `payment-processor` using a primary `UserDefinedNetwork` (UDN) with Layer 2 topology. What is the mandatory requirement regarding namespace labeling when configuring a primary user-defined network in OpenShift Container Platform 4.20?

Accepted Answer

The label `k8s.ovn.org/primary-user-defined-network: ""` must be present on the namespace at creation time and cannot be added after the namespace has already been created

Answer

The namespace must be labeled with `network.openshift.io/udn-enabled: "true"` by an administrator with cluster-admin privileges

Answer

The label `k8s.ovn.org/primary-user-defined-network: ""` can be added or removed dynamically at any time to trigger network migration

Answer

The namespace must have the label `security.openshift.io/scc: privileged` prior to applying the `UserDefinedNetwork` manifest

Question 5

When authoring a namespace-scoped `UserDefinedNetwork` (UDN) resource with `spec.topology: Layer3`, which subnet fields are mandatory under `spec.layer3.subnets`?

Accepted Answer

Each entry requires both `cidr` (cluster-level CIDR) and `hostSubnet` (node-level prefix length)

Answer

Each entry requires `networkCIDR`, `serviceNetworkCIDR`, and `hostPrefix`

Answer

Each entry requires `cidr` and an optional `gatewayIP` field

Answer

Entries accept only a string in CIDR notation, while node subnet slicing is computed automatically by the CNO

Question 6

True or False: In OpenShift Container Platform 4.20, a `ClusterUserDefinedNetwork` (CUDN) resource supports configuring either `Primary` or `Secondary` network roles across multiple target namespaces.

Accepted Answer

False

Answer

True

Free EX282 sample questions

A developer needs to isolate a namespace named `payment-processor` using a primary `UserDefinedNetwork` (UDN) with Layer 2 topology. What is the mandatory requirement regarding namespace labeling when configuring a primary user-defined network in OpenShift Container Platform 4.20?

When authoring a namespace-scoped `UserDefinedNetwork` (UDN) resource with `spec.topology: Layer3`, which subnet fields are mandatory under `spec.layer3.subnets`?

True or False: In OpenShift Container Platform 4.20, a `ClusterUserDefinedNetwork` (CUDN) resource supports configuring either `Primary` or `Secondary` network roles across multiple target namespaces.

6 more free samples are waiting