Study guide
6.1 Configure Access to RPM Repositories
Red Hat Certified System Administrator RHCSA
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Lab Setup & Performance-Based Study Strategy
2 Essential Tools: Shell, Redirection & Text Analysis
2.1 Shell Prompt and Command Syntax 2.2 Input-Output Redirection and Pipes 2.3 grep and Regular Expressions for Text Analysis
3 Essential Tools: Remote Access, Users & Text Editing
3.1 Access Remote Systems Using SSH 3.2 Log In and Switch Users in Multiuser Targets 3.3 Create and Edit Text Files
4 Essential Tools: Files, Links & Archives
4.1 Create, Delete, Copy, and Move Files and Directories 4.2 Hard and Soft Links 4.3 Archive and Compress with tar, gzip, and bzip2
5 Essential Tools: Permissions & System Documentation
5.1 List, Set, and Change Standard ugo/rwx Permissions 5.2 System Documentation: man, info, and /usr/share/doc
6 Manage Software: RPM and Flatpak
6.1 Configure Access to RPM Repositories 6.2 Install and Remove RPM Software Packages 6.3 Configure Access to Flatpak Repositories 6.4 Install and Remove Flatpak Software Packages
7 Create Simple Shell Scripts
7.1 Conditional Execution: if, test, and [] 7.2 Looping Constructs for Files and Input 7.3 Process Script Inputs ($1, $2, and Beyond) 7.4 Process Shell Command Output in Scripts
8 Operate Running Systems: Boot and Recovery
8.1 Boot, Reboot, and Shut Down a System Normally 8.2 Boot Systems into Different Targets Manually 8.3 Interrupt the Boot Process to Gain Access
9 Operate Running Systems: Processes and Tuning
9.1 Identify and Kill CPU/Memory Intensive Processes 9.2 Adjust Process Scheduling 9.3 Manage Tuning Profiles
10 Operate Running Systems: Logs, Services & File Transfer
10.1 Locate and Interpret System Log Files and Journals 10.2 Preserve System Journals 10.3 Start, Stop, and Check Status of Network Services 10.4 Securely Transfer Files Between Systems
11 Configure Local Storage: Partitions and LVM
11.1 List, Create, and Delete Partitions on GPT Disks 11.2 Create and Remove Physical Volumes 11.3 Assign Physical Volumes to Volume Groups 11.4 Create and Delete Logical Volumes
12 Configure Local Storage: Mounting and Expansion
12.1 Mount File Systems at Boot by UUID or Label 12.2 Add Partitions, Logical Volumes, and Swap Non-Destructively
13 Create and Configure File Systems: Local FS and Permissions
13.1 Create, Mount, and Use VFAT, ext4, and XFS File Systems 13.2 Extend Existing Logical Volumes 13.3 Diagnose and Correct File Permission Problems
14 Create and Configure File Systems: NFS and autofs
14.1 Mount and Unmount Network File Systems Using NFS 14.2 Configure autofs
15 Deploy and Maintain: Scheduling, Services & Targets
15.1 Schedule Tasks with at, cron, and systemd Timers 15.2 Start, Stop, and Enable Services at Boot 15.3 Configure Systems to Boot into a Specific Target
16 Deploy and Maintain: Time, Software Updates & Bootloader
16.1 Configure Time Service Clients 16.2 Install and Update Software from CDN, Remote Repos, and Local Files 16.3 Modify the System Bootloader
17 Manage Basic Networking
17.1 Configure IPv4 and IPv6 Addresses 17.2 Configure Hostname Resolution 17.3 Configure Network Services to Start Automatically at Boot 17.4 Restrict Network Access Using firewalld and firewall-cmd
18 Manage Users and Groups
18.1 Create, Delete, and Modify Local User Accounts 18.2 Change Passwords and Adjust Password Aging 18.3 Create, Delete, and Modify Local Groups and Memberships 18.4 Configure Privileged Access
19 Manage Security: Firewall, umask & SSH Keys
19.1 Configure Firewall Settings with firewall-cmd and firewalld 19.2 Manage Default File Permissions 19.3 Configure Key-Based Authentication for SSH
20 Manage Security: SELinux Modes and Contexts
20.1 Set Enforcing and Permissive Modes for SELinux 20.2 List and Identify SELinux File and Process Contexts 20.3 Restore Default File Contexts
21 Manage Security: SELinux Ports and Booleans
21.1 Manage SELinux Port Labels 21.2 Use Boolean Settings to Modify SELinux Settings
6.1 Configure Access to RPM Repositories
Key Takeaways Explain This Topic AI
DNF is the package manager on RHEL 10; repository definitions live as *.repo files under /etc/yum.repos.d/ (global options in /etc/dnf/dnf.conf).
A valid .repo stanza needs a unique [repo-id], name, and a baseurl or metalink/mirrorlist; enabled=1 and gpgcheck settings control use and trust.
Use dnf repolist, dnf config-manager, and dnf makecache to verify repositories before installing packages.
Local file://, HTTP/HTTPS, and CDN/subscription-backed repos all appear the same to DNF once .repo files are correct—exam tasks often add a custom or local repo.
Repository configuration is file-based and persists after reboot; a bad enabled/gpgcheck value fails later install tasks silently or loudly.
Last updated: August 2026
6.1 Configure Access to RPM Repositories
Quick Answer: On RHEL 10, define RPM package sources in /etc/yum.repos.d/*.repo (not hand-stacked only in memory). Each repo needs a unique [id] , name= , and baseurl= or metalink= / mirrorlist= , plus enabled= and GPG settings. Confirm with dnf repolist and dnf makecache . Configs on disk persist after reboot —required for EX200 credit.
Why repository access is its own exam skill
The official EX200 study points split Manage software into repository access and package install/remove for both RPM and Flatpak . Graders do not care that you memorized dnf install if the system has no usable repo . Typical tasks:
- Add a custom or local repository (directory tree with repodata/ )
- Point DNF at an HTTP/HTTPS mirror or training server
- Enable/disable an existing repo
- Fix a broken .repo so packages install again
If the repo is wrong, every later software task fails. Treat this section as the foundation for Section 6.2.
DNF vs yum naming (RHEL 10)
RHEL uses DNF as the package manager stack. The classic yum command remains a familiar front end on many systems (often a compatibility path to DNF). Prefer dnf in modern documentation and on the exam unless a task literally says yum .
Important paths still use the historical yum directory name:
Path Role
/etc/dnf/dnf.conf Global DNF configuration ( [main] ): cache, gpgcheck defaults, plugins, etc.
- /etc/yum.repos.d/ Directory of individual *.repo files— primary place to define repositories
- /var/cache/dnf/ Downloaded metadata and packages (cache)
Red Hat’s guidance: define repositories in .repo files under /etc/yum.repos.d/ , not by stuffing long-lived repo stanzas only into dnf.conf . Keep dnf.conf for global policy; keep repos modular and easy to enable/disable.
Anatomy of a .repo file
Files must end in .repo or DNF ignores them. One file may contain multiple repository sections. [exam-appstream]
- name=Exam AppStream mirror
- baseurl=https://repo.example.com/rhel10/AppStream/x86_64/os/
- enabled=1
- gpgcheck=1
- gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
- Directive Meaning
- [exam-appstream] Repository ID (unique). Used in dnf --enablerepo=exam-appstream and repolist
- name= Human-readable description
- baseurl= Direct URL or path to the repo root (must contain or resolve to repodata/ )
- metalink= / mirrorlist= Dynamic mirror selection instead of a single baseurl
- enabled=1 or 0 Whether DNF uses the repo by default
- gpgcheck=1 or 0 Verify package signatures when installing
- gpgkey= URL or file:// path to the public key
- module_hotfixes= / other options Advanced; only set when documentation or task requires
- Local file repository (common lab/exam pattern)
- If packages and metadata live on disk (ISO mount, NFS share, copied tree): [local-baseos]
- name=Local BaseOS
- baseurl=file:///mnt/iso/BaseOS
- enabled=1
- gpgcheck=0
Notes:
file:// URLs need three slashes for absolute paths: file:///mnt/iso/BaseOS .
The path must be the repository root that contains repodata/ (or the correct relative structure for that product tree).
Training labs sometimes set gpgcheck=0 for unsigned local trees. Prefer gpgcheck=1 with a proper gpgkey when keys are provided—match the task.
- HTTP/HTTPS remote repository [training-extra]
- name=Training Extra Packages
- baseurl=http://materials.example.lab/rhel10/extra/
- enabled=1
- gpgcheck=1
- gpgkey=http://materials.example.lab/RPM-GPG-KEY-training
On a real RHEL system attached to Red Hat CDN, BaseOS/AppStream repos are usually provisioned via subscription-manager content and vendor .repo files. Exam environments may preconfigure CDN access or give you a local/training URL instead—always follow the task wording.
- Creating and editing repository definitions
- Manual file creation sudo vim /etc/yum.repos.d/exam-local.repo
- # or
- sudo tee /etc/yum.repos.d/exam-local.repo <<'EOF'
- [exam-local]
- name=Exam Local Repo
- baseurl=file:///var/www/html/repo
- enabled=1
- gpgcheck=0
- EOF
Permissions: world-readable config is normal; root must own the file. Wrong ownership is rarely the issue— typos in baseurl and missing repodata are.
dnf config-manager (when available)
Many RHEL systems provide dnf config-manager (from dnf-plugins-core ) to add or toggle repos without hand-editing: # Add a repo from a URL (creates a .repo file; often enabled by default)
- sudo dnf config-manager --add-repo=https://example.com/my.repo
- # or
- sudo dnf config-manager --add-repo=http://server.lab/rhel10/
- # Enable / disable by repo id
- sudo dnf config-manager --set-enabled exam-local
- sudo dnf config-manager --set-disabled exam-local
If the plugin is missing in a constrained lab, fall back to editing /etc/yum.repos.d/ directly—the exam grades end state , not which editor you used.
- Importing a GPG key sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
- # or from a file the task provides
- sudo rpm --import /tmp/RPM-GPG-KEY-training
Keys under /etc/pki/rpm-gpg/ are the usual Red Hat locations. After import, gpgkey=file:///etc/pki/rpm-gpg/... in the .repo file can succeed during install.
- Verifying repository access
- Never assume a .repo file works. Verify: # List enabled repositories
- dnf repolist
- # List all (enabled and disabled)
- dnf repolist --all
- # Verbose detail including URLs
- dnf repolist -v
- # Refresh metadata (forces contact with baseurl/metalink)
- sudo dnf makecache
- # or
- sudo dnf clean all
- sudo dnf makecache
Success looks like your new repo id appearing in dnf repolist and makecache completing without “Error: Failed to download metadata” or 404-style failures.
- Useful inspections: ls /etc/yum.repos.d/
- grep -R "^\[" /etc/yum.repos.d/
- cat /etc/dnf/dnf.conf
- dnf config-manager --dump # if plugin present; dumps effective config
- Troubleshooting map
- Symptom Likely cause Fix approach
- Repo missing from repolist enabled=0 or file not named *.repo Set enabled=1 ; rename file
- Metadata download failed Wrong baseurl , network, or no repodata Fix URL; curl /browse path; mount ISO
- GPG errors on install Missing key or gpgcheck=1 without key Import key or set correct gpgkey=
- SSL certificate errors HTTPS MITM/lab CA issues Use HTTP if task allows, or install CA
- Duplicate repo ids Two sections with same [id] Make ids unique
- Temporary enable/disable without editing files
- For a single transaction: sudo dnf install --enablerepo=exam-local httpd
- sudo dnf install --disablerepo="*" --enablerepo=exam-local somepkg
Exam persistence note: --enablerepo on one command does not permanently enable the repo. If the task says “configure the system to use this repository,” edit the .repo ( enabled=1 ) or use config-manager --set-enabled . Runtime-only flags vanish after the shell session—and after reboot the permanent file state is what matters.
Red Hat content layout (conceptual)
Production RHEL 10 systems commonly expose at least:
BaseOS — core OS packages
AppStream — user-space applications, runtimes, databases, etc.
You do not need to memorize every RHSM product name for EX200, but you must recognize that multiple repos may be required for a complete package set. Disabling AppStream while installing a desktop or language stack often causes “No match for argument” failures that look like missing packages but are really disabled sources .
Exam workflow: “Add a repository and prove it”
Read the task for URL/path, repo id requirements, GPG expectations, and enable state.
Create /etc/yum.repos.d/<descriptive>.repo with correct baseurl / metalink .
Import GPG keys if provided.
Run dnf repolist and dnf makecache .
Optionally search for a known package from that repo ( dnf search / dnf list ) without installing yet if the task only asks for access.
Reboot if you have time (or at least re-open a new session) and confirm /etc/yum.repos.d/ content and dnf repolist still show the repo—file-based config should persist; prove it.
Common traps
Writing baseurl=file://mnt/iso (two slashes after file: for absolute path misuse) — use file:///mnt/iso/... .
Pointing baseurl at the ISO file instead of the mounted directory tree containing repodata .
Leaving enabled=0 after creating a perfect file.
Assuming dnf.conf alone is enough while forgetting /etc/yum.repos.d/ .
Using spaces or invalid characters carelessly in repo ids — keep ids simple: letters, numbers, hyphens, underscores.
Fixing only the client when the server path 404s — verify the remote path with curl -I when network tools are available.
Relationship to later objectives
Section 6.2 assumes repositories work. Chapter objectives on install/update from CDN, remote repo, or local filesystem reuse these same .repo skills. Flatpak (6.3–6.4) is a parallel application distribution system—it does not replace DNF for system RPMs ( kernel , httpd , firewalld , etc.).
Section checkpoint
You should be able to create a correct *.repo file, enable or disable repos permanently, import GPG keys, refresh metadata, list available repositories, and leave a configuration that still works after reboot. That is the EX200 definition of “configure access to RPM repositories.”