The answer is that the $releasever or $basearch variables are not expanding correctly, leading to an invalid repository URL. This is the most likely cause when a yum repo shows 0 packages because YUM relies on these dynamic variables to construct the baseurl path to the repository metadata; if the variables are undefined—often due to a missing or misconfigured /etc/yum/vars/ directory or an incorrect release version—the resulting URL becomes unreachable, and YUM cannot download the package list. On the LPIC-1 exam, this scenario tests your understanding of YUM repository configuration and variable expansion, a common trap where candidates overlook the /etc/yum/vars/ files or assume a static URL is being used. Remember the memory tip: "No vars, no bars"—if the variable files are missing, you get zero packages.
LPIC-1 Linux Installation and Package Management Practice Question
This LPIC-1 practice question tests your understanding of linux installation and package management. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
```
$ cat /etc/yum.repos.d/custom.repo
[custom]
name=Custom Repository
baseurl=http://repo.example.com/centos/$releasever/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://repo.example.com/RPM-GPG-KEY-custom
```
$ yum repolist
repo id repo name status
custom Custom Repository 0
Based on the exhibit, the 'custom' repository shows 0 packages. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The $releasever or $basearch variables are not expanding correctly, leading to an invalid URL
The 'custom' repository shows 0 packages because the $releasever or $basearch variables are not expanding correctly, resulting in an invalid or unreachable repository URL. Yum uses these variables to dynamically construct the baseurl, and if they are undefined or incorrect (e.g., due to a missing or misconfigured /etc/yum/vars/ directory or incorrect release version), the repository metadata cannot be downloaded, so yum reports 0 packages available.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The repository is disabled because 'enabled=1' is missing
Why it's wrong here
It is set to 1, so enabled.
✓
The $releasever or $basearch variables are not expanding correctly, leading to an invalid URL
Why this is correct
Variables may not be set or the repository doesn't exist for that release.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The GPG key is missing, causing yum to ignore the repository
Why it's wrong here
GPG key affects package verification, not repository listing.
✗
The repository metadata is corrupt and needs to be regenerated
Why it's wrong here
If metadata were corrupt, yum would report an error.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume 'enabled=1' is mandatory or that GPG key issues cause repositories to be ignored, but the real culprit is variable expansion failure, which silently yields an empty package list without error messages.
Detailed technical explanation
How to think about this question
Yum and DNF use the variables $releasever (from /etc/yum/vars/releasever or the distro version) and $basearch (from uname -m or /etc/yum/vars/basearch) to construct repository URLs. If these variables are unset or incorrect, the baseurl may point to a non-existent path (e.g., 'http://example.com/centos/$releasever/os/$basearch' becomes 'http://example.com/centos//os/'), causing yum to fail to retrieve repodata/repomd.xml and thus report 0 packages. This is a common issue when migrating systems or using custom repository definitions without proper variable configuration.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the LPIC-1 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Linux Installation and Package Management — This question tests Linux Installation and Package Management — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The $releasever or $basearch variables are not expanding correctly, leading to an invalid URL — The 'custom' repository shows 0 packages because the $releasever or $basearch variables are not expanding correctly, resulting in an invalid or unreachable repository URL. Yum uses these variables to dynamically construct the baseurl, and if they are undefined or incorrect (e.g., due to a missing or misconfigured /etc/yum/vars/ directory or incorrect release version), the repository metadata cannot be downloaded, so yum reports 0 packages available.
What should I do if I get this LPIC-1 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This LPIC-1 practice question is part of Courseiva's free LPI 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 LPIC-1 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.