Red Hat Certified Specialist in Containers Exam (EX188) Mock Test

Overview of the Red Hat EX188 Certification

The Red Hat Certified Specialist in Containers exam (EX188) validates an IT professional's ability to implement container technologies using Podman, Buildah, and Skopeo on Red Hat Enterprise Linux (RHEL). As containerised architectures become standard across modern UK cloud and enterprise infrastructure, foundational mastery of container deployment and operational workflows is critical for developers, systems administrators, and DevOps engineers alike.

Unlike traditional entry-level certifications that rely on multiple-choice assessments, the EX188 is an entirely performance-based, hands-on practical examination. Candidates are provided with one or more live RHEL environments and are tasked with completing real-world scenarios. Achieving this credential demonstrates that you possess the skills necessary to work with containers without relying on heavy orchestration engines like Kubernetes or OpenShift, serving as both a standalone qualification and a key stepping stone toward advanced cloud certifications.

Official Syllabus and Core Competencies

The EX188 exam evaluates practical competency across eight core functional domains:

1. Understand Container Architecture

Candidates must understand the distinction between traditional virtual machines and OCI-compliant application containers. This includes knowing how Linux namespaces, cgroups, and rootless containers isolate workloads while sharing the underlying Linux kernel.

2. Image Discovery and Registry Management

You must demonstrate how to locate container images across local and remote registries using commands like podman search and skopeo inspect. Candidates are expected to authenticate with private registries, pull images, tag images locally, and push updated layers securely.

3. Container Creation and Image Customisation

Building container images using Containerfiles (or Dockerfiles) is a core exam deliverable. Candidates must know how to specify base images (FROM), define execution parameters (CMD, ENTRYPOINT), copy files (COPY, ADD), establish environment variables (ENV), configure working directories (WORKDIR), and expose container ports (EXPOSE).

4. Container Lifecycle and Process Management

Tasks require launching, inspecting, halting, attaching to, and removing containers using the Podman CLI. You must be able to run background daemons (-d), inspect real-time log outputs (podman logs), and execute troubleshooting commands inside running containers (podman exec).

5. Persistent Storage and Volume Mounting

Containers are ephemeral by default. Candidates must configure persistent volumes using host directories and dedicated Podman volumes, paying close attention to SELinux container labels (:Z and :z flags) to ensure seamless storage access without compromising host security policies.

6. Container Networking and Host Integration

You will be assessed on exposing container applications to external networks. This involves publishing specific ports (-p), mapping container ports to host listening sockets, and diagnosing port conflicts.

7. Multi-Container Applications and Podman Pods

Candidates are tasked with grouping interdependent containers into local pods to share network namespaces, localhost routing, and shared storage mounts, replicating Kubernetes pod design patterns locally on a RHEL node.

8. Systemd Integration and Auto-Restart

A key enterprise requirement is ensuring containers automatically start when the system boots. Candidates must generate systemd unit files using podman generate systemd (or Quadlet specifications) and enable persistent user services using loginctl enable-linger.

UK Testing Options and Examination Rules

In the United Kingdom, candidates can undertake the EX188 exam through two primary delivery formats:

• Individual Remote Exams: Taken from home or the workplace using Red Hat's secure live-boot environment on an approved x86_64 PC or laptop. Candidates are monitored remotely via webcam and microphone by an external Red Hat proctor.
• Onsite Testing Stations: Available at designated Red Hat partner training facilities across major UK metropolitan centres, including London, Manchester, and Reading.

Strict Examination Rules

• You must present a valid, government-issued photo ID (such as a valid UK Driving Licence or UK/EU Passport).
• The testing room must remain completely private, well-lit, and free of extraneous clutter, secondary monitors, smartwatches, or phones.
• No external documentation, cheat sheets, or personal notes are allowed. All permissible reference material is contained strictly within the provided Linux environment (man pages and installed package documentation).
• Internet access outside the proctored virtual environment is completely restricted.

Scoring System and Performance Evaluation

Red Hat performance exams are scored out of 300 points, with a passing benchmark set at 210 points (70%).

Scores are determined entirely through automated evaluation scripts that execute after your test session concludes. The grading scripts test whether your deliverables function as requested—evaluating whether containers are actively running, whether correct ports are responding, whether storage persistence survives a reboot, and whether systemd units start cleanly. No partial credit is awarded for theoretical understanding or half-finished commands that do not produce the desired state.

Official exam results are emailed directly to candidates by Red Hat Certification Central within three UK business days.

Essential Preparation and Practical Study Tips

1. Build Muscle Memory in the Terminal: Do not rely on web search engines during your prep. Practise using podman --help and manual pages (man podman-run, man Containerfile) so you can quickly resolve syntax questions under timed conditions.
2. Master SELinux Flags: Failing to append :Z to volume mounts is one of the most common reasons container tests fail. Ensure you understand how targeted SELinux policies interact with rootless Podman.
3. Always Test Reboots: Before concluding your session, reboot your lab instance and verify that all required containers, pods, and systemd units recover automatically without manual intervention.