EX280 CLI vs GUI: What to Expect in the Red Hat OpenShift Exam

Objective

If you are preparing for the EX280 Red Hat Certified Specialist in OpenShift Administration exam, one question you are bound to ask is: Should I focus on the Command Line Interface (CLI) or the Graphical User Interface (GUI)? The EX280 is a performance-based exam designed to test your real-world skills in managing and administering OpenShift clusters. As containerization and Kubernetes continues to dominate DevOps workflows, OpenShift Red Hat's Kubernetes-based container platform has become a key technology in modern enterprise infrastructure.

Understanding the difference between using the CLI and GUI is not only important for exam success but also for becoming a successful OpenShift administrator. Let's explore exactly what you should expect and how to best prepare.

Understanding the EX280 Exam

The EX280, officially titled Red Hat Certified Specialist in OpenShift Administration, is a high-stakes, hands-on certification exam offered by Red Hat. It is designed for system administrators, DevOps professionals, and IT specialists who work with containerized applications and Kubernetes-based platforms in production environments. Unlike traditional exams that rely on multiple-choice questions, EX280 is a performance-based exam, which means that you will be tested in a real Red Hat OpenShift environment where tasks must be completed exactly as you would on the job. This makes the certification highly respected and valuable in the IT industry.

• Exam Format: Performance-based, not multiple-choice. You perform tasks in a live OpenShift environment.
• Duration: 3 hours.
• Environment: Typically based on Red Hat Enterprise Linux and an OpenShift cluster.
• Goal: To simulate real-world OpenShift administration tasks.

The key to success is familiarity and confidence in working within OpenShift's administrative tools. And that brings us to the central theme: CLI vs GUI.

CLI vs GUI – What is the Difference?

What is CLI (Command Line Interface)?

The Command Line Interface (CLI) is a text-based interface used to interact with software and operating systems by typing commands. In the context of OpenShift, tools like oc, kubectl, and podman are used to manage resources, deploy applications, and automate tasks. The CLI is favored for its speed, scripting capabilities, and precision.

What is GUI (Graphical User Interface)?

The Graphical User Interface (GUI) is a visual interface that allows users to interact with the system using graphical elements like buttons, menus, and dashboards. In OpenShift, the Web Console serves as the GUI, which enables users to monitor cluster resources, view application topologies, and perform basic administrative actions with minimal command-line knowledge.

While both the CLI and GUI provide access to OpenShift features, they are not equal in terms of power, speed, or practicality, especially in the context of the EX280 exam.

Comparison Table

CLI (Command Line Interface)

Tools:

• oc: OpenShift CLI tool used for managing cluster resources, projects, deployments, and application lifecycles. It wraps around Kubernetes with OpenShift-specific capabilities.
• kubectl: The native Kubernetes CLI used to interact directly with Kubernetes APIs. It is useful for general cluster interactions and when working with Kubernetes-native objects.
• podman: A daemonless container engine used to build, run, and manage containers on RHEL systems. It serves as a lightweight alternative to Docker and supports rootless containers.

Strengths: Complete control, automation, and scripting support. The CLI allows administrators to manage every aspect of the OpenShift cluster—from user permissions to storage—with precision. It supports scripting through shell scripts and pipelines, which enables users to automate repetitive tasks, deploy applications programmatically, and integrate OpenShift operations into CI/CD workflows. This makes the CLI an essential tool for system administrators who need both flexibility and efficiency.

When to use: Almost always, especially when deploying, troubleshooting, or configuring OpenShift components.

GUI (Web Console)

Strengths: Visual feedback, beginner-friendly. The GUI provides a user-friendly, graphical representation of OpenShift resources, making it easier to understand the state and health of the cluster at a glance. With interactive dashboards, drag-and-drop deployment views, and clickable menus, it helps new users grasp concepts without memorizing complex commands. It is ideal for visual learners and administrators transitioning from traditional IT environments into Kubernetes-based systems.

When to use: Monitoring deployments, visualizing network routes, and viewing pod logs.

In real-world scenarios, seasoned administrators tend to use the CLI because it provides unmatched speed and flexibility, especially when working on multiple objects or when automating tasks. The GUI is often reserved for quick inspections or when introducing new team members to the platform.

What Does the Exam Focus On?

The CLI is the primary focus of the EX280 exam.

Most tasks in the exam are expected to be completed using CLI tools like oc. Although the GUI is available in some exam environments, relying on it could cost you time and limit your ability to perform advanced configurations.

Sample CLI-Based Tasks You Must Master

• Project Management: Using oc new-project allows you to create isolated environments for applications, while oc get projects helps list and verify existing projects. Understanding how to create, switch, and manage projects is fundamental for organizing workloads and access control in OpenShift.
• Application Deployment: OpenShift supports deploying applications from templates, Git repositories, or container images using the oc new-app command. This task assesses your ability to package, deploy, and update applications efficiently, reflecting real-world CI/CD pipelines.
• Networking: oc expose and oc create service enable you to create routes and services that expose applications inside and outside the OpenShift cluster. This is essential to ensure applications are accessible and properly load-balanced.
• Storage Management: Configuring persistent volumes and claims ensures that stateful applications retain data even if a pod restarts. You will need to create persistent volume claims (PVCs), bind them to pods, and understand storage classes and dynamic provisioning.
• Configuration Management: OpenShift allows configuration separation via configmaps and secrets. You will be tested on your ability to create, manage, and mount these into applications securely and correctly.
• RBAC (Role-Based Access Control): The command oc adm policy is used to assign roles to users and service accounts. You must understand how to grant and revoke permissions and how access is controlled in a multi-user environment.
• Debugging & Logs: Tools like oc logs provide container logs, oc rsh lets you execute commands inside running pods, and oc describe gives detailed resource information. These tools are vital for troubleshooting, root-cause analysis, and system diagnostics.

Sample GUI-Based Tasks (if any)

• Viewing project and pod status: The GUI allows users to quickly assess the status of different projects and the health of individual pods through visual indicators like color-coded statuses and resource graphs. This is helpful for a high-level overview without needing to type oc get pods or similar commands.
• Visual confirmation of deployments or routes: In the web console, the topology view graphically displays running deployments, routes, and associated services. It allows admins to confirm if an application is correctly deployed and if its network path is properly exposed to users.
• Accessing the web terminal: OpenShift provides a built-in web terminal within the GUI, which gives access to a shell session on a selected pod. Though slower and less flexible than native terminal access, it is a convenient feature for occasional checks or quick command execution.
• Viewing logs in a graphical format: The GUI offers a streamlined way to view real-time pod logs through its interface. This can be useful when you want to follow logs without opening a separate terminal, especially for those who prefer GUI-based monitoring or during training sessions.

Even in GUI-allowed cases, the CLI offers faster, more precise results. For example, oc get all -n myproject provides an instant overview of your project resources, something that takes longer to navigate visually in the GUI.

How to Prepare: CLI vs GUI Skills

To be well-prepared for the EX280, follow the 80/20 rule: spend 80–90% of your practice time mastering the CLI and 10–20% familiarizing yourself with the GUI layout and basic navigation.

CLI Preparation Tips

• Learn oc thoroughly. Know how to use flags like --output, --selector, and --namespace.
• Practice on CLI-only labs such as:
  • Red Hat Learning Subscription labs
  • Katacoda OpenShift scenarios
  • Minishift or CodeReady Containers (CRC) local environments
• Use --help and man pages frequently to get familiar with command options.
• Automate repetitive tasks and explore scripting opportunities using bash and oc.

GUI Preparation Tips

• Learn how to:
  • Navigate between projects
  • View pod logs
  • Access the developer and admin consoles
  • Use the topology view to confirm deployments visually

Preparation Strategy Table

But remember: Never depend on the GUI to complete critical tasks. It should be a fallback or verification tool, not your main interface during the exam.

Tips for the Exam Day

• Master --help and man pages: These are your best friends during the exam. You are not expected to memorize every flag or option, but you must be able to find the correct syntax quickly. Knowing these built-in tools saves time and prevents costly errors.
• Use tab completion: This feature not only speeds up typing but also helps you discover available commands, arguments, and file paths. It reduces syntax errors and helps ensure accuracy under pressure.
• Document everything: Keep a terminal history or notepad open to jot down commands you use. This helps in retracing your steps and debugging issues if something goes wrong. It is also useful for double-checking task completion.
• Verify your work often: Use commands like oc get all, oc describe <resource>, and oc get events to confirm the state and behavior of your configurations. Frequent verification ensures you catch and fix problems before moving on.
• Skip the GUI for complex tasks: The GUI is slower to navigate and may not support every function required during the exam. For time-sensitive tasks, always prefer the CLI to stay in control and maximize efficiency.
• Don't panic: If you hit a roadblock, don't get stuck. Move on to the next task and revisit the problem later. Keeping calm and managing time wisely is just as important as technical knowledge.

Conclusion

The EX280 is designed to reflect real-world OpenShift administration, and in the real world, the CLI is king. The exam environment and structure heavily favor candidates who are proficient with the oc tool and know how to operate without relying on visual guidance. The GUI may assist with quick overviews and verifications, but your primary focus should be on mastering the CLI.