CompTIA XK0-006 Practice Test 14
Question 130
While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. 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.
- Use the absolute executable path or set a minimal explicit safe
PATH for the scheduled job rather than relying on a login profile. - Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere. - Run
rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. - Compare
command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. - Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying
chmod 777.
Explanation
Correct Answers
A:Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. This is the targeted change needed after establishing the fault. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Pair it with the supporting check: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This supplies the decisive diagnostic observation for the stated fault. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Pair this evidence with the targeted change: Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This choice concerns text filtering with grep and awk rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This choice concerns rsync source trailing slash semantics rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This choice concerns selinux avc denial versus unix mode rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 131
During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
- Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting. - Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository. - Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools.
Explanation
Correct Answer
B:Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This action corrects stable fstab identifiers without substituting an unrelated change. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Before acting, verify: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Afterward confirm: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is a change associated with ssh key authorization and root login, not a targeted repair of stable fstab identifiers. The described signal instead calls for: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
C: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 stable fstab identifiers. The described signal instead calls for: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
D:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This is a change associated with xfs online filesystem growth, not a targeted repair of stable fstab identifiers. The described signal instead calls for: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
Question 132
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 TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.
- Use a narrowly scoped
find command with explicit file type and modification-time predicate, safely printing selected paths. - Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
- Compare
id username before and after and review the difference between replacing and appending supplementary groups. - Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
Explanation
Correct Answers
A:Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. This supplies the decisive diagnostic observation for the stated fault. Same-filesystem rename provides atomic pathname replacement; piecemeal in-place writes expose partial content to concurrent readers. Pair this evidence with the targeted change: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. 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.
E:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This is the targeted change needed after establishing the fault. Same-filesystem rename provides atomic pathname replacement; piecemeal in-place writes expose partial content to concurrent readers. Pair it with the supporting check: 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.
Incorrect Answers
B:Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. This choice concerns find modified files without broad recursion rather than the required diagnosis-and-change pair for atomic file replacement and ownership. Compare the needed evidence (Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.) with the repair (Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.). 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.
C:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This choice concerns service health-check signal versus process running rather than the required diagnosis-and-change pair for atomic file replacement and ownership. Compare the needed evidence (Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.) with the repair (Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.).
D: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 atomic file replacement and ownership. Compare the needed evidence (Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.) with the repair (Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.). 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 133
During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. 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?
- Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
- Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem. - Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
- Correct the mount configuration, adding appropriate network-dependent handling or
nofail where business rules allow, and test with mount -a.
Explanation
Correct Answer
C:Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. This action corrects grub root uuid boot repair without substituting an unrelated change. The bootloader and kernel need the actual root device; changing unrelated service configuration cannot fix an invalid root identifier. Before acting, verify: From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. Afterward confirm: The installed kernel boots from the intended root filesystem without emergency root-not-found failures. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This is a change associated with bonded nic failover detection, not a targeted repair of grub root uuid boot repair. The described signal instead calls for: Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
B:Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This is a change associated with luks2 encrypted block-volume opening, not a targeted repair of grub root uuid boot repair. The described signal instead calls for: Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.
D:Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. This is a change associated with corrupted fstab mount at boot, not a targeted repair of grub root uuid boot repair. The described signal instead calls for: Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.
Question 134
During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module. - Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. - Compare
lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.
Explanation
Correct 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 the targeted change needed after establishing the fault. modprobe resolves module dependencies using the module index; insmod loads only the named object. Pair it with the supporting check: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This supplies the decisive diagnostic observation for the stated fault. modprobe resolves module dependencies using the module index; insmod loads only the named object. Pair this evidence with the targeted change: Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This choice concerns rebuilding early-boot driver inventory rather than the required diagnosis-and-change pair for kernel module dependency loading. Compare the needed evidence (Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.) with the repair (Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
C:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This choice concerns bash quoted positional arguments rather than the required diagnosis-and-change pair for kernel module dependency loading. Compare the needed evidence (Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.) with the repair (Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
E:Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This choice concerns ext4 logical-volume expansion rather than the required diagnosis-and-change pair for kernel module dependency loading. Compare the needed evidence (Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.) with the repair (Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
Question 135
While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. 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?
- Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Apply the approved password aging settings to the specific account with
chage and verify the new dates. - Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.
Explanation
Correct Answer
B:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This action corrects systemd journal correlation without substituting an unrelated change. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. Before acting, verify: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. Afterward confirm: systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This is a change associated with bonded nic failover detection, not a targeted repair of systemd journal correlation. The described signal instead calls for: Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
C:Apply the approved password aging settings to the specific account with chage and verify the new dates. This is a change associated with user password expiry visibility, not a targeted repair of systemd journal correlation. The described signal instead calls for: Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This is a change associated with systemd timer activation and calendar, not a targeted repair of systemd journal correlation. The described signal instead calls for: Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
Question 136
While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. 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?
- Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. - Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. - 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.
Explanation
Correct Answer
B:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This checks the mechanism behind persistent grub kernel arguments. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. Once identified, the targeted correction is: Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. Confirm by checking: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This can investigate name-resolution failure versus route failure, but the given incident points to persistent grub kernel arguments. It is not the most decisive first evidence here. The discriminating test is: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C: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 persistent grub kernel arguments. It is not the most decisive first evidence here. The discriminating test is: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 persistent grub kernel arguments. It is not the most decisive first evidence here. The discriminating test is: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 137
During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.- The same mounted XFS path shows increased available space and passes a controlled file-write test.
- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway.
Explanation
Correct Answer
B:findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. This is direct acceptance evidence for stable fstab identifiers rather than a generic process check. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. It validates the correction: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This outcome would support dns resolution versus tcp connectivity fault, but does not establish that the reported stable fstab identifiers problem is resolved. The required direct acceptance test is: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
C:The same mounted XFS path shows increased available space and passes a controlled file-write test. This outcome would support xfs online filesystem growth, but does not establish that the reported stable fstab identifiers problem is resolved. The required direct acceptance test is: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
D:The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. This outcome would support persistent networkmanager static address, but does not establish that the reported stable fstab identifiers problem is resolved. The required direct acceptance test is: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
Question 138
During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.
- Redirect both standard output and standard error explicitly using supported shell syntax, such as
>job.log 2>&1, while checking the exit status. - Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
Explanation
Correct Answers
A:Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. Pair this evidence with the targeted change: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
E:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. Pair it with the supporting check: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.
Incorrect Answers
B:Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This choice concerns shell redirection stderr capture rather than the required diagnosis-and-change pair for git history rewrite on shared branch. Compare the needed evidence (Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.) with the repair (Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.). Scenario context: During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. 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 choice concerns ci pipeline test gate before deployment rather than the required diagnosis-and-change pair for git history rewrite on shared branch. Compare the needed evidence (Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.) with the repair (Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.).
D: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 git history rewrite on shared branch. Compare the needed evidence (Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.) with the repair (Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.).
Question 139
During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. 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?
- Timestamped events from the daemon appear in its configured journal or log destination for the test request.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
- The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
- A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
Explanation
Correct Answer
D:A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This is direct acceptance evidence for auditable configuration drift detection rather than a generic process check. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. It validates the correction: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
Incorrect Answers
A:Timestamped events from the daemon appear in its configured journal or log destination for the test request. This outcome would support filesystem hierarchy standard log location, but does not establish that the reported auditable configuration drift detection problem is resolved. The required direct acceptance test is: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
B:The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This outcome would support selinux persistent file context, but does not establish that the reported auditable configuration drift detection problem is resolved. The required direct acceptance test is: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
C:The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services. This outcome would support openscap policy scan interpretation, but does not establish that the reported auditable configuration drift detection problem is resolved. The required direct acceptance test is: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
Question 140
During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. 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?
- Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
- Inspect the conflict markers,
git diff and both parents' intended changes before staging the resolution. - Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
Explanation
Correct Answer
A:Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. This checks the mechanism behind ai-generated dependency licensing review. Generated code can introduce third-party obligations; provenance and license validation are necessary even when the code runs. Once identified, the targeted correction is: Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. Confirm by checking: The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
Incorrect Answers
B:Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. This can investigate git conflict resolution without loss, but the given incident points to ai-generated dependency licensing review. It is not the most decisive first evidence here. The discriminating test is: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. Scenario context: During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C: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 ai-generated dependency licensing review. It is not the most decisive first evidence here. The discriminating test is: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. Scenario context: During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This can investigate ai-generated shell command validation, but the given incident points to ai-generated dependency licensing review. It is not the most decisive first evidence here. The discriminating test is: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.