CompTIA XK0-006 Practice Test 20
Question 190
While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Inspect
cloud-init status, user-data logs, image customization stages and credential handling. - Inspect
nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. - Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.
Explanation
Correct Answer
A:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This checks the mechanism behind filesystem hierarchy standard log location. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. Once identified, the targeted correction is: Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. Confirm by checking: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Inspect cloud-init status, user-data logs, image customization stages and credential handling. This can investigate cloud-init initialization boundary, but the given incident points to filesystem hierarchy standard log location. It is not the most decisive first evidence here. The discriminating test is: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. This can investigate persistent networkmanager static address, but the given incident points to filesystem hierarchy standard log location. It is not the most decisive first evidence here. The discriminating test is: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This can investigate persistent grub kernel arguments, but the given incident points to filesystem hierarchy standard log location. It is not the most decisive first evidence here. The discriminating test is: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 191
During a repeatability test on an independently built recovery environment, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?
- Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
- Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
- Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.
- Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
Explanation
Correct Answer
A:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This checks the mechanism behind python dependency lock reproducibility. Unpinned dependency resolution can change over time; isolated, version-locked environments improve reproducibility. Once identified, the targeted correction is: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. Confirm by checking: Fresh clean installations resolve the approved package set and pass the same automated startup checks.
Incorrect Answers
B:Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. This can investigate ai-generated dependency licensing review, but the given incident points to python dependency lock reproducibility. It is not the most decisive first evidence here. The discriminating test is: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
C:Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. This can investigate atomic file replacement and ownership, but the given incident points to python dependency lock reproducibility. It is not the most decisive first evidence here. The discriminating test is: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
D:Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. This can investigate python subprocess invocation safety, but the given incident points to python dependency lock reproducibility. It is not the most decisive first evidence here. The discriminating test is: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
Question 192
During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services. Which controlled change is the most appropriate next step after verifying this failure?
- Schedule the command as a one-time
at job with logged output rather than an indefinitely recurring cron entry. - Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Use the distribution-aware package manager (
dnf on the host) with trusted configured repositories to install the package and its dependencies. - Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
Explanation
Correct Answer
A:Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This action corrects one-time versus recurring scheduling without substituting an unrelated change. Cron describes repeated schedules; at is suited to a one-time future execution when installed and permitted. Before acting, verify: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Afterward confirm: The task executes once at the planned time and is absent from subsequent recurring schedules. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This is a change associated with process scheduling priority adjustment, not a targeted repair of one-time versus recurring scheduling. The described signal instead calls for: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services.
C:Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This is a change associated with distribution package dependency resolution, not a targeted repair of one-time versus recurring scheduling. The described signal instead calls for: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services.
D:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This is a change associated with sensitive data leakage into prompts, not a targeted repair of one-time versus recurring scheduling. The described signal instead calls for: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services.
Question 193
During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect
/proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. - Compare
iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. - Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
- Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
Explanation
Correct Answer
D:Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This checks the mechanism behind dhcp lease and address conflict. Two hosts claiming the same IP can cause intermittent ARP traffic redirection regardless of link status. Once identified, the targeted correction is: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. Confirm by checking: Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal. Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This can investigate bonded nic failover detection, but the given incident points to dhcp lease and address conflict. It is not the most decisive first evidence here. The discriminating test is: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
B:Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. This can investigate high i/o wait mistaken for cpu saturation, but the given incident points to dhcp lease and address conflict. It is not the most decisive first evidence here. The discriminating test is: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This can investigate mfa for administrative shell entry, but the given incident points to dhcp lease and address conflict. It is not the most decisive first evidence here. The discriminating test is: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
Question 194
During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. - Compare
systemctl is-active, is-enabled, unit install metadata and boot journal.
Explanation
Correct Answer
C:Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This checks the mechanism behind systemd timer activation and calendar. A timer definition alone does not schedule jobs until its timer unit is active; the service unit executes the triggered task. Once identified, the targeted correction is: Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. Confirm by checking: list-timers shows an expected next trigger and a controlled firing records a successful service run. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This can investigate incorrect default gateway on dual subnet host, but the given incident points to systemd timer activation and calendar. It is not the most decisive first evidence here. The discriminating test is: Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This can investigate process scheduling priority adjustment, but the given incident points to systemd timer activation and calendar. It is not the most decisive first evidence here. The discriminating test is: Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.
D:Compare systemctl is-active, is-enabled, unit install metadata and boot journal. This can investigate systemd enable versus start, but the given incident points to systemd timer activation and calendar. It is not the most decisive first evidence here. The discriminating test is: Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.
Question 195
During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The validated script changes only the intended test paths and does not affect system security-critical directories.
- The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.
- The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
- The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
Explanation
Correct Answer
A:The validated script changes only the intended test paths and does not affect system security-critical directories. This is direct acceptance evidence for ai-generated shell command validation rather than a generic process check. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. It validates the correction: Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state. This outcome would support ansible idempotent package management, but does not establish that the reported ai-generated shell command validation problem is resolved. The required direct acceptance test is: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:The process exits normally, committed work persists, and no crash-recovery warning appears on restart. This outcome would support graceful process shutdown signal, but does not establish that the reported ai-generated shell command validation problem is resolved. The required direct acceptance test is: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks. This outcome would support ai-generated dependency licensing review, but does not establish that the reported ai-generated shell command validation problem is resolved. The required direct acceptance test is: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 196
During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect
cloud-init status, user-data logs, image customization stages and credential handling. - Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Inspect
/proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. - Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
Explanation
Correct Answer
D:Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. This checks the mechanism behind bootloader versus initramfs stages. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Once identified, the targeted correction is: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. Confirm by checking: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
Incorrect Answers
A:Inspect cloud-init status, user-data logs, image customization stages and credential handling. This can investigate cloud-init initialization boundary, but the given incident points to bootloader versus initramfs stages. It is not the most decisive first evidence here. The discriminating test is: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services.
B:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to bootloader versus initramfs stages. It is not the most decisive first evidence here. The discriminating test is: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. This can investigate degraded software raid detection, but the given incident points to bootloader versus initramfs stages. It is not the most decisive first evidence here. The discriminating test is: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services.
Question 197
During a planned automation rollout to a Linux fleet, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. The operator must identify the affected mechanism before approving changes to other services. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
- Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
- Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. - Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
Explanation
Correct Answers
B:Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. Prompt text may leave the intended trust boundary; sanitization and approved data governance are required before AI use. Pair this evidence with the targeted change: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
D:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. Prompt text may leave the intended trust boundary; sanitization and approved data governance are required before AI use. Pair it with the supporting check: Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
Incorrect Answers
A:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for sensitive data leakage into prompts. Compare the needed evidence (Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.) with the repair (Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.).
C:Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. This choice concerns default home-directory skeleton rather than the required diagnosis-and-change pair for sensitive data leakage into prompts. Compare the needed evidence (Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.) with the repair (Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.). Scenario context: During a planned automation rollout to a Linux fleet, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. This choice concerns kubernetes configmap versus secret handling rather than the required diagnosis-and-change pair for sensitive data leakage into prompts. Compare the needed evidence (Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.) with the repair (Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.).
Question 198
During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?
- Use an explicit safe default expansion such as
${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. - Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
Explanation
Correct Answer
C:Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This action corrects sssd central identity lookup without substituting an unrelated change. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Before acting, verify: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Afterward confirm: The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. This is a change associated with bash parameter expansion default, not a targeted repair of sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This is a change associated with sudo action auditing, not a targeted repair of sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is a change associated with gpg artifact signature validation, not a targeted repair of sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
Question 199
During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging.- The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.
- The expected
/dev/mapper device appears and the existing encrypted filesystem mounts with intact files. - The package manager reports a consistent transaction and the application starts with all required libraries.
Explanation
Correct Answer
D:The package manager reports a consistent transaction and the application starts with all required libraries. This is direct acceptance evidence for distribution package dependency resolution rather than a generic process check. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. It validates the correction: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. This outcome would support open deleted log consumes disk, but does not establish that the reported distribution package dependency resolution problem is resolved. The required direct acceptance test is: The package manager reports a consistent transaction and the application starts with all required libraries. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
B:The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. This outcome would support python application isolation from os packages, but does not establish that the reported distribution package dependency resolution problem is resolved. The required direct acceptance test is: The package manager reports a consistent transaction and the application starts with all required libraries.
C:The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. This outcome would support luks2 encrypted block-volume opening, but does not establish that the reported distribution package dependency resolution problem is resolved. The required direct acceptance test is: The package manager reports a consistent transaction and the application starts with all required libraries. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
Question 200
During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Inspect
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Compare
ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. - Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
- Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting. - Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
Explanation
Correct Answers
A:Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This supplies the decisive diagnostic observation for the stated fault. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Pair this evidence with the targeted change: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This is the targeted change needed after establishing the fault. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Pair it with the supporting check: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. This choice concerns host firewall rejects container port rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This choice concerns stable fstab identifiers rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This choice concerns dhcp lease and address conflict rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.