CompTIA Linux+ XK0-006 Practice Test 7
Question 60
After applying the relevant Linux fix for A team has a three-service local development stack and starts its containers in the wrong dependency order, which evidence BEST demonstrates success?
- Test cases confirm the parser extracts documented fields and rejects unknown input formats
- git show for the approved commit contains both the playbook edit and its required template
- A test dataset with spaces and unusual characters is processed without changing intended file boundaries
- The composed stack starts reproducibly and each service passes its expected readiness check
Explanation
Correct Answer
D:The composed stack starts reproducibly and each service passes its expected readiness check. This outcome directly tests whether the Linux operation, define a reviewed Docker or Podman Compose application with required services networks and health behavior, addresses the specified failure. The technical reason is that compose describes multi-container application resources and repeatable lifecycle operations. Without correcting the underlying issue, starting individual containers manually without dependencies can produce intermittent service startup failures.
Incorrect Answers
A:Test cases confirm the parser extracts documented fields and rejects unknown input formats might confirm success for a different Linux problem, such as when an AI tool proposes Python code that appears to parse logs but fabricates unsupported fields. Here the required evidence is that the composed stack starts reproducibly and each service passes its expected readiness check.
B:git show for the approved commit contains both the playbook edit and its required template might confirm success for a different Linux problem, such as when a developer modifies a Linux automation playbook but a required new template file is missing from the proposed commit. Here the required evidence is that the composed stack starts reproducibly and each service passes its expected readiness check.
C:A test dataset with spaces and unusual characters is processed without changing intended file boundaries might confirm success for a different Linux problem, such as when a script loops through filenames containing spaces and unexpectedly splits one path into multiple arguments. Here the required evidence is that the composed stack starts reproducibly and each service passes its expected readiness check.
Question 61
The team addresses A dual-stack Linux service accepts IPv4 connections but clients using its advertised IPv6 address time out by choosing to inspect IPv6 address assignment routes listening sockets and host firewall policy separately. Which result would verify that this remediation worked?
- Both IPv4 and IPv6 test clients connect through their intended published endpoints
- The replacement member resynchronizes and array verification reports healthy redundancy
- The intended principal gets only its required rights and unauthorized accounts remain blocked
- Inode availability returns and the service creates new logs successfully
Explanation
Correct Answer
A:Both IPv4 and IPv6 test clients connect through their intended published endpoints. This outcome directly tests whether the Linux operation, inspect IPv6 address assignment routes listening sockets and host firewall policy separately, addresses the specified failure. The technical reason is that IPv4 service reachability does not imply correct IPv6 binding and forwarding configuration. Without correcting the underlying issue, allowing only IPv4 TCP rules cannot authorize an inbound IPv6 session.
Incorrect Answers
B:The replacement member resynchronizes and array verification reports healthy redundancy might confirm success for a different Linux problem, such as when a Linux server's RAID array is degraded after one NVMe member disappears from the device list. Here the required evidence is that both IPv4 and IPv6 test clients connect through their intended published endpoints.
C:The intended principal gets only its required rights and unauthorized accounts remain blocked might confirm success for a different Linux problem, such as when a privileged script fails on a directory with ACL entries even though the POSIX mode appears to allow its user. Here the required evidence is that both IPv4 and IPv6 test clients connect through their intended published endpoints.
D:Inode availability returns and the service creates new logs successfully might confirm success for a different Linux problem, such as when a service cannot write new tiny log files even though df reports free storage blocks. Here the required evidence is that both IPv4 and IPv6 test clients connect through their intended published endpoints.
Question 62
A production Linux host has this unresolved condition: A privileged local account can reuse the same weak password indefinitely without expiry. What should the administrator do FIRST?
- Synchronize time with a trusted service and verify ticket acquisition under the existing Kerberos realm
- Apply an approved PAM password-quality and expiration policy then test compliant changes
- Assign a non-login shell and minimize the service identity's local and remote access rights
- Correct peer AllowedIPs and routing for the intended private prefixes while retaining validated public keys
Explanation
Correct Answer
B:Apply an approved PAM password-quality and expiration policy then test compliant changes. This directly addresses the stated Linux administration condition because password quality and age controls reduce risks from simple reused or long-lived credentials. If the underlying problem is ignored, checking only the length of a password leaves weak reuse and compromise risks unaddressed. Verify the fix by confirming that a test weak password is refused and an approved strong password follows documented aging rules.
Incorrect Answers
A:Synchronize time with a trusted service and verify ticket acquisition under the existing Kerberos realm could be useful for a different Linux requirement, for example when a Kerberos-enabled Linux client cannot authenticate after its system time drifts far from the domain controller. In the current condition, the effective action is to apply an approved PAM password-quality and expiration policy then test compliant changes.
C:Assign a non-login shell and minimize the service identity's local and remote access rights could be useful for a different Linux requirement, for example when an emergency support account has an interactive shell even though it should only exist for an application process. In the current condition, the effective action is to apply an approved PAM password-quality and expiration policy then test compliant changes.
D:Correct peer AllowedIPs and routing for the intended private prefixes while retaining validated public keys could be useful for a different Linux requirement, for example when two Linux hosts use WireGuard but the tunnel does not pass traffic because peer AllowedIPs are wrong. In the current condition, the effective action is to apply an approved PAM password-quality and expiration policy then test compliant changes.
Question 63
In the scenario An administrator deletes an encrypted drive's file paths and calls the confidential data irrecoverably destroyed, the chosen corrective control is to select an appropriate media-specific secure erasure or verified cryptographic erase procedure. What underlying mechanism makes this appropriate?
- A directory setgid bit causes new contained objects to inherit that directory's group under normal creation
- LUKS2 protects at-rest block content using protected volume keys that are unlocked at authorized boot or mount
- Removing directory entries does not guarantee underlying storage blocks or flash cells are unrecoverable
- SSSD caches and mediates remote identity and authentication information for Linux clients
Explanation
Correct Answer
C:Removing directory entries does not guarantee underlying storage blocks or flash cells are unrecoverable. That is the key operating principle behind the selected remediation, select an appropriate media-specific secure erasure or verified cryptographic erase procedure. The distinction matters because using a simple rm operation as a certified data sanitization process can leave recoverable confidential data. An appropriate observable outcome is that a documented sanitization report and verification meet the approved media disposal standard.
Incorrect Answers
A:A directory setgid bit causes new contained objects to inherit that directory's group under normal creation is a valid explanation for another Linux operation, such as when a shared project directory needs new files to inherit its group without making all users world-writable. The principle here is that removing directory entries does not guarantee underlying storage blocks or flash cells are unrecoverable.
B:LUKS2 protects at-rest block content using protected volume keys that are unlocked at authorized boot or mount is a valid explanation for another Linux operation, such as when a laptop holds confidential data on an unencrypted ext4 filesystem and may be stolen during travel. The principle here is that removing directory entries does not guarantee underlying storage blocks or flash cells are unrecoverable.
D:SSSD caches and mediates remote identity and authentication information for Linux clients is a valid explanation for another Linux operation, such as when a company Linux server should authenticate corporate users through an existing LDAP identity service. The principle here is that removing directory entries does not guarantee underlying storage blocks or flash cells are unrecoverable.
Question 64
A Linux administrator is investigating the following specific issue: A unit file has been edited on disk but systemd still launches the previous ExecStart command. Which action BEST addresses the requirement?
- Check the path with lsof and resolve the owning process before retrying the maintenance step
- Inspect systemctl status and journalctl -u output before modifying the service unit
- Pin deployments to an approved image digest and verify the resolved image identity
- Run systemctl daemon-reload and restart the target unit after validating its new definition
Explanation
Correct Answer
D:Run systemctl daemon-reload and restart the target unit after validating its new definition. This directly addresses the stated Linux administration condition because systemd caches unit configuration until its manager reloads changed unit metadata. If the underlying problem is ignored, restarting a unit without reloading a changed definition may continue using the old settings. Verify the fix by confirming that systemctl show and the running process command line display the new approved ExecStart.
Incorrect Answers
A:Check the path with lsof and resolve the owning process before retrying the maintenance step could be useful for a different Linux requirement, for example when a log-rotation process cannot delete an archived file because another process still has it open. In the current condition, the effective action is to run systemctl daemon-reload and restart the target unit after validating its new definition.
B:Inspect systemctl status and journalctl -u output before modifying the service unit could be useful for a different Linux requirement, for example when a custom systemd service exits immediately and supervisors cannot tell why it failed. In the current condition, the effective action is to run systemctl daemon-reload and restart the target unit after validating its new definition.
C:Pin deployments to an approved image digest and verify the resolved image identity could be useful for a different Linux requirement, for example when a developer uses a container image tag called latest and different deployments run different application builds. In the current condition, the effective action is to run systemctl daemon-reload and restart the target unit after validating its new definition.
Question 65
A Linux+ operations scenario reports: An operator needs to grow an XFS filesystem after expanding its mounted block device. Which remediation is MOST appropriate?
- Use xfs_growfs against the mounted XFS filesystem after verifying volume and device sizes
- Use tracepath and correctly scoped packet captures to investigate path MTU and fragmentation behavior
- Rebuild the distribution-specific initramfs image for the installed kernel and verify its boot entry
- Validate source availability and use a versioned destination or reviewed deletion policy before synchronization
Explanation
Correct Answer
A:Use xfs_growfs against the mounted XFS filesystem after verifying volume and device sizes. This directly addresses the stated Linux administration condition because xFS supports online growth and its resizing tool differs from ext4's resize2fs. If the underlying problem is ignored, attempting to use resize2fs on an XFS filesystem does not perform supported XFS growth. Verify the fix by confirming that xfs_info and df show expanded XFS geometry without replacing the filesystem.
Incorrect Answers
B:Use tracepath and correctly scoped packet captures to investigate path MTU and fragmentation behavior could be useful for a different Linux requirement, for example when a host can send small ICMP requests but an HTTPS transfer stalls on the WAN path. In the current condition, the effective action is to use xfs_growfs against the mounted XFS filesystem after verifying volume and device sizes.
C:Rebuild the distribution-specific initramfs image for the installed kernel and verify its boot entry could be useful for a different Linux requirement, for example when an administrator installs a kernel but forgets to deploy its matching initial RAM filesystem. In the current condition, the effective action is to use xfs_growfs against the mounted XFS filesystem after verifying volume and device sizes.
D:Validate source availability and use a versioned destination or reviewed deletion policy before synchronization could be useful for a different Linux requirement, for example when a nightly rsync backup silently removes historical files when its source directory is accidentally emptied. In the current condition, the effective action is to use xfs_growfs against the mounted XFS filesystem after verifying volume and device sizes.
Question 66
For the Linux issue An added network adapter is visible in PCI enumeration but no usable network interface appears, the administrator applies inspect lspci and dmesg then load the supported driver using modprobe after checking modinfo. Which observation MOST directly confirms recovery?
- mdadm reports both intended active mirrors and a completed synchronization with verified application reads
- The kernel binds the adapter to a compatible module and ip link lists the new interface
- A test restore reproduces the expected files and required ownership metadata
- Both guests obtain distinct identifiers and can communicate without duplicate-address alarms
Explanation
Correct Answer
B:The kernel binds the adapter to a compatible module and ip link lists the new interface. This outcome directly tests whether the Linux operation, inspect lspci and dmesg then load the supported driver using modprobe after checking modinfo, addresses the specified failure. The technical reason is that Kernel drivers bind recognized hardware IDs and expose their devices when suitable modules are available. Without correcting the underlying issue, repeatedly modifying DNS configuration cannot bring up a network device missing its kernel driver.
Incorrect Answers
A:mdadm reports both intended active mirrors and a completed synchronization with verified application reads might confirm success for a different Linux problem, such as when a degraded Linux RAID1 mirror is still running but /proc/mdstat shows only one healthy member. Here the required evidence is that the kernel binds the adapter to a compatible module and ip link lists the new interface.
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 kernel binds the adapter to a compatible module and ip link lists the new interface.
D:Both guests obtain distinct identifiers and can communicate without duplicate-address alarms might confirm success for a different Linux problem, such as when a virtualization operator clones a VM but both guest instances come up with duplicate network identities. Here the required evidence is that the kernel binds the adapter to a compatible module and ip link lists the new interface.
Question 67
What test result provides the strongest evidence after the team remediates A custom systemd service exits immediately and supervisors cannot tell why it failed?
- The batch priority matches policy while interactive request response times remain acceptable
- The search lists only expected recently modified regular files and leaves all other paths intact
- The unit starts successfully after the diagnosed failure is fixed and clean logs show normal readiness
- The approved candidate is installed and the hold state matches change policy
Explanation
Correct Answer
C:The unit starts successfully after the diagnosed failure is fixed and clean logs show normal readiness. This outcome directly tests whether the Linux operation, inspect systemctl status and journalctl -u output before modifying the service unit, addresses the specified failure. The technical reason is that systemd unit state and journal records link process exit status to activation attempts. Without correcting the underlying issue, randomly changing Restart settings can cause a crash loop while hiding the original error.
Incorrect Answers
A:The batch priority matches policy while interactive request response times remain acceptable might confirm success for a different Linux problem, such as when a process has lower priority than intended and competes with critical interactive services. Here the required evidence is that the unit starts successfully after the diagnosed failure is fixed and clean logs show normal readiness.
B: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 the unit starts successfully after the diagnosed failure is fixed and clean logs show normal readiness.
D:The approved candidate is installed and the hold state matches change policy might confirm success for a different Linux problem, such as when an Ubuntu host needs a security fix but unattended upgrades are unintentionally held for one package. Here the required evidence is that the unit starts successfully after the diagnosed failure is fixed and clean logs show normal readiness.
Question 68
An administrator chooses to separate nonsensitive settings into ConfigMaps and sensitive values into controlled Secrets with appropriate workload access because of this Linux issue: A Kubernetes service requires configuration to change without baking credentials into a container image. Which technical principle BEST explains the remediation?
- Puppet agent-server communication uses certificate-based identity to retrieve managed configuration catalogs
- External AI service prompts may cross organizational security boundaries and should not contain sensitive secrets
- Agentless Ansible can apply declarative configuration tasks over supported remote connections
- Kubernetes workload configuration and secret distribution can be managed separately from application image layers
Explanation
Correct Answer
D:Kubernetes workload configuration and secret distribution can be managed separately from application image layers. That is the key operating principle behind the selected remediation, separate nonsensitive settings into ConfigMaps and sensitive values into controlled Secrets with appropriate workload access. The distinction matters because embedding reusable production credentials inside an image can spread secrets across registries and deployments. An appropriate observable outcome is that a test Deployment consumes approved configuration and only authorized pods can read its Secret.
Incorrect Answers
A: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 Kubernetes workload configuration and secret distribution can be managed separately from application image layers.
B:External AI service prompts may cross organizational security boundaries and should not contain sensitive secrets is a valid explanation for another Linux operation, such as when a developer pastes a production SSH private key into a public AI chatbot to debug an authentication issue. The principle here is that Kubernetes workload configuration and secret distribution can be managed separately from application image layers.
C:Agentless Ansible can apply declarative configuration tasks over supported remote connections is a valid explanation for another Linux operation, such as when a fleet of twenty Linux servers needs the same SSH daemon settings without logging into each host interactively. The principle here is that Kubernetes workload configuration and secret distribution can be managed separately from application image layers.
Question 69
The team addresses An administrator wants to block a vulnerable service from being started accidentally during remediation by choosing to mask the service unit until the approved fix is complete and later unmask it deliberately. Which result would verify that this remediation worked?
- Attempts to start the masked unit are refused until change control removes the mask
- The parent performs wait or is restarted safely and the zombie entry disappears
- A reviewed package transaction completes without unresolved dependencies or service regressions
- The unit starts successfully after the diagnosed failure is fixed and clean logs show normal readiness
Explanation
Correct Answer
A:Attempts to start the masked unit are refused until change control removes the mask. This outcome directly tests whether the Linux operation, mask the service unit until the approved fix is complete and later unmask it deliberately, addresses the specified failure. The technical reason is that masking links a unit to an unavailable target so ordinary activation cannot start the service. Without correcting the underlying issue, merely disabling a unit does not prevent manual or dependency-triggered activation.
Incorrect Answers
B:The parent performs wait or is restarted safely and the zombie entry disappears might confirm success for a different Linux problem, such as when a daemon appears in a zombie state and an operator repeatedly tries to kill its PID. Here the required evidence is that attempts to start the masked unit are refused until change control removes the mask.
C:A reviewed package transaction completes without unresolved dependencies or service regressions might confirm success for a different Linux problem, such as when a package update fails because an installed library conflicts with a newly requested application version. Here the required evidence is that attempts to start the masked unit are refused until change control removes the mask.
D:The unit starts successfully after the diagnosed failure is fixed and clean logs show normal readiness might confirm success for a different Linux problem, such as when a custom systemd service exits immediately and supervisors cannot tell why it failed. Here the required evidence is that attempts to start the masked unit are refused until change control removes the mask.
Question 70
For the Linux issue A new application service should run under a noninteractive account without a home-directory login shell, the administrator applies create a dedicated system account with a non-login shell and narrowly scoped file ownership. Which observation MOST directly confirms recovery?
- The search lists only expected recently modified regular files and leaves all other paths intact
- The daemon runs under its intended UID and the account cannot start an interactive shell
- The batch priority matches policy while interactive request response times remain acceptable
- The process exits after termination and application integrity checks pass
Explanation
Correct Answer
B:The daemon runs under its intended UID and the account cannot start an interactive shell. This outcome directly tests whether the Linux operation, create a dedicated system account with a non-login shell and narrowly scoped file ownership, addresses the specified failure. The technical reason is that system and service accounts can have distinct login capabilities and UID allocation practices. Without correcting the underlying issue, running a network daemon directly as root expands the impact of application compromise.
Incorrect Answers
A: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 the daemon runs under its intended UID and the account cannot start an interactive shell.
C:The batch priority matches policy while interactive request response times remain acceptable might confirm success for a different Linux problem, such as when a process has lower priority than intended and competes with critical interactive services. Here the required evidence is that the daemon runs under its intended UID and the account cannot start an interactive shell.
D:The process exits after termination and application integrity checks pass might confirm success for a different Linux problem, such as when a runaway batch process consumes CPU and a team needs graceful shutdown before escalation. Here the required evidence is that the daemon runs under its intended UID and the account cannot start an interactive shell.