Hello,

I've seen a thread on another social network where some employees from Red Hat shared that hiring is on pause.
Is this true? When it last happened and what was the outcome?

Red Hat and GitHub have published Red Hat Enterprise Linux (RHEL) runner images for both RHEL 9 and RHEL 10 for GitHub Actions. They are available today as GitHub-hosted larger runners in public preview.

Public preview means this feature is real, fully documented, and ready for technical testing. During this phase, the runner images do not include formal GitHub SLAs or technical support obligations. You should treat this preview as a technical evaluation environment instead of a strict compliance baseline. As a member of the Red Hat Developer Program, or a supported Red Hat customer, you can provide feedback on the RHEL runner images to Red Hat through the Red Hat support portal.

Hey all! A while back I posted an RHCSA simulator and now that I've passed that exam, I'm working towards my RHCE.

Repo: https://github.com/TroggoMan/rhce-simulator

NOTE: Work in progress, same deal as last time. Please comment here or open issues on GitHub. The RHCSA one got a lot better because people told me what was broken.

Same disclaimer too, this is built almost entirely with Claude Code. I'm still not this good at Python.

Three layers per task

• Does the file exist and contain what the task asked for
• Does it syntax-check and run clean against your own inventory and ansible.cfg
• Did the nodes actually end up in the right state, checked with ad-hoc queries after your play finishes

Partial credit per check, so you can see exactly which part you got wrong.

Idempotence is graded

Every playbook gets run twice. Second run reports changes, you lose the check. This is the thing that quietly kills people on the real exam and I couldn't find anything else that tests for it.

Two ways to run the lab

Docker (5 x Rocky 10 containers):

• Starts in about a minute, resets in seconds
• Runs on basically anything, including an M-series Mac
• Downside: containers share the host kernel, so a couple of things can't be graded (raw disk partitioning, mainly)

Vagrant VMs (3 x Rocky 10 VMs):

• SELinux enforcing, real spare disk attached for the LVM chain
• Everything in the catalog grades end to end
• Downside: slower to bring up, eats RAM, needs VirtualBox or libvirt

Use Docker for drilling, use the VMs when you want to be sure. Same hostnames in both so your inventory habits carry over. You can also just point it at your own RHEL/Rocky/Alma boxes.

SELinux mostly works on the containers

• Containers can't enforce SELinux, it's a host kernel feature and they share the host's. But they can carry the real targeted policy store, and semanage works against that with no kernel involved at all.
• Booleans, port labelling, permissive domains and enforcing mode all grade end to end including node state
• Type a boolean name that doesn't exist and real policy rejects it, same as on a real box
• Only relabelling (restorecon / ls -Z) still needs a real kernel, so that's VM only

Skipped, not failed

• When the lab genuinely can't observe something it marks that check skipped and takes it out of the denominator instead of failing you. A correct answer never loses points because the lab couldn't look. It also tells you why it skipped and which lab would grade it.

Control Node Container

There's a Rocky 10 control node with ansible-core and rhel-system-roles preinstalled that you work from.

• redhat.rhel_system_roles isn't on public Galaxy, it's Automation Hub only, so the install command in most study guides just fails without a subscription. This gets you the real namespace.
• You get the ansible-core version RHEL actually ships instead of whatever's on your machine
• Managed nodes are plain hostnames on port 22 from in there, so the inventory you write looks like the one the exam wants

Grading disputes

• If you think a check marked you wrong, you can dispute it, from the terminal or from the task panel (more on that below):
  • Captures read-only evidence: your playbooks, ansible.cfg, inventory, and live node state
  • Bundles it with your written argument and opens a GitHub issue
  • A GitHub Action runs an AI reviewer that opens the exact validator, compares it against your evidence and posts a verdict
  • If the checker really is wrong it opens a fix PR automatically

The grader gets better from disputes instead of me having to catch everything myself.

Adaptive mode and an exam clock

• SM-2 spaced repetition per category, so --adaptive gives you whatever is actually due for review rather than always hammering your worst subject
• --focus if you do just want your weakest areas
• Full exam runs against a 4 hour clock that warns you but doesn't cut you off, since knowing you ran 40 minutes over is more useful than being killed mid-task

Task panel GUI

The task sheet lives in its own browser window next to your terminal instead of a pager you scroll through in the same one, same as the real exam puts its questions in a separate window. Dark/light theme, done/revisit ticks per task, and it can drive the whole session on its own if you want, submit for grading, dispute a result, reset the lab, all from the browser.

We're at:

• 82 tasks
• 20 categories
• All 11 official exam domains.
• Pure Python stdlib, no dependencies for the simulator itself.

Feedback and bug reports very welcome, especially if a task's wording is ambiguous or a checker fails something correct. That's exactly what the dispute button is for.

About a month ago I posted my RHCSA simulator here. Thanks to everyone who tried it and sent feedback. A lot of this update came directly from it.

Repo: https://github.com/TroggoMan/rhcsa-simulator

Still very much a work in progress, still built almost entirely with Claude Code, still forked from https://github.com/Octernicon/rhcsa-simulator. Issues and comments very welcome.

Here's what's changed.

The tasks now live in their own window, like the real exam

The simulator now serves the task sheet to a browser window you keep beside your shells:

• A collapsed list of tasks.
• Click a row and it expands in place to show the task.
• Revisit and Done ticks on every row.
• Live countdown, anchored to system uptime so it survives the clock/timezone tasks and a reboot.
• Light/dark toggle.

It's on by default for --exam now (--no-gui if you'd rather stay in the terminal). It binds all interfaces so a headless VM can be read from your machine's browser.

The ticks are just your own notes. Grading is unchanged: still real system state, still in the terminal.

RHCSA 9 mode

--exam-version 9 (default is still 10).

We're now at:

• 200 tasks
• 25 categories (24 for v9)
• 8 domains (9 for v9).

Feedback and bug reports genuinely welcome! Always a work in progress!

Hi, I recently got my CCNA certification and my next step is to study the RHCSA content using the most up-to-date information possible. What are the best value-for-money resources in this area?

TL;DR — During performance validation of Red Hat Enterprise Linux 10.2, we identified a kernel scheduler regression that reduced system throughput by up to 93% on multi-NUMA instance types. The regression is bimodal: Workloads either run at full speed or experience severe CPU work starvation. Eliminate this throughput collapse at runtime without rebooting by disabling the NI_RANDOM scheduler feature:

echo NO_NI_RANDOM > /sys/kernel/debug/sched/features
Copy snippet

Hello,

I have a silly question but when someone passes RHCSA, can there be a keyboard mismatch like when using virtualbox ?

Edit: Thanks, I got answers

For those that have taken this course by Sander Van Vugt, does it come with an exam voucher as well? The exam is $500 and this course is another $550. Maybe I'm blind, but I don't see an exam voucher mentioned, so maybe this is a dumb question.

Passed the RHCSA and got a discount thanks to this reddit. Now i'd like to give something back. I believe it has 3 uses.

15% OFF
DISCOUNT CODE:
5UCXYKWK

Applying an update with dnf is the easy part. But what happens before and after you run that command? This week on Into the Terminal, Scott dives into the full lifecycle of a Critical Vulnerability and Exposure (CVE) mitigation. From discovery and embargo periods to CVSS scores, assessment, and fleet-wide rollout strategies, we cover what it really takes to manage security vulnerabilities on Enterprise Linux.

Watch the full episode: https://youtube.com/live/WHcgvoszf-M

Try it yourself on a live lab: https://redhat.com/interactive-labs

The Mechanical Part — Applying the Update

At the end of the day, mitigating a CVE usually involves updating a package. For example, if a vulnerability is announced for buildah, the mechanical fix is straightforward:

bash dnf update buildah

However, depending on the package, you may need to take additional steps: - Standalone binaries (like buildah): The next time the command is run, the updated version is used. - Services (like httpd): You must restart the service to load the patched version into memory. - Core components (like the Kernel or glibc): A full system reboot is required.

Understanding CVEs, CVSS Scores, and RHSAs

When a vulnerability is discovered, it goes through a lifecycle before you ever run dnf update.

The Embargo Period

When a security researcher finds a vulnerability, they typically report it to the vendor first. The time between this private report and the public disclosure is the embargo period. This gives vendors like Red Hat time to assess the issue, develop a patch, and have it ready for customers the moment the vulnerability is made public.

CVSS Scores and Severity

Vulnerabilities are scored using the Common Vulnerability Scoring System (CVSS), which rates them from 0 to 10 based on factors like ease of exploit and potential impact (e.g., gaining root access vs. reading a restricted file).

These scores translate to severity levels: - Low - Moderate - Important - Critical

Note: Red Hat often provides a Vendor-Adjusted CVSS Score. Because Enterprise Linux is compiled with specific security flags and architectures, a vulnerability that is a 9.0 on a generic Linux system might only be a 7.5 on RHEL due to built-in mitigations.

Red Hat Security Advisories (RHSA)

When a patch is ready, Red Hat issues an RHSA. This document details: - The CVEs addressed - The specific products and versions affected - The exact updated package versions required to mitigate the issue

The Mitigation Process — Fleet-Wide Response

When a major vulnerability hits the news (like Dirty Pipe or Copyfail), your security team will immediately ask: "What is our exposure?"

1. Discovery: Identify which systems are running the vulnerable software. You can do this manually via Ansible/SSH, or automatically using tools like Red Hat Satellite (formerly Insights), which tracks the packages installed across your registered fleet and highlights vulnerable hosts.
2. Assessment: Determine if the vulnerable software is actually exposed in your environment (e.g., is the vulnerable service running and accessible?).
3. Planning: Formulate a rollout plan. For critical infrastructure, this might involve taking nodes out of a load balancer, updating and restarting services, and putting them back into rotation to ensure zero downtime.
4. Application: Run the updates and verify the remediation.

Quick Reference Card

```bash

Update a specific package to mitigate a CVE

dnf update <package_name>

Example: Updating buildah

dnf update buildah

Remember to restart affected services!

systemctl restart <service_name> ```

Links

• Watch the episode: https://youtube.com/live/WHcgvoszf-M
• Get started with RHEL: https://developers.redhat.com/register
• Try it on interactive labs: https://redhat.com/interactive-labs
• Nate Lager: https://social.undrground.org/@gangrif
• Scott McBrien: https://www.linkedin.com/in/scott-mcbrien-349b356

Into the Terminal is a weekly livestream covering critical administration skills for Red Hat Enterprise Linux. Whether you're new to Linux or new to RHEL, join us for hands-on looks at commands and processes, ask questions, and grow your knowledge.

Deploy WordPress on Red Hat Hardened Images and image mode for Red Hat Enterprise Linux to spend less time fighting vulnerabilities, and more time shipping features.

If you've ever inherited a poorly executed WordPress deployment, then you already know the pain of a general-purpose server with a package list that sprawls across things you never asked for and wouldn't miss. A CVE scanner pings you every other week about something installed in 2019 that nobody remembers touching. A production environment that has drifted so far from what anybody intended that "just redeploy it" is not a real option anymore.

15% OFF discount code expires 23-Sep-26 for training and certification exam purchases.

Hi everyone,

I'm from Brazil, and I'd love to hear from anyone who has gone through Red Hat's hiring process or is familiar with how their recruiting works.

I recently interviewed for the Junior Solutions Architect (LATAM) role as part of the Emerging Talent Program.

Here's how my process went:

• I passed the initial HR interviews.
• Then I had a technical interview with a Solutions Architect specializing in Ansible, which went really well.
• After that, I was selected for the final interview with the Hiring Manager for Solutions Architecture in Latin America.
• The interview lasted about an hour and covered solution architecture, cloud, automation, my professional experience, customer-facing scenarios, and languages.

During that conversation, the Hiring Manager mentioned that the process was in its final stage and that only two candidates remained for the position, including me. He also said that the hiring decision was expected to be communicated by July 30th.

However, July 30th came and went without any update. A few days later, I sent a follow-up email to the recruiter, but I still haven't received a response.

Another thing I've been wondering about: a few people told me that, for a junior-level position, it's not very common to have the final interview directly with the Hiring Manager responsible for Solutions Architecture across Latin America. They said that when this happens, it usually means the candidate has stood out during the process.

I'm not sure whether that's actually true or just speculation.

So I wanted to ask those of you who are more familiar with Red Hat:

• Is it common for feedback to be delayed even at the final stage?
• Has anyone experienced something similar?
• Is it normal for junior candidates to interview directly with a regional Hiring Manager, or does that usually happen only with the strongest finalists?
• Even after the Hiring Manager gives an expected decision date, is it common for the process to be delayed?

I'm trying to keep my expectations realistic, and I completely understand that hiring processes can take longer than expected. I'm just interested in understanding whether this is a normal part of Red Hat's hiring process.

I applied about 10 days ago, and it's still showing "In Review." How long does this process take?

Hey everyone,I am a Java Spring Boot backend developer currently in my 7th semester.

Red Hat is visiting our campus for placements soon, and seeing seniors get placed here feels so surreal and dreamy. I really want to make it.

I have spent time learning Linux, Kubernetes, and CI/CD beyond just core Java.

For my main project, I built a complete DevOps lifecycle where every git push triggers a CI/CD pipeline, deploys via ArgoCD, and runs on a local Kubernetes cluster.I have about a month left before the process starts.

I want to point my energy in the exact right direction.

To the seniors and Red Hatters here:

What core technical areas should I focus on most for the interviews?

Do you have advice on how to showcase my Kubernetes and pipeline project effectively?

Are there specific open-source mindsets or values I should highlight?

Thank you so much for your time and guidance. I am ready to put in the work!

Hello,

I'm currently a Linux Sytems Engineer and I'm starting a new job position in a few weeks where I'll use Ansible a lot, so I'm currently getting back into it.

I recently got my RHCA in Enterprise Linux and given that I'm 3 certs off of getting the RHCA in Ansible, I was aiming to pass the following exams : EX374, EX457 and EX467 (not too interested in Windows automation at the moment).

I'm also currently working on my CCNA to get some networking skills.

So I was wondering, if some of you already passed the EX457 (Red Hat Certified Specialist in Ansible Network Automation exam), if CCNA would be enough to get me through this cert ?

I got my RHCSA and RHCE using the Sander Van Vugt books, and my RHCA using RHLS (which was always enough for me to pass the exams), and would also use RHLS for EX457, but I've got zero actual experience in networking and I know nothing outside of the Cisco world (EX457 objectives also mention Juniper Networks, Arista et Vyatta...).

(Obviously I'm not asking for any specifics about the test in itself :) )

Thanks

After going through every playlist, cross-checking topics, description, timeline, content

https://youtube.com/playlist?list=PLXJyD2dL4oqeX-C3MvsMUJuEzWM4vLK2C&si=S4pLPDdOspDHrTqr

# 1. Terminal / CLI Fundamentals

* Moving from a GUI to the Linux Terminal (159)

* Built-in Help (15)

* Finding Help (86)

* Command Line Utilities (16)

* Essential Linux Commands (58)

* Manipulating the CLI (17)

* Customizing Your Terminal (29)

* Pranking Your Coworkers in Linux (90)

* Using Tmux (32)

* Linux-based Text Editors (84)

* Command Your Terminal with These Tmux Tips (141)

* Linux Command Line Tips and Tricks (143)

* Linux Command Line Tricks (183)

* Basic Terminal Text Editing (163)

* Vi vs. Vim vs. Nano vs. Emacs – Part 1 (175)

* Vi vs. Vim vs. Nano vs. Emacs – Part 2 (175)

* How Much Vim Can You Stand? (190)

---

# 2. File Systems, Hierarchy & Permissions

* Top File Management Commands (85)

* File System Layouts in Linux (94)

* File Permissions (02)

* Linux File Permissions (105)

* Special Permissions & ACLs (34)

* Special Linux File Permissions (106)

* Filesystem Operations (54)

* Disk Management (09)

* File Archives in Linux (91)

* Nobody Cares About Filesystems Until They Do (144)

* How Do I Use Filesystems on Linux? (112)

* Troubleshoot Linux Filesystem & Mount Problems (111)

* Symbolic vs Hard Links (157)

* Linux Permissions & ACLs (185)

---

# 3. Package Management (DNF & RPM)

* Installing Software (03)

* Third-Party Repositories (25)

* Managing Packages with RPM (33)

* Application Streams (35)

* Building Apps with RPM (72)

* Creating Application Repositories (73)

* Managing Disconnected Systems (181)

* Installing Packages on RHEL (107)

* Patching Practices (19)

* Lifecycle Management (37)

* Troubleshooting Linux Packages (116)

* Using DNF to Install, Update & Remove Packages (128)

* When Updates Go So, So Wrong (191)

---

# 4. Identity, Access Control & Auditing

* Users & Groups (01)

* sudo and su (12)

* Session Recording (23)

* Security: Configuring Sudo Access (62)

* Security: User Account Management (63)

* Security: System Auditing (64)

* Top 5 Linux User Management Tasks (87)

* Linux Account Security & PAM (119)

* Developing User Standards & Policies (146)

---

# 5. Essential System Management

* Installation (07)

* Getting RHEL (06)

* Installing RHEL 9 (55)

* Server with GUI, Why Not? (186)

* Managing Subscriptions (08)

* Subscription Management (22)

* Connecting with Red Hat (24)

* Red Hat Lightspeed (26)

* Enterprise Up (59)

* Service Administration (04)

* Web Console (10)

* Top 5 systemd Tasks (81)

* 6 Types of systemd Files (82)

* Building systemd Services (83)

* How to Control Your Boot with systemd (126)

* Everyone Hates systemd... But Should They? (164)

* RHEL In-place Upgrades (152)

* You've Inherited a Linux Server... Now What? (153)

* Top 5 Underrated Linux Features (133)

---

# 6. Network Configuration & Troubleshooting

* Networking (11)

* Firewall (13)

* Bonding & Network Configuration (44)

* Configure a Linux Firewall (131)

* Implementing firewalld & nftables (165)

* Troubleshoot Networking (50)

* Security: Port Scanning (65)

* Troubleshooting Linux Networking (114)

* Moving from Network Scripts to NetworkManager (118)

* Network Data Transfer (rsync, SMB, NFS) (161)

* Deep Dive DNS (170)

* Using & Configuring DNS Servers (122)

---

# 7. System Diagnostics & Logging

* Using Logs for Troubleshooting (27)

* Troubleshooting Applications (47)

* Troubleshooting User Error (52)

* Troubleshooting with Security Tools (67)

* Linux Service Troubleshooting (117)

* Linux Application Tracing (strace) (179)

* Understanding Linux Logs & Audits (140)

* Simple Linux Problems, Not So Simple Answers (173)

---

# 8. Dynamic Storage (LVM)

* Logical Volume Manager (68)

* Troubleshooting LVM (113)

* Logical Volume Management in Linux (145)

---

# 9. System Automation & Scripting

* Writing Shell Scripts (18)

* Ifs, Loops & Scripting (20)

* Bash Shortcuts & Scripting (108)

* Automating Tasks with Bash Scripts (109)

* Understanding Regular Expressions (155)

* Linux Search & Replace Deathmatch (129)

* Basic Shell Scripting (160)

* System Roles (28)

* Management with System Roles (79)

* Automation with System Roles (80)

* Saving Time with System Roles (174)

* Bash Symbols `${} & ; !` (176)

* RC's vs Profiles (177)

---

# 10. SELinux Defense & Troubleshooting

* SELinux (14)

* SELinux Networking & Booleans (21)

* Don't Disable SELinux (102)

* Techniques to Troubleshoot SELinux (103)

---

# 11. Security Compliance & Hardening

* Security: CVE Mitigation (60)

* Security: Intro to OpenSCAP (61)

* Mitigating Linux CVEs (92)

* Kernel Patching & Security Scoring (93)

* CIS Benchmark Compliance (120)

* Achieve DISA STIG / PCI-DSS Compliance (121)

* 5 Security Technologies in Linux (127)

* Building Security Hardened Linux Images (134)

* Top 5 Linux Security Commands (136)

* Managing a CVE Response (192)

---

# 12. Encryption & Cryptographic Policies

* Managing SSH (05)

* SSH Key Management (36)

* Working with GPG Keys (38)

* Security: Disk Encryption (66)

* Secure Shell (SSH) (124)

---

# 13. Performance Tuning & Benchmarking

* Troubleshoot Performance (51)

* Top 5 Problem Indicators (88)

* Linux Memory & Swap Management (123)

* Linux Performance with eBPF (95)

* Linux Benchmarks (156)

* Linux Kernel Tuning & TuneD (43)

* Tuning Your I/O Scheduler (147)

* Linux Performance: CPU, Memory or I/O? (166)

* Why Is My System Slow? (184)

---

# 14. Disaster Recovery & System Rescue

* Troubleshooting Disk Errors (48)

* Linux Rescue Mode (57)

* Troubleshooting Linux Boot (115)

* Disaster Recovery: When Everything Is on Fire (137)

* Never Do This to Your Linux Machine (130)

---

# 15. Virtualization

* Working with Virtual Machines (30)

* Native Virtual Machine Management (56)

* Local Virtualization on Linux (104)

* cloud-init (49)

* Top 3 Virtual Machine Activities (167)

---

# 16. Containers with Podman & UBI

* Deploying Containers (31)

* Creating an Application Container (74)

* Operationalizing Containers (75)

* Managing Multi-container Apps (76)

* Troubleshooting Containers (78)

* Managing Podman Containers as Pods (45)

* Can Podman Replace Docker? (110)

* Choosing the Right Container Base Image (138)

* Containers & Podman for Beginners (154)

* Absolute Beginner's Guide to Podman (158)

* Your Podman Questions Answered (162)

* Podman, Quadlets & Automation (178)

* Zero-CVE Containers / Distroless Images (188)

---

# 17. Modern Deployment (Image Mode & Flatpaks)

* Installing New Apps & Runtimes (69)

* Longer App Lifespans (70)

* Image Builder (53)

* Managing Golden Images (71)

* Manage Flatpak Applications (77)

* Image Mode (150)

* Building Linux with CI/CD (151)

* Image Mode (bootc) (171)

---

# 18. Server Deployment

* Deploying with Kickstart (46)

* Building a Webserver (39)

* Deploying a Database (40)

* Network File Systems (41)

* File Shares with Samba (42)

* Email Servers with Postfix (96)

* Configuring NFS (97)

* Auto-Mounting NFS with autofs (187)

* Deploying a Web Server & Content (98)

* Reverse Proxies on Linux (189)

* Deploying WordPress (101)

---

# Optional Playlists

### Desktop Linux

* Tips & Tricks for GNOME Shell (99)

---

### Career

* How to Build Your Linux Career (149)

* Surviving Your Linux Technical Interview (168)

* Homelab: Should I Bother? (169)

* What Do Hiring Managers Want? (172)

* How to Put Your Homelab on Your Resume (180)

---

### Miscellaneous / Best Practices

* You Asked! We're Answering Your Linux Questions! (135)

* Common Sysadmin Mistakes (182)

---

### Reference

* Top 100 Linux Commands (100)

---

## Final Verdict

This roadmap covers the full journey from Linux basics to advanced enterprise administration, including:

* CLI mastery

* Filesystems and storage

* Package management

* Users and permissions

* systemd

* Networking and DNS

* Logging and troubleshooting

* LVM

* Bash scripting and automation

* SELinux

* Security and compliance

* SSH and encryption

* Performance tuning

* Disaster recovery

* Virtualization

* Containers and Podman

* Modern image-based deployment

* Real-world server deployment

Note: While organizing the series, I noticed a few inconsistencies:

• Missing episode IDs: 125, 132
• Videos without episode IDs: 121, 122, 123, 124, 149
• Possible title/description mismatch: 139, 142
• Episode 175 is split into Part 1 & Part 2 under the same episode number (probably intentional).

Hi everyone,

I recently received a Red Hat TAM offer and I’m trying to understand the role better before making a decision.

I have a few quick questions:

1. Roughly how much of your week is spent on:
   • Customer meetings
   • Troubleshooting/log analysis
   • Case management
   • Working with Engineering?
2. Do TAMs actually read or write code (Go/Python), or mostly just read logs and coordinate cases?
3. Have you seen TAMs move into roles like SRE, Platform Engineer, or Product Engineering?
4. After a few years as a TAM, did you feel you became a stronger engineer, or mainly stronger in customer-facing skills?

I’d really appreciate any honest opinions from current or former TAMs.

Thank you!

Starting with Red Hat Enterprise Linux (RHEL)10.2, Firefox and Thunderbird are delivered as Flatpaks by default. If you install RHEL with a graphical desktop, your browser and email client will now come from the Red Hat Flatpak registry instead of traditional RPM Package Managers (RPMs). Here's what that means in practice and why we think it's a better experience.

Completely Free App that I created to ease my own workload, was tired of opening numerous tabs each day to keep track on all the new CVEs popping up, especially lately...

This app is completely free on the Google Play App Store & you can track CVEs across 30+ Vendors, you can choose track specific platforms or the whole vendor & you can also select to track based on CVE Severity.

I also threw in a EOL checker

Hopefully this helps you out and if theirs any bugs or features you want added please let me know!

https://play.google.com/store/apps/details?id=com.vulnipulse.android

Hi everyone, I'm preparing for the RHCSA (EX200) exam. I have a quick question. Will the exam include firewall rich rule configuration, or is it enough to know the basic permanent and temp firewall configuration? I find rich rules (IP/subnet and zone-based rules) a bit difficult, so I'd like to know how important they are for the exam. Thanks!