Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Red Hat
Exam Format
Registration
Validity
Skills this practice test covers
- Read the cluster network settings and attach pods to secondary networks with Multus.
- Isolate namespaces on user-defined networks and prove that the isolation holds.
- Forward DNS for a custom domain, and expose applications through MetalLB pools and secure routes.
- Restrict outbound traffic with EgressFirewall rules and fixed EgressIP addresses.
- Build node bonds, VLANs and bridges with NMState, and peer the cluster with routers over BGP.
- Collect and filter network flows with a FlowCollector, then turn them into Prometheus metrics.
Explore related topics
EX282 exam content
8 domains · 36 topics · 150 questions
Manage core networking in Red Hat OpenShift Container Platform22 questions
This domain starts with the default cluster network: the Cluster Network Operator, the active network plugin, and settings such as the cluster CIDRs, MTU and host prefix. It then adds secondary networks, which give a pod extra interfaces through Multus.
Skills tested
- Read the cluster network objects to find the active plugin, clusterNetwork, serviceNetwork, hostPrefix and MTU.
- Write a NetworkAttachmentDefinition that uses the macvlan, ipvlan or bridge CNI plugin.
- Pick static, host-local or DHCP IP address management for a secondary network.
- Attach a pod to a secondary network with the k8s.v1.cni.cncf.io/networks annotation.
Questions by topic
- Create secondary networks using macvlan, ipvlan, and bridge CNI plugins5
- Configure IP address management (static, host-local, DHCP) for secondary networks4
- Identify the active network plugin and its settings (network CIDRs, MTU, host prefix)5
- Configure additional network interfaces using Multus CNI and NetworkAttachmentDefinition resources4
- Inspect and interpret the Cluster Network Operator configuration4
Implement and manage user-defined networks in Red Hat OpenShift Container Platform21 questions
User-defined networks give one namespace, or a chosen set of namespaces, a network of its own that is isolated from the default cluster network. Candidates create these networks, run workloads on them and troubleshoot connections that fail.
Skills tested
- Create a UserDefinedNetwork with a Layer2 or Layer3 topology for one namespace.
- Join several namespaces to one network with a ClusterUserDefinedNetwork and a namespaceSelector.
- Set the primary user-defined network label when the namespace is created, because it cannot be added later.
- Apply NetworkPolicy resources on a user-defined network and test which traffic gets through.
Questions by topic
- Create UserDefinedNetwork resources for namespace-scoped network isolation4
- Create ClusterUserDefinedNetwork resources that span multiple namespaces4
- Deploy workloads on user-defined networks and verify isolation from the default cluster network4
- Apply NetworkPolicy resources to user-defined networks5
- Troubleshoot connectivity and isolation issues on user-defined networks4
Manage DNS in Red Hat OpenShift Container Platform15 questions
This domain covers name resolution in the cluster. Candidates forward custom domains through the DNS operator, check CoreDNS, and test lookups from inside pods.
Skills tested
- Add a server to dns.operator/default that forwards one zone to upstream resolvers.
- Check the CoreDNS pods in the openshift-dns namespace and the dns-default ConfigMap.
- Test a service.namespace.svc.cluster.local lookup from inside a pod.
- Find why a lookup fails for an internal service or for an external domain.
Questions by topic
- Configure DNS forwarding for custom domains using the DNS operator3
- Verify CoreDNS pod health and configuration3
- Troubleshoot DNS resolution failures for internal services and external domains5
- Test name resolution from within pods (service.namespace.svc.cluster.local)4
Manage ingress traffic in Red Hat OpenShift Container Platform12 questions
This domain handles traffic that enters the cluster. Candidates give LoadBalancer services addresses from MetalLB, protect routes with TLS, and split routes across several ingress controllers.
Skills tested
- Create an IPAddressPool and an L2Advertisement so that a Service type LoadBalancer gets an address.
- Choose edge, re-encrypt or passthrough termination for a secure route.
- Shard routes across IngressController resources with a routeSelector and route labels.
Questions by topic
- Expose applications using MetalLB LoadBalancer services with IP address pools4
- Create secure routes with TLS termination (edge, re-encrypt, passthrough)5
- Configure ingress controller sharding using route selectors and labels3
Manage egress traffic in Red Hat OpenShift Container Platform16 questions
This domain controls traffic that leaves the cluster. Candidates write per-namespace firewall rules for outbound connections, and give namespaces a fixed source IP address that keeps working when a node fails.
Skills tested
- Write an EgressFirewall named default whose Allow and Deny rules come in the right order.
- Match destinations by cidrSelector or by dnsName.
- Assign an EgressIP to a namespace, and label nodes k8s.ovn.org/egress-assignable for failover.
Questions by topic
- Create EgressFirewall resources to control outbound traffic from namespaces3
- Assign static source IP addresses to namespaces using EgressIP resources4
- Configure allow and deny rules using CIDR ranges and DNS names4
- Label nodes as egress-assignable for EgressIP failover5
Implement native BGP routing in Red Hat OpenShift Container Platform16 questions
With native BGP routing, the cluster exchanges routes with routers outside it. Candidates define peering sessions, confirm that they are established, and advertise pod and service prefixes to the external peers.
Skills tested
- Turn on the FRR provider through additionalRoutingCapabilities in the Cluster Network Operator.
- Write an FRRConfiguration with the ASN, the router ID and each BGP neighbor.
- Check that sessions are Established with vtysh show bgp summary, then inspect the routes received.
- Advertise pod network and EgressIP prefixes to peers with a RouteAdvertisements resource.
Questions by topic
- Create FRRConfiguration resources to define BGP peering sessions5
- Advertise service and pod network prefixes to external BGP peers5
- Configure BGP neighbors, ASN, and router IDs3
- Verify BGP session establishment and route exchange3
Configure node networking for provider integration16 questions
This domain sets up the network interfaces of the nodes themselves. Candidates use the Kubernetes NMState Operator to build bonds, VLAN sub-interfaces and Linux bridges, then connect virtual machines to provider networks through those bridges.
Skills tested
- Write a NodeNetworkConfigurationPolicy whose desiredState describes a bond, a VLAN or a Linux bridge.
- Apply the policy to chosen nodes with a nodeSelector.
- Read NodeNetworkState and NodeNetworkConfigurationEnactment to see what changed or failed.
- Attach a virtual machine to an NMState-managed bridge through a bridge CNI NetworkAttachmentDefinition.
Questions by topic
- Configure bonded interfaces, VLAN sub-interfaces, and Linux bridges on cluster nodes3
- Connect virtual machines to external provider networks using NetworkAttachmentDefinitions referencing NMState-managed bridges4
- Create NodeNetworkConfigurationPolicy resources to configure node interfaces5
- Apply node network configurations to specific nodes using node selectors4
Enable network observability32 questions
The domain with the most objectives turns traffic into flow records. Candidates configure and tune the FlowCollector and its eBPF agent, filter flows in the console, and create custom network metrics.
Skills tested
- Configure the FlowCollector named cluster, with its eBPF agent and Loki storage.
- Tune sampling, cache size, agent features and resource limits.
- Filter flows by namespace, pod, service or IP address in the network observability console plugin.
- Define a FlowMetric and confirm that the new metric appears in Prometheus.
- Troubleshoot an eBPF agent that collects no flows.
Questions by topic
- Configure FlowCollector resources for eBPF-based network flow collection4
- Tune FlowCollector parameters (sampling, cache size, features, resource limits)6
- Analyze traffic patterns using the network observability console plugin3
- Create custom network metrics and verify their availability in Prometheus3
- Manage network observability configuration5
- Capture and filter network flows by namespace, pod, service, or IP address5
- Troubleshoot flow collection and eBPF agent issues6
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: the Configuring and Managing Red Hat OpenShift Networking (DO282) course, or the same experience.
- Recommended: the cluster administration skills taught in Red Hat OpenShift Administration II (DO280), which DO282 lists as its prerequisite.
About the EX282 exam
EX282 is Red Hat's hands-on exam for the networking layer of Red Hat OpenShift Container Platform. Candidates plan, deploy and manage that layer on a live cluster, from secondary and user-defined networks to DNS, ingress, egress, BGP routing and node interfaces. Network observability has more objectives than any other domain. Passing earns the Red Hat Certified Specialist in OpenShift Networking certification, which counts toward Red Hat Certified Architect in OpenShift.
The Enable network observability domain also gets the most questions in the PlanetCert practice test, followed by core networking and user-defined networks. The real exam is scored on finished tasks, so the practice questions focus on why each setting works, while lab work builds speed at the command line. The explanations separate look-alike choices, such as edge and re-encrypt TLS termination. Study Mode suits the egress and BGP questions, where rule order and peer settings decide the answer. Brainy AI Assistant can explain a FlowCollector field, or why an EgressIP did not fail over to another node.
How to earn the certification
- Earns
- Red Hat Certified Specialist in OpenShift NetworkingSpecialist (Level 4)
Red Hat certifications stay current for three years. Holders renew by retaking the exam for their highest certification, earning another one at the same level, or moving up a level.
- Before
- EX280 Red Hat Certified System Administrator in OpenShift
Red Hat's OpenShift administrator exam. EX282 does not require it, but Red Hat Certified Architect in OpenShift does.
- EX280 Red Hat Certified System Administrator in OpenShift
- After
- EX380 Red Hat Certified Advanced System Administrator in OpenShift
The engineer-level OpenShift exam. Red Hat Certified Architect in OpenShift requires it and Red Hat Certified System Administrator in OpenShift, plus three specialist exams.
- EX380 Red Hat Certified Advanced System Administrator in OpenShift
How to prepare for EX282
- 1
Build a lab like the exam cluster
Use an OpenShift Container Platform cluster with MetalLB, Kubernetes NMState, Loki, Network observability and OpenShift Virtualization installed. The exam cluster comes with these operators, so practice can start from configuring them.
- 2
Write every resource by hand
Most tasks end in YAML: a NetworkAttachmentDefinition, a UserDefinedNetwork, an EgressFirewall, an FRRConfiguration or a NodeNetworkConfigurationPolicy. Write each one from the product documentation, then check its status with oc.
- 3
Spend the most time on flows
The Enable network observability domain has the most objectives. Deploy a FlowCollector, change its sampling and cache settings, filter flows in the console plugin, and add a FlowMetric that shows up in Prometheus.
- 4
Break the network, then repair it
Several objectives ask for troubleshooting. Misorder EgressFirewall rules, point DNS forwarding at an upstream that does not answer, or give a BGP neighbor the wrong ASN. Then trace each fault with oc and vtysh.
- 5
Check each domain with practice sets
Work through the EX282 practice test in Study Mode one domain at a time, then take a full run in Timed Mode. Repeat each missed task on the lab cluster, and ask Brainy AI Assistant why the right answer works.
Start a timed EX282run
Red Hat recommends Configuring and Managing Red Hat OpenShift Networking (DO282). That course lists Red Hat OpenShift Administration II: Configuring a Production Cluster (DO280) as its prerequisite.
Who EX282 is for
- Cluster network engineers who design and maintain networking on OpenShift Container Platform.
- Platform administrators who set isolation, ingress and egress policies in multi-tenant clusters.
- Site reliability engineers who troubleshoot connectivity and run network observability.
- Infrastructure architects who plan secondary networks, BGP routing and NMState node settings.
Typical job titles: OpenShift network engineer · Platform administrator · Site reliability engineer · Infrastructure architect · DevOps engineer
EX282 glossary
19 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Cluster Network Operator (CNO)
- The operator that deploys and manages the cluster network plugin. Its settings live in the network.operator.openshift.io object named cluster.
- ClusterUserDefinedNetwork
- A cluster-scoped resource that creates one user-defined network across the namespaces that a namespaceSelector picks.
- CoreDNS
- The DNS server that answers name lookups inside the cluster. The DNS Operator runs it in the openshift-dns namespace.
- eBPF agent
- The Network Observability component that captures network flow data on each node.
- EgressFirewall
- A per-namespace resource, always named default, that holds ordered Allow and Deny rules for outbound traffic.
- EgressIP
- A resource that gives traffic leaving chosen namespaces a fixed source IP address, hosted on an egress-assignable node.
- FlowCollector
- The cluster-wide resource, named cluster, that sets up the eBPF agent, flow processing, Loki storage and the console plugin.
- FlowMetric
- A resource that defines a custom Prometheus metric built from network flow data.
- FRRConfiguration
- A resource that defines BGP routers, with their ASN and router ID, and the neighbors that they peer with.
- ipvlan
- A CNI plugin that creates virtual interfaces which share the MAC address of the parent host interface.
- macvlan
- A CNI plugin that gives a pod a virtual interface with its own MAC address on a host interface.
- MetalLB
- An operator that assigns external addresses to LoadBalancer services on bare-metal clusters and announces them with Layer 2 or BGP.
- Multus CNI
- A CNI plugin that calls other plugins, so that a pod can join extra networks besides the default cluster network.
- NetworkAttachmentDefinition
- A namespaced resource that holds the CNI configuration for one secondary network.
- NodeNetworkConfigurationPolicy
- An NMState resource that describes the interfaces, such as bonds, VLANs and bridges, that matching nodes should have.
- OVN-Kubernetes
- The default network plugin in OpenShift Container Platform. It provides pod and service networking, egress features and user-defined networks.
- Passthrough termination
- A secure route type in which encrypted traffic goes straight to the pod, and the router does not end the TLS session.
- Re-encrypt termination
- A secure route type in which the router ends the client's TLS session and opens a new TLS connection to the pod.
- UserDefinedNetwork
- A namespace-scoped resource that creates an isolated Layer2 or Layer3 network for one namespace.