Inspecting GPT partition information | LinuC Level 1 101 Exam original practice question

1.04.4Basic

Inspect partition numbers, start/end sectors, and type codes on GPT disk /dev/sdb.

Do not modify the partition table.

Which command is appropriate?

Hint 1: Focus on the requirement

Use the query that reads installed-package version data from the local RPM database.

Hint 2: Key terms

Review the short RPM query and verification definitions before comparing the choices.

rpm -q: Queries installed package state and version.
RPM database: Local records of installed package metadata and ownership.
NEVRA: Name, epoch, version, release, and architecture used to identify an RPM.

Detailed explanation

Correctrpm -q bash

Correct. gdisk -l /dev/sdb lists the GPT partition table read-only.

Incorrectrpm -ql bash

Incorrect. mkfs creates a filesystem and can destroy existing data.

Incorrectrpm -qR bash

Incorrect. mount attaches a filesystem and does not inspect GPT layout.

Incorrectrpm -V bash

Incorrect. pvcreate initializes an LVM physical volume and changes state.

An example you can run in a temporary verification environment.

rpm -q rpm

rpm-版-リリース等。未導入ならpackage rpm is not installed相当

Environment: RPM 4.x / 読み取り照会
Use a read-only query or trusted disposable RPM when testing.
RPM options and signature behavior should be confirmed on the target distribution.

Foundation review

The basic query reports package identity; file-list, dependency, and verification options answer different questions.

Query a known installed package and observe the result for an absent package.

Question IDKL-101-540

EnvironmentRPM 4.x / 読み取り照会

Last technical review2026-08-13

More practice in this area