EX200 Essential Tools Practice Question
A developer needs to compile software from source and install it under /opt/custom. To avoid affecting the system package manager, which approach should be used?
⚠ Common exam trap
Red Hat often tests the misconception that `--prefix=/usr/local` is safe, but the trap here is that `/usr/local` can still be managed by the system package manager in some configurations, and the only way to guarantee no interference is to use a completely separate directory like `/opt/custom`.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Compile with './configure --prefix=/opt/custom' and then 'make install'
Using `./configure --prefix=/opt/custom` sets the installation root to `/opt/custom`, which keeps the compiled software completely separate from the system-managed directories (e.g., `/usr`, `/usr/local`). Running `make install` then installs all files under this custom prefix, ensuring the system package manager (RPM/YUM/DNF) is not affected by the manual installation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Compile and install with default paths, then use 'make uninstall' to remove
Why it's wrong here
Running ./configure without --prefix defaults to /usr/local, placing binaries and libraries alongside system-managed paths, which can shadow package files and create conflicts. Moreover, 'make uninstall' is often an incomplete or missing target in the Makefile, so it may leave many installed files behind. Thus this approach does not guarantee a clean or reversible installation.
- ✗
Compile with './configure --prefix=/opt/custom' and use 'checkinstall' to create an RPM
Why it's wrong here
Using 'checkinstall' to build an RPM from a custom-built source adds unnecessary complexity and a third-party tool dependency. The tool may not reliably capture every installed file or dependency, leading to an incomplete package. Since the goal is simply to compile and install, performing 'make install' into a dedicated prefix like /opt/custom is straightforward and sufficient.
- ✗
Compile with './configure --prefix=/usr' and then install
Why it's wrong here
Specifying '--prefix=/usr' causes the software to be installed directly into the distribution's system directories, which are managed by the package manager. This can overwrite files that belong to RPM packages, break package integrity, and hinder future updates or removals. Manual installation into /usr is strongly discouraged for exactly these reasons.
- ✓
Compile with './configure --prefix=/opt/custom' and then 'make install'
Why this is correct
Using './configure --prefix=/opt/custom' sets the installation root to a dedicated directory, typically /opt/custom. The subsequent 'make install' places all binaries, libraries, and configuration files under that single prefix, keeping the software isolated from system-managed areas. This avoids conflicts with the package manager and allows clean removal by simply deleting the /opt/custom directory.
Go deeper
Related to this question
About these practice questions
One of 427 original EX200 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This EX200 practice question is part of Courseiva's free Red Hat certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the EX200 exam.