CompTIA XK0-006 Practice Test 2
Question 10
During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Use a list of fixed executable arguments in
subprocess.run(..., shell=False, check=True) and validate allowed file paths. - Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
- Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
- Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
Explanation
Correct Answer
A:Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This action corrects python subprocess invocation safety without substituting an unrelated change. Argument-list execution without a shell avoids shell metacharacter interpretation; blindly concatenating strings risks command injection. Before acting, verify: Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. Afterward confirm: A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This is a change associated with python exception handling specificity, not a targeted repair of python subprocess invocation safety. The described signal instead calls for: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Make deployment depend on successful required build, security and integration test jobs with protected approval for production. This is a change associated with ci pipeline test gate before deployment, not a targeted repair of python subprocess invocation safety. The described signal instead calls for: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This is a change associated with thread contention versus raw cpu capacity, not a targeted repair of python subprocess invocation safety. The described signal instead calls for: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 11
During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Inspect the actual argument vector by testing with a filename containing spaces and compare
"$@" with unquoted $* expansion. - Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
- Use an explicit safe default expansion such as
${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks.
Explanation
Correct Answers
B:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This is the targeted change needed after establishing the fault. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. Pair it with the supporting check: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. This supplies the decisive diagnostic observation for the stated fault. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. Pair this evidence with the targeted change: Forward arguments with "$@" to retain each original positional argument as a separate shell word. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for bash quoted positional arguments. Compare the needed evidence (Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion.) with the repair (Forward arguments with "$@" to retain each original positional argument as a separate shell word.). Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
D:Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This choice concerns qemu overlay disk and backing file rather than the required diagnosis-and-change pair for bash quoted positional arguments. Compare the needed evidence (Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion.) with the repair (Forward arguments with "$@" to retain each original positional argument as a separate shell word.). Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
E:Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. This choice concerns bash parameter expansion default rather than the required diagnosis-and-change pair for bash quoted positional arguments. Compare the needed evidence (Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion.) with the repair (Forward arguments with "$@" to retain each original positional argument as a separate shell word.). Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
Question 12
During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- A controlled test passes filenames containing spaces intact and the called command receives the intended argument count.
- Fresh clean installations resolve the approved package set and pass the same automated startup checks.
- The expected
/dev/mapper device appears and the existing encrypted filesystem mounts with intact files. - The script handles the unset optional variable with the documented default and still fails for missing required settings.
Explanation
Correct Answer
A:A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. This is direct acceptance evidence for bash quoted positional arguments rather than a generic process check. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. It validates the correction: Forward arguments with "$@" to retain each original positional argument as a separate shell word. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Fresh clean installations resolve the approved package set and pass the same automated startup checks. This outcome would support python dependency lock reproducibility, but does not establish that the reported bash quoted positional arguments problem is resolved. The required direct acceptance test is: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
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 bash quoted positional arguments problem is resolved. The required direct acceptance test is: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
D:The script handles the unset optional variable with the documented default and still fails for missing required settings. This outcome would support bash parameter expansion default, but does not establish that the reported bash quoted positional arguments problem is resolved. The required direct acceptance test is: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
Question 13
During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Schedule the command as a one-time
at job with logged output rather than an indefinitely recurring cron entry. - Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
- Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
Explanation
Correct Answer
A:Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This action corrects process scheduling priority adjustment without substituting an unrelated change. On typical Linux scheduling, a higher nice value means lower CPU scheduling priority. Before acting, verify: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. Afterward confirm: Interactive latency improves under load while the batch job continues with a less favorable nice value. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This is a change associated with one-time versus recurring scheduling, not a targeted repair of process scheduling priority adjustment. The described signal instead calls for: Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
C:Make deployment depend on successful required build, security and integration test jobs with protected approval for production. This is a change associated with ci pipeline test gate before deployment, not a targeted repair of process scheduling priority adjustment. The described signal instead calls for: Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
D:Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. This is a change associated with container image provenance by digest, not a targeted repair of process scheduling priority adjustment. The described signal instead calls for: Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.
Question 14
While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?
- 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. - Inspect exception handling and the observed failure traceback in a controlled test run.
- Inspect the application's
sys.executable, active Python environment, pip show paths and dependency requirements.
Explanation
Correct Answer
A: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: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B: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: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect exception handling and the observed failure traceback in a controlled test run. This can investigate python exception handling specificity, 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: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This can investigate python application isolation from os packages, 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: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 15
While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. 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.
- Schedule the command as a one-time
at job with logged output rather than an indefinitely recurring cron entry. - Inspect the proposed recurrence and confirm whether
at or a one-shot systemd timer is available for the host. - Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
- Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Compare
id username before and after and review the difference between replacing and appending supplementary groups.
Explanation
Correct Answers
A:Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This is the targeted change needed after establishing the fault. Cron describes repeated schedules; at is suited to a one-time future execution when installed and permitted. Pair it with the supporting check: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. This supplies the decisive diagnostic observation for the stated fault. Cron describes repeated schedules; at is suited to a one-time future execution when installed and permitted. Pair this evidence with the targeted change: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
C:Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This choice concerns thread contention versus raw cpu capacity rather than the required diagnosis-and-change pair for one-time versus recurring scheduling. Compare the needed evidence (Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host.) with the repair (Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This choice concerns process scheduling priority adjustment rather than the required diagnosis-and-change pair for one-time versus recurring scheduling. Compare the needed evidence (Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host.) with the repair (Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Compare id username before and after and review the difference between replacing and appending supplementary groups. This choice concerns supplementary group membership append rather than the required diagnosis-and-change pair for one-time versus recurring scheduling. Compare the needed evidence (Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host.) with the repair (Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 16
During an ordinary maintenance shift on a multi-user Linux service host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. 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?
- Compare
systemctl is-active, is-enabled, unit install metadata and boot journal. - Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. - Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.
- Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events.
Explanation
Correct Answer
C:Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. This checks the mechanism behind atomic file replacement and ownership. Same-filesystem rename provides atomic pathname replacement; piecemeal in-place writes expose partial content to concurrent readers. Once identified, the targeted correction is: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. Confirm by checking: Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 atomic file replacement and ownership. It is not the most decisive first evidence here. The discriminating test is: Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The operator must identify the affected mechanism before approving changes to other services.
B:Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This can investigate find modified files without broad recursion, but the given incident points to atomic file replacement and ownership. It is not the most decisive first evidence here. The discriminating test is: Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This can investigate sudo action auditing, but the given incident points to atomic file replacement and ownership. It is not the most decisive first evidence here. The discriminating test is: Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The operator must identify the affected mechanism before approving changes to other services.
Question 17
During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?
- Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
- Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path.
Explanation
Correct Answer
B:Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This action corrects bonded nic failover detection without substituting an unrelated change. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Before acting, verify: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Afterward confirm: A planned member failure causes traffic to use a healthy link without retaining the dead member as active. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. This is a change associated with swapping-induced application latency, not a targeted repair of bonded nic failover detection. The described signal instead calls for: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
C:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is a change associated with dns resolution versus tcp connectivity fault, not a targeted repair of bonded nic failover detection. The described signal instead calls for: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
D:Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is a change associated with file existence conditional in bash, not a targeted repair of bonded nic failover detection. The described signal instead calls for: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
Question 18
During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- The installed kernel boots from the intended root filesystem without emergency root-not-found failures.
- The expected directory account resolves through
getent and an authorized login succeeds without changing local accounts. - The specified group can create the expected file while an unrelated account is denied write access.
- A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
Explanation
Correct Answer
D:A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. This is direct acceptance evidence for pam failed-login lockout configuration rather than a generic process check. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. It validates the correction: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:The installed kernel boots from the intended root filesystem without emergency root-not-found failures. This outcome would support grub root uuid boot repair, but does not establish that the reported pam failed-login lockout configuration problem is resolved. The required direct acceptance test is: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
B:The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. This outcome would support sssd central identity lookup, but does not establish that the reported pam failed-login lockout configuration problem is resolved. The required direct acceptance test is: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:The specified group can create the expected file while an unrelated account is denied write access. This outcome would support posix acl restrictive shared directory, but does not establish that the reported pam failed-login lockout configuration problem is resolved. The required direct acceptance test is: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
Question 19
While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. 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?
- Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
- The service name resolves to the intended address and both name-based and IP-based connectivity work.
lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears.- Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.
Explanation
Correct Answer
B:The service name resolves to the intended address and both name-based and IP-based connectivity work. This is direct acceptance evidence for name-resolution failure versus route failure rather than a generic process check. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. It validates the correction: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
Incorrect Answers
A:Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits. This outcome would support cpu throttling under cgroup quota, but does not establish that the reported name-resolution failure versus route failure problem is resolved. The required direct acceptance test is: The service name resolves to the intended address and both name-based and IP-based connectivity work.
C:lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears. This outcome would support kernel module dependency loading, but does not establish that the reported name-resolution failure versus route failure problem is resolved. The required direct acceptance test is: The service name resolves to the intended address and both name-based and IP-based connectivity work. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. This outcome would support network interface mtu configuration, but does not establish that the reported name-resolution failure versus route failure problem is resolved. The required direct acceptance test is: The service name resolves to the intended address and both name-based and IP-based connectivity work.
Question 20
While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Use the matching bus inventory (
lsusb for USB) and supported driver binding to inventory and initialize the adapter. - Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Set an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs. - Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository.
Explanation
Correct Answer
A:Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. This action corrects detecting pci versus usb hardware without substituting an unrelated change. PCI and USB inventory commands enumerate different buses; absence from lspci is not evidence that USB hardware is absent. Before acting, verify: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Afterward confirm: The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This is a change associated with kernel module dependency loading, not a targeted repair of detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This is a change associated with secure default umask for sensitive files, not a targeted repair of detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. This is a change associated with filesystem hierarchy standard log location, not a targeted repair of detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.