CompTIA XK0-006 Practice Test 62
Question 610
While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
- The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision.
readlink -f resolves the expected target and application access works while the link resides on another filesystem.- Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct.
- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway.
Explanation
Correct Answer
B:readlink -f resolves the expected target and application access works while the link resides on another filesystem. This is direct acceptance evidence for symbolic link across filesystems rather than a generic process check. Hard links refer to inodes within one filesystem; symbolic links store path references and can cross filesystems. It validates the correction: Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision. This outcome would support systemd enable versus start, but does not establish that the reported symbolic link across filesystems problem is resolved. The required direct acceptance test is: readlink -f resolves the expected target and application access works while the link resides on another filesystem. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct. This outcome would support atomic file replacement and ownership, but does not establish that the reported symbolic link across filesystems problem is resolved. The required direct acceptance test is: readlink -f resolves the expected target and application access works while the link resides on another filesystem. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 symbolic link across filesystems problem is resolved. The required direct acceptance test is: readlink -f resolves the expected target and application access works while the link resides on another filesystem. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 611
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scanner marks a Linux baseline noncompliant, but an operator plans to apply every suggested remediation without considering service exceptions. 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?
- Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem. - Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
- Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
- Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
Explanation
Correct Answer
B:Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. This action corrects openscap policy scan interpretation without substituting an unrelated change. Compliance tooling supplies rule evidence; blind blanket remediation can conflict with operational requirements and approved compensating controls. Before acting, verify: Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. Afterward confirm: The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
Incorrect Answers
A: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 openscap policy scan interpretation. The described signal instead calls for: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scanner marks a Linux baseline noncompliant, but an operator plans to apply every suggested remediation without considering service exceptions. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This is a change associated with auditable configuration drift detection, not a targeted repair of openscap policy scan interpretation. The described signal instead calls for: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
D:Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This is a change associated with git conflict resolution without loss, not a targeted repair of openscap policy scan interpretation. The described signal instead calls for: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
Question 612
During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. 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.
- Correct the mount configuration, adding appropriate network-dependent handling or
nofail where business rules allow, and test with mount -a. - Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Compare
ss -ltnp, container port publication, firewall counters and a remote SYN packet capture.
Explanation
Correct Answers
B:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This supplies the decisive diagnostic observation for the stated fault. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. Pair this evidence with the targeted change: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
C:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This is the targeted change needed after establishing the fault. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. Pair it with the supporting check: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. This choice concerns corrupted fstab mount at boot rather than the required diagnosis-and-change pair for inode exhaustion on linux filesystem. Compare the needed evidence (Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.) with the repair (Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.). Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
D:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This choice concerns bootloader versus initramfs stages rather than the required diagnosis-and-change pair for inode exhaustion on linux filesystem. Compare the needed evidence (Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.) with the repair (Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.). Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
E: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 inode exhaustion on linux filesystem. Compare the needed evidence (Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.) with the repair (Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.). Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
Question 613
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. What acceptance result would show the fix actually resolves the reported failure?
- Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
- Interactive latency improves under load while the batch job continues with a less favorable nice value.
- Password authentication for the account is blocked while the account UID and home files remain intact for retention.
- The task executes once at the planned time and is absent from subsequent recurring schedules.
Explanation
Correct Answer
D:The task executes once at the planned time and is absent from subsequent recurring schedules. This is direct acceptance evidence for one-time versus recurring scheduling rather than a generic process check. Cron describes repeated schedules; at is suited to a one-time future execution when installed and permitted. It validates the correction: 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.
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 one-time versus recurring scheduling problem is resolved. The required direct acceptance test is: The task executes once at the planned time and is absent from subsequent recurring schedules.
B:Interactive latency improves under load while the batch job continues with a less favorable nice value. This outcome would support process scheduling priority adjustment, but does not establish that the reported one-time versus recurring scheduling problem is resolved. The required direct acceptance test is: The task executes once at the planned time and is absent from subsequent recurring schedules.
C:Password authentication for the account is blocked while the account UID and home files remain intact for retention. This outcome would support local account lock versus password expiration, but does not establish that the reported one-time versus recurring scheduling problem is resolved. The required direct acceptance test is: The task executes once at the planned time and is absent from subsequent recurring schedules.
Question 614
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. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect the process PID, service unit behavior and prior journal messages around forced termination.
- Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.
Explanation
Correct Answer
B:Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This checks the mechanism behind process scheduling priority adjustment. On typical Linux scheduling, a higher nice value means lower CPU scheduling priority. Once identified, the targeted correction is: Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. Confirm by checking: 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
A:Inspect the process PID, service unit behavior and prior journal messages around forced termination. This can investigate graceful process shutdown signal, but the given incident points to process scheduling priority adjustment. It is not the most decisive first evidence here. The discriminating test is: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. 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: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 process scheduling priority adjustment. It is not the most decisive first evidence here. The discriminating test is: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. 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:Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This can investigate xfs online filesystem growth, but the given incident points to process scheduling priority adjustment. It is not the most decisive first evidence here. The discriminating test is: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. 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 615
During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. 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 the conflict markers,
git diff and both parents' intended changes before staging the resolution. - Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
- Inspect the distribution's PAM auth stack,
faillock --user data and authentication logs for the user and service. - Examine pipeline stage dependencies, test job exit codes and deploy
needs or equivalent gating rules.
Explanation
Correct Answer
D:Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. This checks the mechanism behind ci pipeline test gate before deployment. Deployment ordering must be conditioned on test success; executing tests without enforcing their result is not a release gate. Once identified, the targeted correction is: Make deployment depend on successful required build, security and integration test jobs with protected approval for production. Confirm by checking: An intentionally failing test blocks deployment while the successful branch passes all required gates. Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 ci pipeline test gate before deployment. It is not the most decisive first evidence here. The discriminating test is: Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. This can investigate kubernetes configmap versus secret handling, but the given incident points to ci pipeline test gate before deployment. It is not the most decisive first evidence here. The discriminating test is: Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This can investigate pam failed-login lockout configuration, but the given incident points to ci pipeline test gate before deployment. It is not the most decisive first evidence here. The discriminating test is: Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
Question 616
During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Correct the ACL mask and intended group entry narrowly using
setfacl, preserving unrelated access decisions. - Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying
chmod 777. - Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
- Apply the approved password aging settings to the specific account with
chage and verify the new dates.
Explanation
Correct Answer
B:Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This action corrects selinux avc denial versus unix mode without substituting an unrelated change. SELinux mandatory access control can deny an operation even when discretionary file modes permit it. Before acting, verify: Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. Afterward confirm: The service performs the authorized operation with the intended label and no matching AVC denial remains. Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This is a change associated with posix acl mask denies expected access, not a targeted repair of selinux avc denial versus unix mode. The described signal instead calls for: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
C: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 selinux avc denial versus unix mode. The described signal instead calls for: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
D: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 selinux avc denial versus unix mode. The described signal instead calls for: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
Question 617
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 TWO complementary steps best identify and correct this cause? Select TWO.
- Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to
/etc/shadow hashes. - 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. - Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. - Inspect the proposed recurrence and confirm whether
at or a one-shot systemd timer is available for the host.
Explanation
Correct Answers
B: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: 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.
E: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: 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
A:Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This choice concerns pam password history policy 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: 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: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: 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:Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This choice concerns local account lock versus password expiration 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: 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 618
While preparing a recovery-site Linux node for a repeatable cutover, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Compare
lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. - Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
- Inspect
nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. - Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
- Use a list of fixed executable arguments in
subprocess.run(..., shell=False, check=True) and validate allowed file paths.
Explanation
Correct Answers
B:Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. This is the targeted change needed after establishing the fault. Ad hoc ip addr mutations are transient; NetworkManager-managed hosts require persistent connection profile settings. Pair it with the supporting check: Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. 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 supplies the decisive diagnostic observation for the stated fault. Ad hoc ip addr mutations are transient; NetworkManager-managed hosts require persistent connection profile settings. Pair this evidence with the targeted change: Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. This choice concerns detecting pci versus usb hardware rather than the required diagnosis-and-change pair for persistent networkmanager static address. Compare the needed evidence (Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.) with the repair (Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This choice concerns route metrics for preferred uplink rather than the required diagnosis-and-change pair for persistent networkmanager static address. Compare the needed evidence (Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.) with the repair (Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This choice concerns python subprocess invocation safety rather than the required diagnosis-and-change pair for persistent networkmanager static address. Compare the needed evidence (Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.) with the repair (Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 619
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 TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces. - Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. - Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- 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.
Explanation
Correct Answers
C:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This supplies the decisive diagnostic observation for the stated fault. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. Pair this evidence with the targeted change: 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. 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.
E: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. This is the targeted change needed after establishing the fault. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. Pair it with the supporting check: 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.
Incorrect Answers
A:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for persistent grub kernel arguments. Compare the needed evidence (Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.) with the repair (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.). 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.
B:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This choice concerns bootloader versus initramfs stages rather than the required diagnosis-and-change pair for persistent grub kernel arguments. Compare the needed evidence (Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.) with the repair (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.). 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:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This choice concerns sensitive data leakage into prompts rather than the required diagnosis-and-change pair for persistent grub kernel arguments. Compare the needed evidence (Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.) with the repair (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.). 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 620
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 check most directly tests the fault described in this case?
- Compare
iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. - Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. - Inspect
ip route show default, ip route get for a real destination, and per-connection route metrics. - Inspect
virsh domiflist, the libvirt network type, bridge membership, and guest addressing.
Explanation
Correct Answer
B:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This checks the mechanism behind name-resolution failure versus route failure. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Once identified, the targeted correction is: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. Confirm by checking: 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.
Incorrect Answers
A: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 name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. 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.
C:Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. This can investigate route metrics for preferred uplink, but the given incident points to name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. 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:Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This can investigate kvm virtual networking bridge selection, but the given incident points to name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. 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.