CompTIA Linux+ XK0-006 Practice Test 3
Question 20
A Linux host has not yet addressed this problem: A rack server reports thermal alarms while ordinary CPU usage remains low. What is the MOST direct failure or security risk?
- Retrying full sequential raw copies without a rescue map can waste remaining disk read opportunities
- Disabling CPU virtualization support can force slower emulation or prevent a requested accelerated VM
- Exposing a new TCP listener inside an isolated guest does not make it routable from the external LAN
- Raising CPU limits without inspecting a failed fan can increase thermal shutdown risk
Explanation
Correct Answer
D:Raising CPU limits without inspecting a failed fan can increase thermal shutdown risk. This follows from the underlying Linux mechanism: temperature and fan sensor telemetry can reveal chassis cooling faults independently of application CPU load. A targeted remedy is to check lm_sensors and supported BMC hardware readings using ipmitool before altering workloads. After correction, a useful verification is that sensor readings and hardware alert status return to acceptable ranges after the cooling issue is resolved.
Incorrect Answers
A:Retrying full sequential raw copies without a rescue map can waste remaining disk read opportunities can be a concern in another case, for example when a disk contains unreadable sectors and an administrator tries to copy it repeatedly using dd. The described Linux condition instead directly exposes this risk: raising CPU limits without inspecting a failed fan can increase thermal shutdown risk.
B:Disabling CPU virtualization support can force slower emulation or prevent a requested accelerated VM can be a concern in another case, for example when a Linux lab must use hardware-assisted guest virtualization instead of emulating every CPU instruction. The described Linux condition instead directly exposes this risk: raising CPU limits without inspecting a failed fan can increase thermal shutdown risk.
C:Exposing a new TCP listener inside an isolated guest does not make it routable from the external LAN can be a concern in another case, for example when a guest application must be accessible from the LAN but its interface uses an isolated host-only virtual network. The described Linux condition instead directly exposes this risk: raising CPU limits without inspecting a failed fan can increase thermal shutdown risk.
Question 21
The team addresses A containerized service loses uploaded files when its container is replaced during deployment by choosing to attach a suitable persistent named volume or bind mount and validate permissions. Which result would verify that this remediation worked?
- Files written before replacement remain present through the mounted persistent volume afterward
- id reports the new support group alongside all previously approved groups
- systemctl show and the running process command line display the new approved ExecStart
- The search lists only expected recently modified regular files and leaves all other paths intact
Explanation
Correct Answer
A:Files written before replacement remain present through the mounted persistent volume afterward. This outcome directly tests whether the Linux operation, attach a suitable persistent named volume or bind mount and validate permissions, addresses the specified failure. The technical reason is that container writable layers are not a reliable substitute for explicitly managed persistent data storage. Without correcting the underlying issue, assuming a recreated ephemeral container retains files from its removed writable layer can cause data loss.
Incorrect Answers
B:id reports the new support group alongside all previously approved groups might confirm success for a different Linux problem, such as when a database support user needs a supplementary group but must retain their existing group memberships. Here the required evidence is that files written before replacement remain present through the mounted persistent volume afterward.
C:systemctl show and the running process command line display the new approved ExecStart might confirm success for a different Linux problem, such as when a unit file has been edited on disk but systemd still launches the previous ExecStart command. Here the required evidence is that files written before replacement remain present through the mounted persistent volume afterward.
D:The search lists only expected recently modified regular files and leaves all other paths intact might confirm success for a different Linux problem, such as when a maintenance team must locate configuration files modified during an outage in a large directory tree. Here the required evidence is that files written before replacement remain present through the mounted persistent volume afterward.
Question 22
The team proposes to relocate persistent host configuration into appropriate paths under /etc and use /run only for runtime state after observing A compliance script stores host configuration files under a transient runtime directory that is erased at reboot. Which Linux behavior supports the change?
- Line-oriented text filters can match patterns and transform selected records without rewriting unrelated data
- The Filesystem Hierarchy Standard distinguishes persistent configuration from volatile system runtime data
- Disk size, partition boundary, logical volume and filesystem capacity can differ after a virtual disk grows
- Linux distributions can support multiple processor instruction sets but executable machine code must match the target architecture
Explanation
Correct Answer
B:The Filesystem Hierarchy Standard distinguishes persistent configuration from volatile system runtime data. That is the key operating principle behind the selected remediation, relocate persistent host configuration into appropriate paths under /etc and use /run only for runtime state. The distinction matters because keeping required settings only in /run may erase them when the system restarts. An appropriate observable outcome is that a reboot preserves the approved configuration in /etc and recreates only runtime state under /run.
Incorrect Answers
A:Line-oriented text filters can match patterns and transform selected records without rewriting unrelated data is a valid explanation for another Linux operation, such as when an engineer must replace only matching lines in a large configuration inventory while leaving others untouched. The principle here is that the Filesystem Hierarchy Standard distinguishes persistent configuration from volatile system runtime data.
C:Disk size, partition boundary, logical volume and filesystem capacity can differ after a virtual disk grows is a valid explanation for another Linux operation, such as when a virtualization host has a large data disk but its partitions have not been expanded after cloud resizing. The principle here is that the Filesystem Hierarchy Standard distinguishes persistent configuration from volatile system runtime data.
D:Linux distributions can support multiple processor instruction sets but executable machine code must match the target architecture is a valid explanation for another Linux operation, such as when an operations team deploys an x86_64-only binary to an AArch64 Linux host and it cannot execute. The principle here is that the Filesystem Hierarchy Standard distinguishes persistent configuration from volatile system runtime data.
Question 23
A Linux administrator is evaluating the operational consequences of A team uses a private local LLM to review an Ansible playbook and assumes no further code security check is needed. Which problem is MOST directly associated?
- Copying an unverified generated rm command to production can delete unrelated data
- Copying a shell-style brace into Python without consistent indentation will not repair block structure
- Replacing peer review with a model verdict can miss privilege escalation and idempotency mistakes
- Continuing a backup pipeline after an unnoticed failed copy can report misleading successful completion
Explanation
Correct Answer
C:Replacing peer review with a model verdict can miss privilege escalation and idempotency mistakes. This follows from the underlying Linux mechanism: running a model locally changes data exposure boundaries but does not make model output inherently accurate. A targeted remedy is to keep source review and standard static analysis despite using a locally hosted AI model. After correction, a useful verification is that independent tests and a human reviewer approve the playbook without relying solely on model confidence.
Incorrect Answers
A:Copying an unverified generated rm command to production can delete unrelated data can be a concern in another case, for example when an AI assistant generates a Bash cleanup command that includes a broad recursive deletion pattern. The described Linux condition instead directly exposes this risk: replacing peer review with a model verdict can miss privilege escalation and idempotency mistakes.
B: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: replacing peer review with a model verdict can miss privilege escalation and idempotency mistakes.
D:Continuing a backup pipeline after an unnoticed failed copy can report misleading successful completion can be a concern in another case, for example when a Bash backup script must fail safely when a command returns a nonzero exit status. The described Linux condition instead directly exposes this risk: replacing peer review with a model verdict can miss privilege escalation and idempotency mistakes.
Question 24
An administrator chooses to inspect link negotiation and bond mode requirements before modifying physical member configuration because of this Linux issue: A network team creates an interface bond but one member negotiates a different speed and loses traffic. Which technical principle BEST explains the remediation?
- Package-signature validation protects the chain of trust between repository publisher and installation
- The ACL mask can restrict effective permissions of named users and groups independent of a quick ls listing
- systemd starts services using the unit's executable definition and reports failures when that path is invalid
- Bonding behavior depends on compatible member links and correct partner negotiation where applicable
Explanation
Correct Answer
D:Bonding behavior depends on compatible member links and correct partner negotiation where applicable. That is the key operating principle behind the selected remediation, inspect link negotiation and bond mode requirements before modifying physical member configuration. The distinction matters because simply forcing all traffic over a degraded member can make availability and throughput worse. An appropriate observable outcome is that bond status and link counters show healthy members and successful failover testing.
Incorrect Answers
A:Package-signature validation protects the chain of trust between repository publisher and installation is a valid explanation for another Linux operation, such as when a repository update command fails signature verification after the package mirror changes ownership. The principle here is that bonding behavior depends on compatible member links and correct partner negotiation where applicable.
B:The ACL mask can restrict effective permissions of named users and groups independent of a quick ls listing is a valid explanation for another Linux operation, such as when a privileged script fails on a directory with ACL entries even though the POSIX mode appears to allow its user. The principle here is that bonding behavior depends on compatible member links and correct partner negotiation where applicable.
C:systemd starts services using the unit's executable definition and reports failures when that path is invalid is a valid explanation for another Linux operation, such as when a custom systemd unit fails because its configured executable was moved during a package upgrade. The principle here is that bonding behavior depends on compatible member links and correct partner negotiation where applicable.
Question 25
For this Linux+ scenario, A Linux server's RAID array is degraded after one NVMe member disappears from the device list, the planned fix is to check hardware discovery and mdadm array health before replacing and rebuilding the failed member. Why will that fix work?
- A mirrored array can continue degraded only if remaining storage members are accessible and consistent
- Kernel module ABI and early-boot driver packaging must match the kernel selected by the bootloader
- The ACL mask can restrict effective permissions of named users and groups independent of a quick ls listing
- Encapsulation overhead can make the effective path MTU smaller than the physical interface MTU
Explanation
Correct Answer
A:A mirrored array can continue degraded only if remaining storage members are accessible and consistent. That is the key operating principle behind the selected remediation, check hardware discovery and mdadm array health before replacing and rebuilding the failed member. The distinction matters because recreating the array metadata on the healthy disk can destroy information needed for recovery. An appropriate observable outcome is that the replacement member resynchronizes and array verification reports healthy redundancy.
Incorrect Answers
B:Kernel module ABI and early-boot driver packaging must match the kernel selected by the bootloader is a valid explanation for another Linux operation, such as when a Linux system fails to load a required storage driver after a kernel package update. The principle here is that a mirrored array can continue degraded only if remaining storage members are accessible and consistent.
C:The ACL mask can restrict effective permissions of named users and groups independent of a quick ls listing is a valid explanation for another Linux operation, such as when a privileged script fails on a directory with ACL entries even though the POSIX mode appears to allow its user. The principle here is that a mirrored array can continue degraded only if remaining storage members are accessible and consistent.
D:Encapsulation overhead can make the effective path MTU smaller than the physical interface MTU is a valid explanation for another Linux operation, such as when an application handshake stalls across a VPN although small pings and route lookups succeed. The principle here is that a mirrored array can continue degraded only if remaining storage members are accessible and consistent.
Question 26
For the Linux issue An operations team sends signed configuration bundles but recipients cannot verify which team published them, the administrator applies sign release artifacts with an approved GPG private key and distribute a validated corresponding public key. Which observation MOST directly confirms recovery?
- The intended permitted and denied port tests give the same results after restarting firewalld
- A recipient verifies the signature against the trusted public key and rejects a tampered bundle
- An authorized user completes the supported second factor and a password-only attempt is denied
- visudo validation passes and approved maintenance commands work only for their designated users
Explanation
Correct Answer
B:A recipient verifies the signature against the trusted public key and rejects a tampered bundle. This outcome directly tests whether the Linux operation, sign release artifacts with an approved GPG private key and distribute a validated corresponding public key, addresses the specified failure. The technical reason is that public-key signatures authenticate artifact integrity and signing identity without sharing the secret signing key. Without correcting the underlying issue, encrypting a file with a shared password does not independently establish who signed its contents.
Incorrect Answers
A:The intended permitted and denied port tests give the same results after restarting firewalld might confirm success for a different Linux problem, such as when a firewalld rule works until reboot because an engineer changed only the running configuration. Here the required evidence is that a recipient verifies the signature against the trusted public key and rejects a tampered bundle.
C:An authorized user completes the supported second factor and a password-only attempt is denied might confirm success for a different Linux problem, such as when a sensitive remote administration workflow currently accepts a stolen password without another factor. Here the required evidence is that a recipient verifies the signature against the trusted public key and rejects a tampered bundle.
D:visudo validation passes and approved maintenance commands work only for their designated users might confirm success for a different Linux problem, such as when a sudoers file edited with a text editor contains a syntax error and the administrator cannot elevate. Here the required evidence is that a recipient verifies the signature against the trusted public key and rejects a tampered bundle.
Question 27
During a Linux service review, the team discovers: A team has a three-service local development stack and starts its containers in the wrong dependency order. Which corrective action should be selected?
- Remove exposed credentials from the workflow and rotate any disclosed key under data-governance policy
- Use supported command substitution such as $(hostname) and quote the assigned expansion as appropriate
- Define a reviewed Docker or Podman Compose application with required services networks and health behavior
- Use a tested if or case branch with an explicit allowed-value check and a safe default
Explanation
Correct Answer
C:Define a reviewed Docker or Podman Compose application with required services networks and health behavior. This directly addresses the stated Linux administration condition because compose describes multi-container application resources and repeatable lifecycle operations. If the underlying problem is ignored, starting individual containers manually without dependencies can produce intermittent service startup failures. Verify the fix by confirming that the composed stack starts reproducibly and each service passes its expected readiness check.
Incorrect Answers
A:Remove exposed credentials from the workflow and rotate any disclosed key under data-governance policy could be useful for a different Linux requirement, for example when a developer pastes a production SSH private key into a public AI chatbot to debug an authentication issue. In the current condition, the effective action is to define a reviewed Docker or Podman Compose application with required services networks and health behavior.
B:Use supported command substitution such as $(hostname) and quote the assigned expansion as appropriate could be useful for a different Linux requirement, for example when a shell script needs the output of hostname without accidentally executing a literal string. In the current condition, the effective action is to define a reviewed Docker or Podman Compose application with required services networks and health behavior.
D:Use a tested if or case branch with an explicit allowed-value check and a safe default could be useful for a different Linux requirement, for example when a shell deployment script needs to choose different behavior depending on an environment variable. In the current condition, the effective action is to define a reviewed Docker or Podman Compose application with required services networks and health behavior.
Question 28
A Linux administrator is investigating the following specific issue: A platform team uses OpenTofu to provision cloud Linux hosts but two engineers overwrite the same state file. Which action BEST addresses the requirement?
- Keep source review and standard static analysis despite using a locally hosted AI model
- Verify the proposed parser against actual sanitized sample logs and add deterministic unit tests
- Use a command's exit status for success/failure and stdout for richer returned data
- Use a properly protected shared state backend with locking and reviewed plan/apply workflow
Explanation
Correct Answer
D:Use a properly protected shared state backend with locking and reviewed plan/apply workflow. This directly addresses the stated Linux administration condition because infrastructure-as-code state records managed resource identities and coordinates changes to declared resources. If the underlying problem is ignored, concurrent uncoordinated state writes can orphan infrastructure or undo another engineer's changes. Verify the fix by confirming that a second plan after an approved apply shows a consistent state with no unexpected drift.
Incorrect Answers
A:Keep source review and standard static analysis despite using a locally hosted AI model could be useful for a different Linux requirement, for example when a team uses a private local LLM to review an Ansible playbook and assumes no further code security check is needed. In the current condition, the effective action is to use a properly protected shared state backend with locking and reviewed plan/apply workflow.
B:Verify the proposed parser against actual sanitized sample logs and add deterministic unit tests could be useful for a different Linux requirement, for example when an AI tool proposes Python code that appears to parse logs but fabricates unsupported fields. In the current condition, the effective action is to use a properly protected shared state backend with locking and reviewed plan/apply workflow.
C:Use a command's exit status for success/failure and stdout for richer returned data could be useful for a different Linux requirement, for example when an administrator writes a Bash function that must output a generated hostname and separately report success or failure. In the current condition, the effective action is to use a properly protected shared state backend with locking and reviewed plan/apply workflow.
Question 29
What risk BEST explains the need to fix the following Linux situation: A network team creates an interface bond but one member negotiates a different speed and loses traffic?
- Simply forcing all traffic over a degraded member can make availability and throughput worse
- Importing an unknown key without source verification can authorize hostile packages
- Assuming every webhook notification arrives exactly once can cause duplicate disruptive remediation
- A monthly average can conceal short severe failures that affect customers
Explanation
Correct Answer
A:Simply forcing all traffic over a degraded member can make availability and throughput worse. This follows from the underlying Linux mechanism: bonding behavior depends on compatible member links and correct partner negotiation where applicable. A targeted remedy is to inspect link negotiation and bond mode requirements before modifying physical member configuration. After correction, a useful verification is that bond status and link counters show healthy members and successful failover testing.
Incorrect Answers
B:Importing an unknown key without source verification can authorize hostile packages can be a concern in another case, for example when a repository update command fails signature verification after the package mirror changes ownership. The described Linux condition instead directly exposes this risk: simply forcing all traffic over a degraded member can make availability and throughput worse.
C:Assuming every webhook notification arrives exactly once can cause duplicate disruptive remediation can be a concern in another case, for example when a webhook-based incident automation triggers several identical repair jobs for the same monitoring event. The described Linux condition instead directly exposes this risk: simply forcing all traffic over a degraded member can make availability and throughput worse.
D:A monthly average can conceal short severe failures that affect customers can be a concern in another case, for example when an API on Linux meets average latency targets but brief outages are invisible in its dashboard. The described Linux condition instead directly exposes this risk: simply forcing all traffic over a degraded member can make availability and throughput worse.
Question 30
For the Linux issue A small ext4 filesystem reports no space left despite df showing substantial free capacity, the administrator applies compare inode counts with df -i and identify directories containing huge numbers of small files. Which observation MOST directly confirms recovery?
- A controlled test preserves prior versions when a source path is unavailable
- The approved cleanup frees inodes and creating a representative new file succeeds
- A test restore reproduces the expected files and required ownership metadata
- findmnt and a controlled reboot show required filesystems mounted while the optional absent disk does not block login
Explanation
Correct Answer
B:The approved cleanup frees inodes and creating a representative new file succeeds. This outcome directly tests whether the Linux operation, compare inode counts with df -i and identify directories containing huge numbers of small files, addresses the specified failure. The technical reason is that a filesystem can exhaust its finite inode inventory before consuming all available data blocks. Without correcting the underlying issue, expanding a file by one byte is not the relevant remedy when no inode remains for new directory entries.
Incorrect Answers
A:A controlled test preserves prior versions when a source path is unavailable might confirm success for a different Linux problem, such as when a nightly rsync backup silently removes historical files when its source directory is accidentally emptied. Here the required evidence is that the approved cleanup frees inodes and creating a representative new file succeeds.
C:A test restore reproduces the expected files and required ownership metadata might confirm success for a different Linux problem, such as when a Linux operator wants to preserve permissions and timestamps while archiving a website configuration tree. Here the required evidence is that the approved cleanup frees inodes and creating a representative new file succeeds.
D:findmnt and a controlled reboot show required filesystems mounted while the optional absent disk does not block login might confirm success for a different Linux problem, such as when a host cannot boot after a stale USB disk entry in /etc/fstab becomes unavailable. Here the required evidence is that the approved cleanup frees inodes and creating a representative new file succeeds.