mcAfee Secure Website
23

CompTIA XK0-006 Bundle

Exam Code: XK0-006

Exam Name CompTIA Linux+

Certification Provider: CompTIA

Corresponding Certification: CompTIA Linux+

XK0-006 Training Materials $19.99

Reliable & Actual Study Materials for XK0-006 Exam Success

The Latest XK0-006 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    XK0-006 Questions & Answers

    160 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • exam =30
    Study Guide

    XK0-006 Study Guide

    1297 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

CompTIA Linux+ (XK0-006) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable CompTIA Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $154.98
Bundle Price: $134.99

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    160 Questions

    $124.99
    exam =35
  • exam =36
    Study Guide

    Study Guide

    1297 PDF Pages

    $29.99

CompTIA XK0-006 Practice Test 10

Question 90

A Linux administrator evaluates: An appliance image has two NetworkManager profiles and the wrong one automatically activates at startup. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. Correlate lspci, lsusb, lscpu, lsblk, dmesg and relevant /sys device information to identify Linux hardware before modifying drivers.
  2. A restore rehearsal recovers the expected files, ownership and permissions to an isolated path with matching checksums.
  3. Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode.
  4. Use NetworkManager nmcli connection profiles to set the intended IPv4 address, gateway and DNS, then activate and verify the profile safely.
  5. nmcli and ip address/ip route show the intended persistent configuration before and after reactivation.

Explanation

Correct Answers

D:

The observed Linux condition is: An appliance image has two NetworkManager profiles and the wrong one automatically activates at startup. The recommended direct administrative response is: Use NetworkManager nmcli connection profiles to set the intended IPv4 address, gateway and DNS, then activate and verify the profile safely. The relevant failure or security risk is: Changing an ephemeral interface address without saving its connection profile can remove remote access at restart. Validate success with: nmcli and ip address/ip route show the intended persistent configuration before and after reactivation.

E:

For the specific observation (An appliance image has two NetworkManager profiles and the wrong one automatically activates at startup), the acceptance evidence is: nmcli and ip address/ip route show the intended persistent configuration before and after reactivation. This verifies the action (Use NetworkManager nmcli connection profiles to set the intended IPv4 address, gateway and DNS, then activate and verify the profile safely.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Changing an ephemeral interface address without saving its connection profile can remove remote access at restart.

Incorrect Answers

A:

Hardware and device discovery (1.2) addresses another technical failure: Guessing a driver without confirming the kernel-visible hardware can mask a disconnected device or wrong bus identity. The case states: An appliance image has two NetworkManager profiles and the wrong one automatically activates at startup. The most direct paired action and test is: Use NetworkManager nmcli connection profiles to set the intended IPv4 address, gateway and DNS, then activate and verify the profile safely.

B:

Rsync incremental backup and restoration verification (1.6) would demonstrate or implement: A restore rehearsal recovers the expected files, ownership and permissions to an isolated path with matching checksums. This choice can be useful for that problem, but it does not establish the Persistent network configuration with nmcli control being assessed here.

C:

Persistent filesystem mounting by UUID (1.3) would demonstrate or implement: Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode. This case instead tests Persistent network configuration with nmcli; the choice measures or changes another part of the system.

Question 91

A Linux administrator investigates: A web client gets an old database IP because an /etc/hosts entry overrides updated DNS records. Which action BEST addresses the specific Linux technical requirement?

  1. Use a bounded grep, awk, cut or sort pipeline to select the required log or delimited-data fields without changing the source file.
  2. Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.
  3. Use libvirt and virsh to inspect, define, start and manage supported KVM guests, distinguishing guest state from disk-image data.
  4. Use modprobe and module metadata to load or remove a supported kernel module with dependency resolution, checking lsmod and kernel logs afterward.

Explanation

Correct Answer

B:

The observed Linux condition is: A web client gets an old database IP because an /etc/hosts entry overrides updated DNS records. The recommended direct administrative response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. The relevant failure or security risk is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. Validate success with: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Incorrect Answers

A:

Shell text processing pipelines (1.5) addresses another technical failure: Grepping an entire unfiltered log or using a wrong delimiter can silently miscount events or report unrelated fields. The case states: A web client gets an old database IP because an /etc/hosts entry overrides updated DNS records. The most direct diagnosis is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.

C:

KVM virtual machine lifecycle with virsh (1.7) addresses another technical failure: Deleting or redefining a VM without understanding its storage volumes can lose persistent guest data. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

D:

Kernel module dependencies with modprobe (1.2) addresses another technical failure: Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional. The required diagnosis concerns DNS resolver diagnosis with dig and hosts precedence; a passing result for this alternative could leave that requirement unresolved.

Question 92

In the post-change validation, the team sees: A web client gets an old database IP because an /etc/hosts entry overrides updated DNS records. Which evidence MOST directly confirms the appropriate correction succeeded?

  1. The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.
  2. The archive inventory matches the intended files and a test extraction reproduces them at the correct locations.
  3. The relevant module and required dependencies appear loaded, and the associated device becomes usable without new kernel errors.
  4. Inspection shows persistent settings in /etc and expected service state or logs in appropriate paths such as /var or /run.

Explanation

Correct Answer

A:

For the specific observation (A web client gets an old database IP because an /etc/hosts entry overrides updated DNS records), the acceptance evidence is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result. This verifies the action (Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched.

Incorrect Answers

B:

Tar archive creation and extraction integrity (1.6) would demonstrate or implement: The archive inventory matches the intended files and a test extraction reproduces them at the correct locations. This choice can be useful for that problem, but it does not establish the DNS resolver diagnosis with dig and hosts precedence control being assessed here.

C:

Kernel module dependencies with modprobe (1.2) would demonstrate or implement: The relevant module and required dependencies appear loaded, and the associated device becomes usable without new kernel errors. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

D:

Filesystem Hierarchy Standard paths (1.1) would demonstrate or implement: Inspection shows persistent settings in /etc and expected service state or logs in appropriate paths such as /var or /run. The required evidence concerns DNS resolver diagnosis with dig and hosts precedence; a passing result for this alternative could leave that requirement unresolved.

Question 93

A change review on a Linux server identifies: A Linux host can ping a numeric public IP but cannot resolve a short internal hostname. Which action BEST addresses the specific Linux technical requirement?

  1. Locate system-specific configuration, transient runtime data, device nodes, user homes and variable application data under their appropriate FHS paths.
  2. Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.
  3. Use modprobe and module metadata to load or remove a supported kernel module with dependency resolution, checking lsmod and kernel logs afterward.
  4. Create and inspect a tar archive with the appropriate compression choice and test extraction into a controlled directory before depending on it.

Explanation

Correct Answer

B:

The observed Linux condition is: A Linux host can ping a numeric public IP but cannot resolve a short internal hostname. The recommended direct administrative response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. The relevant failure or security risk is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. Validate success with: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Incorrect Answers

A:

Filesystem Hierarchy Standard paths (1.1) addresses another technical failure: Placing persistent configuration or operational logs under temporary paths can cause data loss or a broken service on reboot. The case states: A Linux host can ping a numeric public IP but cannot resolve a short internal hostname. The most direct corrective action is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.

C:

Kernel module dependencies with modprobe (1.2) addresses another technical failure: Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

D:

Tar archive creation and extraction integrity (1.6) addresses another technical failure: Mistaking archive packaging for a verified backup or extracting unsafe paths blindly can lose files or overwrite live content. The required corrective action concerns DNS resolver diagnosis with dig and hosts precedence; a passing result for this alternative could leave that requirement unresolved.

Question 94

A Linux administrator reviews a reported issue: A Linux host can ping a numeric public IP but cannot resolve a short internal hostname. Which failure mode or risk is MOST relevant to this condition?

  1. An unverified mirror or incorrectly placed trailing slash can back up the wrong directory structure or propagate deletions.
  2. Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched.
  3. Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional.
  4. Grepping an entire unfiltered log or using a wrong delimiter can silently miscount events or report unrelated fields.

Explanation

Correct Answer

B:

The reported situation (A Linux host can ping a numeric public IP but cannot resolve a short internal hostname) most directly creates this failure risk: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. The corresponding safe response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. An appropriate outcome check is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Incorrect Answers

A:

Rsync incremental backup and restoration verification (1.6) would demonstrate or implement: An unverified mirror or incorrectly placed trailing slash can back up the wrong directory structure or propagate deletions. The case states: A Linux host can ping a numeric public IP but cannot resolve a short internal hostname. The most direct risk is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched.

C:

Kernel module dependencies with modprobe (1.2) would demonstrate or implement: Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

D:

Shell text processing pipelines (1.5) would demonstrate or implement: Grepping an entire unfiltered log or using a wrong delimiter can silently miscount events or report unrelated fields. The required risk concerns DNS resolver diagnosis with dig and hosts precedence; a passing result for this alternative could leave that requirement unresolved.

Question 95

A production incident ticket states: A resolver change points /etc/resolv.conf at an unavailable server and package updates fail by name. Which action BEST addresses the specific Linux technical requirement?

  1. Use rsync with appropriate source, destination and preservation flags, then perform a controlled restore and compare file content and metadata.
  2. Use modprobe and module metadata to load or remove a supported kernel module with dependency resolution, checking lsmod and kernel logs afterward.
  3. Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.
  4. Use a bounded grep, awk, cut or sort pipeline to select the required log or delimited-data fields without changing the source file.

Explanation

Correct Answer

C:

The observed Linux condition is: A resolver change points /etc/resolv.conf at an unavailable server and package updates fail by name. The recommended direct administrative response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. The relevant failure or security risk is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. Validate success with: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Incorrect Answers

A:

Rsync incremental backup and restoration verification (1.6) addresses another technical failure: An unverified mirror or incorrectly placed trailing slash can back up the wrong directory structure or propagate deletions. The case states: A resolver change points /etc/resolv.conf at an unavailable server and package updates fail by name. The most direct corrective action is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.

B:

Kernel module dependencies with modprobe (1.2) addresses another technical failure: Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional. This choice can be useful for that problem, but it does not establish the DNS resolver diagnosis with dig and hosts precedence control being assessed here.

D:

Shell text processing pipelines (1.5) addresses another technical failure: Grepping an entire unfiltered log or using a wrong delimiter can silently miscount events or report unrelated fields. The required corrective action concerns DNS resolver diagnosis with dig and hosts precedence; a passing result for this alternative could leave that requirement unresolved.

Question 96

An infrastructure engineer checks a specific situation: A resolver change points /etc/resolv.conf at an unavailable server and package updates fail by name. Which evidence MOST directly confirms the appropriate correction succeeded?

  1. The archive inventory matches the intended files and a test extraction reproduces them at the correct locations.
  2. A controlled command writes successes and errors to the separate expected logs with the intended retention behavior.
  3. A restore rehearsal recovers the expected files, ownership and permissions to an isolated path with matching checksums.
  4. The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Explanation

Correct Answer

D:

For the specific observation (A resolver change points /etc/resolv.conf at an unavailable server and package updates fail by name), the acceptance evidence is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result. This verifies the action (Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched.

Incorrect Answers

A:

Tar archive creation and extraction integrity (1.6) would demonstrate or implement: The archive inventory matches the intended files and a test extraction reproduces them at the correct locations. The case states: A resolver change points /etc/resolv.conf at an unavailable server and package updates fail by name. The most direct evidence is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

B:

Shell output redirection stdout stderr and append (1.5) would demonstrate or implement: A controlled command writes successes and errors to the separate expected logs with the intended retention behavior. This choice can be useful for that problem, but it does not establish the DNS resolver diagnosis with dig and hosts precedence control being assessed here.

C:

Rsync incremental backup and restoration verification (1.6) would demonstrate or implement: A restore rehearsal recovers the expected files, ownership and permissions to an isolated path with matching checksums. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

Question 97

An authorized Linux operations assessment observes: An operator uses dig against public DNS and assumes that proves the local NSS hosts lookup is correct. Which action BEST addresses the specific Linux technical requirement?

  1. Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.
  2. Use rsync with appropriate source, destination and preservation flags, then perform a controlled restore and compare file content and metadata.
  3. Create and inspect a tar archive with the appropriate compression choice and test extraction into a controlled directory before depending on it.
  4. Direct standard output and standard error to their intended paths using shell redirection, and choose append or overwrite explicitly.

Explanation

Correct Answer

A:

The observed Linux condition is: An operator uses dig against public DNS and assumes that proves the local NSS hosts lookup is correct. The recommended direct administrative response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. The relevant failure or security risk is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. Validate success with: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Incorrect Answers

B:

Rsync incremental backup and restoration verification (1.6) addresses another technical failure: An unverified mirror or incorrectly placed trailing slash can back up the wrong directory structure or propagate deletions. This choice can be useful for that problem, but it does not establish the DNS resolver diagnosis with dig and hosts precedence control being assessed here.

C:

Tar archive creation and extraction integrity (1.6) addresses another technical failure: Mistaking archive packaging for a verified backup or extracting unsafe paths blindly can lose files or overwrite live content. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

D:

Shell output redirection stdout stderr and append (1.5) addresses another technical failure: Confusing 2> with > or using overwrite when append is required can lose evidence or hide errors. The required evidence concerns DNS resolver diagnosis with dig and hosts precedence; a passing result for this alternative could leave that requirement unresolved.

Question 98

In a controlled system validation, the observation is: An operator uses dig against public DNS and assumes that proves the local NSS hosts lookup is correct. Which failure mode or risk is MOST relevant to this condition?

  1. Applying an ext4 repair or resize utility to an XFS volume, or repairing a mounted filesystem improperly, can fail or damage data.
  2. Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched.
  3. Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode.
  4. Placing persistent configuration or operational logs under temporary paths can cause data loss or a broken service on reboot.

Explanation

Correct Answer

B:

The reported situation (An operator uses dig against public DNS and assumes that proves the local NSS hosts lookup is correct) most directly creates this failure risk: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. The corresponding safe response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. An appropriate outcome check is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Incorrect Answers

A:

Ext4 and XFS filesystem repair and growth distinctions (1.3) would demonstrate or implement: Applying an ext4 repair or resize utility to an XFS volume, or repairing a mounted filesystem improperly, can fail or damage data. The case states: An operator uses dig against public DNS and assumes that proves the local NSS hosts lookup is correct. The most direct evidence is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched.

C:

Persistent filesystem mounting by UUID (1.3) would demonstrate or implement: Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

D:

Filesystem Hierarchy Standard paths (1.1) would demonstrate or implement: Placing persistent configuration or operational logs under temporary paths can cause data loss or a broken service on reboot. The required evidence concerns DNS resolver diagnosis with dig and hosts precedence; a passing result for this alternative could leave that requirement unresolved.

Question 99

During a planned service review, engineers find: A newly deployed VM resolves its own hostname differently from the corporate DNS service. Which action BEST addresses the specific Linux technical requirement?

  1. Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.
  2. Locate system-specific configuration, transient runtime data, device nodes, user homes and variable application data under their appropriate FHS paths.
  3. Choose filesystem-specific supported tools such as resize2fs for ext4 and xfs_growfs for mounted XFS; perform repair only under appropriate unmount and recovery conditions.
  4. Record the correct filesystem UUID and supported mount options in /etc/fstab and test the entry with mount before restarting the host.

Explanation

Correct Answer

A:

The observed Linux condition is: A newly deployed VM resolves its own hostname differently from the corporate DNS service. The recommended direct administrative response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. The relevant failure or security risk is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. Validate success with: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Incorrect Answers

B:

Filesystem Hierarchy Standard paths (1.1) addresses another technical failure: Placing persistent configuration or operational logs under temporary paths can cause data loss or a broken service on reboot. This choice can be useful for that problem, but it does not establish the DNS resolver diagnosis with dig and hosts precedence control being assessed here.

C:

Ext4 and XFS filesystem repair and growth distinctions (1.3) addresses another technical failure: Applying an ext4 repair or resize utility to an XFS volume, or repairing a mounted filesystem improperly, can fail or damage data. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

D:

Persistent filesystem mounting by UUID (1.3) addresses another technical failure: Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode. The required corrective action concerns DNS resolver diagnosis with dig and hosts precedence; a passing result for this alternative could leave that requirement unresolved.

Question 100

A Linux administrator evaluates: A newly deployed VM resolves its own hostname differently from the corporate DNS service. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. Inspect /proc/mdstat and mdadm array details, identify the failed member and follow a documented supported replacement and rebuild process.
  2. The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.
  3. Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode.
  4. Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.
  5. pvs, vgs, lvs and the filesystem capacity check show the intended growth with application data intact.

Explanation

Correct Answers

B:

For the specific observation (A newly deployed VM resolves its own hostname differently from the corporate DNS service), the acceptance evidence is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result. This verifies the action (Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched.

D:

The observed Linux condition is: A newly deployed VM resolves its own hostname differently from the corporate DNS service. The recommended direct administrative response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. The relevant failure or security risk is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. Validate success with: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

Incorrect Answers

A:

Software RAID health and rebuild with mdadm (1.3) addresses another technical failure: Replacing the wrong disk or trusting a degraded mirror without monitoring rebuild can cause avoidable data loss. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.

C:

Persistent filesystem mounting by UUID (1.3) would demonstrate or implement: Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.

E:

LVM physical volume to logical volume capacity growth (1.3) would demonstrate or implement: pvs, vgs, lvs and the filesystem capacity check show the intended growth with application data intact. The paired-answer requirement concerns DNS resolver diagnosis with dig and hosts precedence; this alternative does not provide the matching intervention and separate acceptance evidence.