LPIC-1 Linux Installation and Package Management Practice Question
A Debian-based server has a custom application installed from a local .deb file that was built in-house. The administrator wants to verify the package's metadata (version, dependencies, and maintainer scripts) before installing it on a production system, but does not want to actually install it. Which command should the administrator use?
⚠ Common exam trap
Many candidates confuse the options that list files inside a package with the option that displays the package's control metadata.
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
✓
dpkg --info application.deb
The dpkg --info command reads the control information embedded in a .deb archive, showing the package name, version, architecture, dependencies, and maintainer scripts. It is the standard way to inspect a local package's metadata before installation, which is precisely what the administrator needs to verify the in-house application without modifying the production system.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
dpkg --contents application.deb
Why it's wrong here
The --contents (or -c) option lists the files contained inside the .deb archive, which is useful for seeing what will be placed on the filesystem. However, it does not show version, dependency, or maintainer script metadata, so it does not satisfy the requirement to verify those specific details before installation.
- ✗
apt-cache show application
Why it's wrong here
apt-cache show queries the APT package cache for a package available from configured repositories. A locally built .deb file that has not been added to a repository is not in the cache, so this command would fail to find the package. It also cannot display the contents of a specific local file.
- ✓
dpkg --info application.deb
Why this is correct
The --info (or -I) option to dpkg displays detailed metadata from a .deb archive, including package name, version, architecture, dependencies, and the maintainer scripts, without installing it. This is exactly what the administrator needs to inspect the package before deployment, making it the correct tool for a pre-installation review of an in-house .deb file.
- ✗
dpkg-deb --extract application.deb /tmp/app
Why it's wrong here
The --extract option unpacks the files from the .deb archive into a directory but does not display metadata such as version, dependencies, or maintainer scripts. While it can be used to inspect the package contents, it does not fulfill the administrator's requirement to review metadata without installation.
Go deeper
Related to this question
About these practice questions
One of 402 original LPIC-1 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official LPI exam blueprint
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.