CompTIA Linux+ XK0-006 Practice Test 10
Question 90
The team proposes to check lm_sensors and supported BMC hardware readings using ipmitool before altering workloads after observing A rack server reports thermal alarms while ordinary CPU usage remains low. Which Linux behavior supports the change?
- Persistent mount definitions influence boot jobs and must match available filesystems and intended failure handling
- Temperature and fan sensor telemetry can reveal chassis cooling faults independently of application CPU load
- LVM consumes initialized physical volumes inside a volume group rather than arbitrary unprepared block devices
- Name resolution depends on configured DNS servers and lookup sources independently of Layer 3 reachability
Explanation
Correct Answer
B:Temperature and fan sensor telemetry can reveal chassis cooling faults independently of application CPU load. That is the key operating principle behind the selected remediation, check lm_sensors and supported BMC hardware readings using ipmitool before altering workloads. The distinction matters because raising CPU limits without inspecting a failed fan can increase thermal shutdown risk. An appropriate observable outcome is that sensor readings and hardware alert status return to acceptable ranges after the cooling issue is resolved.
Incorrect Answers
A:Persistent mount definitions influence boot jobs and must match available filesystems and intended failure handling is a valid explanation for another Linux operation, such as when a host cannot boot after a stale USB disk entry in /etc/fstab becomes unavailable. The principle here is that temperature and fan sensor telemetry can reveal chassis cooling faults independently of application CPU load.
C:LVM consumes initialized physical volumes inside a volume group rather than arbitrary unprepared block devices is a valid explanation for another Linux operation, such as when an administrator adds a disk to a volume group but LVM still reports no new physical extents. The principle here is that temperature and fan sensor telemetry can reveal chassis cooling faults independently of application CPU load.
D:Name resolution depends on configured DNS servers and lookup sources independently of Layer 3 reachability is a valid explanation for another Linux operation, such as when an application reports DNS failure but pinging its numeric service IP succeeds. The principle here is that temperature and fan sensor telemetry can reveal chassis cooling faults independently of application CPU load.
Question 91
During a Linux service review, the team discovers: A log-rotation process cannot delete an archived file because another process still has it open. Which corrective action should be selected?
- Recreate the link using the intended stable target path and verify it with readlink or ls -l
- Enable the appropriate systemd service unit and verify the install target dependencies
- Check the path with lsof and resolve the owning process before retrying the maintenance step
- Add the user with usermod -aG and verify memberships using id or groups
Explanation
Correct Answer
C:Check the path with lsof and resolve the owning process before retrying the maintenance step. This directly addresses the stated Linux administration condition because open file descriptors can retain underlying files after their directory names change or disappear. If the underlying problem is ignored, repeatedly moving the file without identifying its open descriptor can leave disk blocks allocated. Verify the fix by confirming that the appropriate process releases its descriptor and filesystem usage falls after cleanup.
Incorrect Answers
A:Recreate the link using the intended stable target path and verify it with readlink or ls -l could be useful for a different Linux requirement, for example when a deployment creates a relative symbolic link that stops resolving after moving its parent directory. In the current condition, the effective action is to check the path with lsof and resolve the owning process before retrying the maintenance step.
B:Enable the appropriate systemd service unit and verify the install target dependencies could be useful for a different Linux requirement, for example when a critical daemon starts manually but does not return after a Linux server reboot. In the current condition, the effective action is to check the path with lsof and resolve the owning process before retrying the maintenance step.
D:Add the user with usermod -aG and verify memberships using id or groups could be useful for a different Linux requirement, for example when a database support user needs a supplementary group but must retain their existing group memberships. In the current condition, the effective action is to check the path with lsof and resolve the owning process before retrying the maintenance step.
Question 92
A Linux host has not yet addressed this problem: Two Linux VMs intermittently disconnect because they have accidentally been assigned the same static address. What is the MOST direct failure or security risk?
- Installing a module for another kernel release may not make it loadable at startup
- Permanently disabling SELinux to bypass one incorrect label weakens broader service confinement
- Randomly disabling password quality or MFA modules to restore login can weaken intended protections
- Adding another DNS record does not resolve hosts competing for one Layer 3 address
Explanation
Correct Answer
D:Adding another DNS record does not resolve hosts competing for one Layer 3 address. This follows from the underlying Linux mechanism: duplicate IP ownership creates inconsistent ARP or neighbor resolution to different network interfaces. A targeted remedy is to locate the IP conflict with neighbor tables and packet evidence then assign unique addresses. After correction, a useful verification is that both VMs remain reachable on unique addresses and neighbor mappings remain stable.
Incorrect Answers
A:Installing a module for another kernel release may not make it loadable at startup can be a concern in another case, for example when a Linux system fails to load a required storage driver after a kernel package update. The described Linux condition instead directly exposes this risk: adding another DNS record does not resolve hosts competing for one Layer 3 address.
B:Permanently disabling SELinux to bypass one incorrect label weakens broader service confinement can be a concern in another case, for example when an Apache process reads a web file only when SELinux is set permissive despite correct traditional permissions. The described Linux condition instead directly exposes this risk: adding another DNS record does not resolve hosts competing for one Layer 3 address.
C:Randomly disabling password quality or MFA modules to restore login can weaken intended protections can be a concern in another case, for example when an authentication service fails after an administrator installed a new PAM module for login hardening. The described Linux condition instead directly exposes this risk: adding another DNS record does not resolve hosts competing for one Layer 3 address.
Question 93
For this Linux+ scenario, A vendor proposes combining proprietary redistribution restrictions with copyleft-licensed source without a review, the planned fix is to review the precise software licenses and distribution obligations before bundling the components. Why will that fix work?
- Open-source license families impose different obligations when modified or combined software is redistributed
- The Filesystem Hierarchy Standard distinguishes persistent configuration from volatile system runtime data
- Kernel drivers bind recognized hardware IDs and expose their devices when suitable modules are available
- Host-only networking intentionally limits reachability compared with bridged or routed guest networks
Explanation
Correct Answer
A:Open-source license families impose different obligations when modified or combined software is redistributed. That is the key operating principle behind the selected remediation, review the precise software licenses and distribution obligations before bundling the components. The distinction matters because assuming every free-to-download program permits unrestricted proprietary redistribution can create a licensing violation. An appropriate observable outcome is that a documented legal and technical review approves a compliant packaging and source-disclosure approach.
Incorrect Answers
B:The Filesystem Hierarchy Standard distinguishes persistent configuration from volatile system runtime data is a valid explanation for another Linux operation, such as when a compliance script stores host configuration files under a transient runtime directory that is erased at reboot. The principle here is that open-source license families impose different obligations when modified or combined software is redistributed.
C:Kernel drivers bind recognized hardware IDs and expose their devices when suitable modules are available is a valid explanation for another Linux operation, such as when an added network adapter is visible in PCI enumeration but no usable network interface appears. The principle here is that open-source license families impose different obligations when modified or combined software is redistributed.
D:Host-only networking intentionally limits reachability compared with bridged or routed guest networks is a valid explanation for another Linux operation, such as when a guest application must be accessible from the LAN but its interface uses an isolated host-only virtual network. The principle here is that open-source license families impose different obligations when modified or combined software is redistributed.
Question 94
The team proposes to quote variable expansions and use a safe array or null-delimited iteration strategy after observing A script loops through filenames containing spaces and unexpectedly splits one path into multiple arguments. Which Linux behavior supports the change?
- A Git tag identifies a specific revision independently of a branch that continues moving forward
- Unquoted shell expansion can perform word splitting and pathname expansion on embedded characters
- git stash can temporarily store working-tree and index modifications independently of branch history
- Compose describes multi-container application resources and repeatable lifecycle operations
Explanation
Correct Answer
B:Unquoted shell expansion can perform word splitting and pathname expansion on embedded characters. That is the key operating principle behind the selected remediation, quote variable expansions and use a safe array or null-delimited iteration strategy. The distinction matters because using a simple for name in $(ls) construct can corrupt filenames and process incorrect paths. An appropriate observable outcome is that a test dataset with spaces and unusual characters is processed without changing intended file boundaries.
Incorrect Answers
A:A Git tag identifies a specific revision independently of a branch that continues moving forward is a valid explanation for another Linux operation, such as when a release engineer needs to reproduce the exact automation version installed on a production server. The principle here is that unquoted shell expansion can perform word splitting and pathname expansion on embedded characters.
C:git stash can temporarily store working-tree and index modifications independently of branch history is a valid explanation for another Linux operation, such as when an administrator needs to update a feature branch while preserving unrelated uncommitted local changes. The principle here is that unquoted shell expansion can perform word splitting and pathname expansion on embedded characters.
D:Compose describes multi-container application resources and repeatable lifecycle operations is a valid explanation for another Linux operation, such as when a team has a three-service local development stack and starts its containers in the wrong dependency order. The principle here is that unquoted shell expansion can perform word splitting and pathname expansion on embedded characters.
Question 95
During a Linux service review, the team discovers: A user has been removed from a business unit but an old SSH login session still exists. Which corrective action should be selected?
- Inspect process nice levels and adjust priority with renice under approved permission controls
- Inspect apt package holds and approved pinning policy before scheduling the targeted update
- Disable or lock the account using approved tooling and separately terminate unauthorized active sessions
- Start it under a suitable persistent session manager or nohup with explicit output handling
Explanation
Correct Answer
C:Disable or lock the account using approved tooling and separately terminate unauthorized active sessions. This directly addresses the stated Linux administration condition because locking future password authentication does not always revoke every established authenticated process. If the underlying problem is ignored, assuming passwd -l instantly destroys all existing SSH sessions may leave an access window. Verify the fix by confirming that a new password authentication fails and any revoked active session is confirmed terminated.
Incorrect Answers
A:Inspect process nice levels and adjust priority with renice under approved permission controls could be useful for a different Linux requirement, for example when a process has lower priority than intended and competes with critical interactive services. In the current condition, the effective action is to disable or lock the account using approved tooling and separately terminate unauthorized active sessions.
B:Inspect apt package holds and approved pinning policy before scheduling the targeted update could be useful for a different Linux requirement, for example when an Ubuntu host needs a security fix but unattended upgrades are unintentionally held for one package. In the current condition, the effective action is to disable or lock the account using approved tooling and separately terminate unauthorized active sessions.
D:Start it under a suitable persistent session manager or nohup with explicit output handling could be useful for a different Linux requirement, for example when a command should continue running after its SSH terminal disconnects during a planned data copy. In the current condition, the effective action is to disable or lock the account using approved tooling and separately terminate unauthorized active sessions.
Question 96
An administrator chooses to use a tested if or case branch with an explicit allowed-value check and a safe default because of this Linux issue: A shell deployment script needs to choose different behavior depending on an environment variable. Which technical principle BEST explains the remediation?
- Generated code can hallucinate API names and data fields even when its syntax is valid
- Puppet agent-server communication uses certificate-based identity to retrieve managed configuration catalogs
- Infrastructure-as-code state records managed resource identities and coordinates changes to declared resources
- Bash conditional expressions and case statements select operations based on evaluated string or numeric values
Explanation
Correct Answer
D:Bash conditional expressions and case statements select operations based on evaluated string or numeric values. That is the key operating principle behind the selected remediation, use a tested if or case branch with an explicit allowed-value check and a safe default. The distinction matters because treating an unset environment variable as a valid production target can deploy to the wrong location. An appropriate observable outcome is that the script accepts documented environment names and rejects unrecognized values before changes.
Incorrect Answers
A:Generated code can hallucinate API names and data fields even when its syntax is valid is a valid explanation for another Linux operation, such as when an AI tool proposes Python code that appears to parse logs but fabricates unsupported fields. The principle here is that Bash conditional expressions and case statements select operations based on evaluated string or numeric values.
B:Puppet agent-server communication uses certificate-based identity to retrieve managed configuration catalogs is a valid explanation for another Linux operation, such as when a Linux estate managed by Puppet has a broken service because agents cannot validate the Puppet server certificate. The principle here is that Bash conditional expressions and case statements select operations based on evaluated string or numeric values.
C:Infrastructure-as-code state records managed resource identities and coordinates changes to declared resources is a valid explanation for another Linux operation, such as when a platform team uses OpenTofu to provision cloud Linux hosts but two engineers overwrite the same state file. The principle here is that Bash conditional expressions and case statements select operations based on evaluated string or numeric values.
Question 97
The team addresses A database volume group has free extents but its logical filesystem has run out of space by choosing to extend the logical volume and then grow its supported filesystem using the correct XFS or ext4 utility. Which result would verify that this remediation worked?
- lvs and df report the planned larger block allocation and filesystem capacity
- A documented legal and technical review approves a compliant packaging and source-disclosure approach
- The approved cleanup frees inodes and creating a representative new file succeeds
- The rebuilt image includes the required controller and the new kernel mounts root successfully
Explanation
Correct Answer
A:lvs and df report the planned larger block allocation and filesystem capacity. This outcome directly tests whether the Linux operation, extend the logical volume and then grow its supported filesystem using the correct XFS or ext4 utility, addresses the specified failure. The technical reason is that LVM size and filesystem size are separate layers that must both be expanded for new capacity to become usable. Without correcting the underlying issue, extending an LVM logical volume without growing the filesystem leaves application-visible free space unchanged.
Incorrect Answers
B:A documented legal and technical review approves a compliant packaging and source-disclosure approach might confirm success for a different Linux problem, such as when a vendor proposes combining proprietary redistribution restrictions with copyleft-licensed source without a review. Here the required evidence is that lvs and df report the planned larger block allocation and filesystem capacity.
C:The approved cleanup frees inodes and creating a representative new file succeeds might confirm success for a different Linux problem, such as when a small ext4 filesystem reports no space left despite df showing substantial free capacity. Here the required evidence is that lvs and df report the planned larger block allocation and filesystem capacity.
D:The rebuilt image includes the required controller and the new kernel mounts root successfully might confirm success for a different Linux problem, such as when a new storage controller was included in the boot image on the old kernel but absent in a custom kernel update. Here the required evidence is that lvs and df report the planned larger block allocation and filesystem capacity.
Question 98
An operations team leaves this Linux condition unchanged: A developer modifies a Linux automation playbook but a required new template file is missing from the proposed commit. Which adverse consequence is MOST likely?
- Accessing a list with a string key can raise a TypeError and halt automated inventory processing
- Assuming every local untracked file is automatically included in a commit can break deployments
- Modifying the source image alone may not provision environment-specific keys or packages on every new host
- Copying a shell-style brace into Python without consistent indentation will not repair block structure
Explanation
Correct Answer
B:Assuming every local untracked file is automatically included in a commit can break deployments. This follows from the underlying Linux mechanism: Git tracks staged changes in the index separately from modifications present only in the working tree. A targeted remedy is to stage the new file explicitly and inspect git status and staged diff before committing. After correction, a useful verification is that git show for the approved commit contains both the playbook edit and its required template.
Incorrect Answers
A:Accessing a list with a string key can raise a TypeError and halt automated inventory processing can be a concern in another case, for example when a Python automation script parses a JSON inventory but treats a list of hosts as a dictionary. The described Linux condition instead directly exposes this risk: assuming every local untracked file is automatically included in a commit can break deployments.
C:Modifying the source image alone may not provision environment-specific keys or packages on every new host can be a concern in another case, for example when a cloud image must install monitoring packages and authorized SSH keys on first boot. The described Linux condition instead directly exposes this risk: assuming every local untracked file is automatically included in a commit can break deployments.
D:Copying a shell-style brace into Python without consistent indentation will not repair block structure can be a concern in another case, for example when a Python function stops with an IndentationError after an engineer adds a nested condition. The described Linux condition instead directly exposes this risk: assuming every local untracked file is automatically included in a commit can break deployments.
Question 99
What test result provides the strongest evidence after the team remediates A newly installed kernel module has unresolved dependencies when loaded manually with insmod?
- nmcli and ip address show the approved address after reconnect and reboot
- The approved cleanup frees inodes and creating a representative new file succeeds
- lsmod and kernel diagnostics confirm that the module and required dependencies loaded successfully
- Both direct DNS lookup and the application's hostname resolution return the expected address
Explanation
Correct Answer
C:lsmod and kernel diagnostics confirm that the module and required dependencies loaded successfully. This outcome directly tests whether the Linux operation, use modprobe with an updated module dependency index and inspect the module dependency information, addresses the specified failure. The technical reason is that modprobe resolves declared kernel module dependencies while insmod inserts only the named object. Without correcting the underlying issue, forcing a single kernel object without its prerequisites can fail or leave the hardware unavailable.
Incorrect Answers
A:nmcli and ip address show the approved address after reconnect and reboot might confirm success for a different Linux problem, such as when a NetworkManager host loses its manually assigned IPv4 address each time the interface reconnects. Here the required evidence is that lsmod and kernel diagnostics confirm that the module and required dependencies loaded successfully.
B:The approved cleanup frees inodes and creating a representative new file succeeds might confirm success for a different Linux problem, such as when a small ext4 filesystem reports no space left despite df showing substantial free capacity. Here the required evidence is that lsmod and kernel diagnostics confirm that the module and required dependencies loaded successfully.
D:Both direct DNS lookup and the application's hostname resolution return the expected address might confirm success for a different Linux problem, such as when an application reports DNS failure but pinging its numeric service IP succeeds. Here the required evidence is that lsmod and kernel diagnostics confirm that the module and required dependencies loaded successfully.
Question 100
An administrator chooses to restore an authenticated repository signing configuration after validating the publisher's current key because of this Linux issue: A Red Hat family server cannot retrieve patched packages because a third-party repository signing key changed. Which technical principle BEST explains the remediation?
- Open file descriptors can retain underlying files after their directory names change or disappear
- A zombie has already terminated and remains only as an unreaped process table entry
- Container writable layers are not a reliable substitute for explicitly managed persistent data storage
- Signed repository metadata and package signatures help authenticate software distribution sources
Explanation
Correct Answer
D:Signed repository metadata and package signatures help authenticate software distribution sources. That is the key operating principle behind the selected remediation, restore an authenticated repository signing configuration after validating the publisher's current key. The distinction matters because disabling all signature verification to make an update work removes an important integrity check. An appropriate observable outcome is that package metadata refresh succeeds with signature checks enabled and the expected trusted signing identity.
Incorrect Answers
A:Open file descriptors can retain underlying files after their directory names change or disappear is a valid explanation for another Linux operation, such as when a log-rotation process cannot delete an archived file because another process still has it open. The principle here is that signed repository metadata and package signatures help authenticate software distribution sources.
B:A zombie has already terminated and remains only as an unreaped process table entry is a valid explanation for another Linux operation, such as when a daemon appears in a zombie state and an operator repeatedly tries to kill its PID. The principle here is that signed repository metadata and package signatures help authenticate software distribution sources.
C:Container writable layers are not a reliable substitute for explicitly managed persistent data storage is a valid explanation for another Linux operation, such as when a containerized service loses uploaded files when its container is replaced during deployment. The principle here is that signed repository metadata and package signatures help authenticate software distribution sources.