Question 99 of 500
Project Life Cycle PhasesmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is a filesystem label or UUID mismatch between the backup software configuration and the actual backup volume. This is the most likely cause of the backup failure because the backup software relies on a unique identifier—either a human-readable label or a universally unique identifier (UUID)—to locate and mount the correct target volume. When the actual volume’s label or UUID differs from the value stored in the software’s configuration, the software cannot find its intended destination, resulting in mount errors and a failed job. On the CompTIA Project+ PK0-005 exam, this scenario tests your ability to interpret logs and configuration files to isolate root causes in project troubleshooting tasks. A common trap is to blame hardware failure or network issues, but the logs will typically show “volume not found” or “mount failed” errors tied to the identifier. Remember the mnemonic: **L-U Match**—Label or UUID must match the config to latch onto the backup.

PK0-005 Project Life Cycle Phases Practice Question

This PK0-005 practice question tests your understanding of project life cycle phases. 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.

=== backup.log ===
2025-03-15 02:00:01 INFO: Starting daily backup job
2025-03-15 02:00:05 INFO: Mounting backup volume /dev/sdb1
2025-03-15 02:00:07 ERROR: Volume /dev/sdb1 is not a valid backup volume
2025-03-15 02:00:08 ERROR: Backup aborted
2025-03-15 02:00:09 INFO: Unmounting volume

=== fstab ===
/dev/sda1 / ext4 defaults 0 1
/dev/sdb1 /backup ext4 defaults 0 2
/dev/sdc1 /var ext4 defaults 0 2

=== backup_script.sh ===
#!/bin/bash
mount /dev/sdb1 /backup
rsync -av /data /backup
umount /backup

Refer to the exhibit. A server administrator is troubleshooting a failed backup job. Based on the logs and configuration files, what is the most likely cause of the error?

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.

Question 1mediummultiple choice
Full question →

Exhibit

Refer to the exhibit.

=== backup.log ===
2025-03-15 02:00:01 INFO: Starting daily backup job
2025-03-15 02:00:05 INFO: Mounting backup volume /dev/sdb1
2025-03-15 02:00:07 ERROR: Volume /dev/sdb1 is not a valid backup volume
2025-03-15 02:00:08 ERROR: Backup aborted
2025-03-15 02:00:09 INFO: Unmounting volume

=== fstab ===
/dev/sda1 / ext4 defaults 0 1
/dev/sdb1 /backup ext4 defaults 0 2
/dev/sdc1 /var ext4 defaults 0 2

=== backup_script.sh ===
#!/bin/bash
mount /dev/sdb1 /backup
rsync -av /data /backup
umount /backup

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

The backup volume's filesystem label or UUID does not match the expected value in the backup software configuration.

The backup software configuration specifies a filesystem label or UUID for the backup volume, but the actual volume has a different label or UUID. This mismatch causes the backup job to fail because the software cannot locate the intended target volume. The logs would show errors related to mounting or accessing the volume by its expected identifier.

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 backup volume has a corrupted filesystem.

    Why it's wrong here

    The log does not indicate filesystem corruption; it says 'not a valid backup volume'.

  • The backup volume is out of space.

    Why it's wrong here

    No disk space error is shown in the log.

  • The backup volume's filesystem label or UUID does not match the expected value in the backup software configuration.

    Why this is correct

    The error suggests the backup software verifies the volume identity and it fails.

    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 backup script is not scheduled to run at the correct time.

    Why it's wrong here

    The log shows it ran at 2:00 AM, which appears scheduled correctly.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may assume a 'failed backup job' is always due to insufficient space or a corrupted filesystem, overlooking the subtle but common configuration mismatch between the expected volume identifier and the actual volume identifier.

Trap categories for this question

  • Command / output trap

    No disk space error is shown in the log.

Detailed technical explanation

How to think about this question

Backup software often uses the blkid command or reads /etc/fstab to match a configured UUID or label to a device node. If the volume's filesystem is reformatted or replaced, its UUID changes, causing the mount to fail. In Linux, the 'lsblk -f' command displays UUIDs and labels; a mismatch can be resolved by updating the backup configuration or reformatting with the original UUID using 'mkfs -U'. This is a common issue when swapping backup drives or restoring from a snapshot.

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 PK0-005 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.

Related practice questions

Related PK0-005 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PK0-005 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PK0-005 question test?

Project Life Cycle Phases — This question tests Project Life Cycle Phases — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The backup volume's filesystem label or UUID does not match the expected value in the backup software configuration. — The backup software configuration specifies a filesystem label or UUID for the backup volume, but the actual volume has a different label or UUID. This mismatch causes the backup job to fail because the software cannot locate the intended target volume. The logs would show errors related to mounting or accessing the volume by its expected identifier.

What should I do if I get this PK0-005 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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

This PK0-005 practice question is part of Courseiva's free CompTIA 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 PK0-005 exam.