This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
RHCSA is a public Red Hat performance exam. This page is not that exam, not a question dump, and not an official Red Hat guide. There is no browser tool here. The pillar links the neighbouring calculators.
Practice is one change you can explain and roll back: a user, a permission, a service, a firewall rich rule you can say. Do not practice on production. Do not collect a dump. The proof is the rollback.
One skill. The next skill waits.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Pick one skill you can show on a lab.
- Write the proof and the rollback.
- Do not use a question dump.
- Do not touch production.
- Stop after that skill.
Mistakes that outlive the command
RHCSA Exam Study Guide goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A question dump.
- Production used as the lab.
- The page treated as the exam.
- A certification claimed from reading.
Decisions to write down
One decision for RHCSA Exam Study Guide: One skill. The lab can be rebuilt. This is not the exam. No dump was used. And the rollback is written.
Checks before you call it done
Confirm this before you call the change done: The skill is named. The lab is named. The rollback is written. No dump was used. And production was not changed. If one of those fails, stop.
# Not the exam. Not a question dump. Not an official guide.
# A lab you can rebuild.
# One skill, with a rollback.Before you leave the host
RHCSA Exam Study Guide ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
This guide does not name a browser tool. The pillar it belongs to links the calculators for the neighbouring work.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.