CompTIA XK0-006 Practice Test 75
Question 740
During a repeatability test on an independently built recovery environment, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. 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?
- A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
- A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains.
- A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.
- The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.
Explanation
Correct Answer
A:A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret. This is direct acceptance evidence for kubernetes configmap versus secret handling rather than a generic process check. A ConfigMap is for nonsensitive configuration; a Secret is a distinct Kubernetes object but still requires access and at-rest protection. It validates the correction: Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
Incorrect Answers
B:A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. This outcome would support rebuilding early-boot driver inventory, but does not establish that the reported kubernetes configmap versus secret handling problem is resolved. The required direct acceptance test is: A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
C:A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. This outcome would support python subprocess invocation safety, but does not establish that the reported kubernetes configmap versus secret handling problem is resolved. The required direct acceptance test is: A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
D:The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state. This outcome would support ansible idempotent package management, but does not establish that the reported kubernetes configmap versus secret handling problem is resolved. The required direct acceptance test is: A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
Question 741
During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?
- Inspect
getfacl output including the mask:: entry and #effective permissions for the named group. - Inspect exception handling and the observed failure traceback in a controlled test run.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
Explanation
Correct Answer
C:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This checks the mechanism behind ai-generated shell command validation. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. Once identified, the targeted correction is: Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. Confirm by checking: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect getfacl output including the mask:: entry and #effective permissions for the named group. This can investigate posix acl mask denies expected access, but the given incident points to ai-generated shell command validation. It is not the most decisive first evidence here. The discriminating test is: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect exception handling and the observed failure traceback in a controlled test run. This can investigate python exception handling specificity, but the given incident points to ai-generated shell command validation. It is not the most decisive first evidence here. The discriminating test is: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. This can investigate ai-generated dependency licensing review, but the given incident points to ai-generated shell command validation. It is not the most decisive first evidence here. The discriminating test is: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 742
During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Compare
id username before and after and review the difference between replacing and appending supplementary groups. - Inspect
stat -c %d for source and destination devices and confirm link creation requirements. - Inspect
chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. - Inspect SSH authentication logs, effective sshd authentication settings and
faillock or the active PAM lock records.
Explanation
Correct Answer
C:Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This checks the mechanism behind user password expiry visibility. Existing account aging values do not automatically change when global defaults are modified for future accounts. Once identified, the targeted correction is: Apply the approved password aging settings to the specific account with chage and verify the new dates. Confirm by checking: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare id username before and after and review the difference between replacing and appending supplementary groups. This can investigate supplementary group membership append, but the given incident points to user password expiry visibility. It is not the most decisive first evidence here. The discriminating test is: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect stat -c %d for source and destination devices and confirm link creation requirements. This can investigate symbolic link across filesystems, but the given incident points to user password expiry visibility. It is not the most decisive first evidence here. The discriminating test is: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This can investigate ssh login denied by account lock policy, but the given incident points to user password expiry visibility. It is not the most decisive first evidence here. The discriminating test is: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
Question 743
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. 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?
- Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.
- Inspect SSH authentication logs, effective sshd authentication settings and
faillock or the active PAM lock records. - Review
nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. - Inspect
ufw status numbered, host listeners and the approved management subnet requirement.
Explanation
Correct Answer
D:Inspect ufw status numbered, host listeners and the approved management subnet requirement. This checks the mechanism behind ufw least-privilege inbound port. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. Once identified, the targeted correction is: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. Confirm by checking: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. This can investigate openscap policy scan interpretation, but the given incident points to ufw least-privilege inbound port. It is not the most decisive first evidence here. The discriminating test is: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This can investigate ssh login denied by account lock policy, but the given incident points to ufw least-privilege inbound port. It is not the most decisive first evidence here. The discriminating test is: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This can investigate stateful nftables established connections, but the given incident points to ufw least-privilege inbound port. It is not the most decisive first evidence here. The discriminating test is: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 744
During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
- Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
Explanation
Correct Answers
C:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This is the targeted change needed after establishing the fault. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. Pair it with the supporting check: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This supplies the decisive diagnostic observation for the stated fault. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. Pair this evidence with the targeted change: Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This choice concerns sssd central identity lookup rather than the required diagnosis-and-change pair for ai-generated shell command validation. Compare the needed evidence (Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.) with the repair (Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.). Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B: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 ai-generated shell command validation. Compare the needed evidence (Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.) with the repair (Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.). Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This choice concerns python dependency lock reproducibility rather than the required diagnosis-and-change pair for ai-generated shell command validation. Compare the needed evidence (Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.) with the repair (Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.). Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 745
During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. 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?
- The selected boot entry and post-reboot
/proc/cmdline both include the intended argument, without unrelated changes. - The same mounted XFS path shows increased available space and passes a controlled file-write test.
readlink -f resolves the expected target and application access works while the link resides on another filesystem.- The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
Explanation
Correct Answer
A:The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. This is direct acceptance evidence for persistent grub kernel arguments rather than a generic process check. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. It validates the correction: 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: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B: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 persistent grub kernel arguments problem is resolved. The required direct acceptance test is: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
C:readlink -f resolves the expected target and application access works while the link resides on another filesystem. This outcome would support symbolic link across filesystems, but does not establish that the reported persistent grub kernel arguments problem is resolved. The required direct acceptance test is: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
D:The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services. This outcome would support bootloader versus initramfs stages, but does not establish that the reported persistent grub kernel arguments problem is resolved. The required direct acceptance test is: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.
Question 746
While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- 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. - Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. - Inspect the container's published-port mapping and host listening sockets with
ss -ltnp plus firewall exposure.
Explanation
Correct Answer
B:Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. This checks the mechanism behind route metrics for preferred uplink. Linux route selection weighs prefix length and metrics; a second default route is not always harmless when priorities are wrong. Once identified, the targeted correction is: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. Confirm by checking: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. 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 route metrics for preferred uplink. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This can investigate persistent grub kernel arguments, but the given incident points to route metrics for preferred uplink. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This can investigate container port publishing scope, but the given incident points to route metrics for preferred uplink. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 747
During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. 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 boot journal and
systemctl --failed for the mount unit plus fstab options and network reachability. - Use
usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. - Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
- Correct the mount configuration, adding appropriate network-dependent handling or
nofail where business rules allow, and test with mount -a. - Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
Explanation
Correct Answers
A:Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. This supplies the decisive diagnostic observation for the stated fault. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. Pair this evidence with the targeted change: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. This is the targeted change needed after establishing the fault. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. Pair it with the supporting check: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. This choice concerns supplementary group membership append rather than the required diagnosis-and-change pair for corrupted fstab mount at boot. Compare the needed evidence (Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability.) with the repair (Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. This choice concerns cpu throttling under cgroup quota rather than the required diagnosis-and-change pair for corrupted fstab mount at boot. Compare the needed evidence (Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability.) with the repair (Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This choice concerns oom-killed process root-cause analysis rather than the required diagnosis-and-change pair for corrupted fstab mount at boot. Compare the needed evidence (Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability.) with the repair (Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 748
During a forensic reproduction of the fault at a secondary Linux test site, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The installed kernel boots from the intended root filesystem without emergency root-not-found failures.
- The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.- The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
Explanation
Correct Answer
B:The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume. This is direct acceptance evidence for service health-check signal versus process running rather than a generic process check. A live process is not proof that its application endpoint can successfully serve real requests. It validates the correction: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
Incorrect Answers
A:The installed kernel boots from the intended root filesystem without emergency root-not-found failures. This outcome would support grub root uuid boot repair, but does not establish that the reported service health-check signal versus process running problem is resolved. The required direct acceptance test is: The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
C:findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. This outcome would support stable fstab identifiers, but does not establish that the reported service health-check signal versus process running problem is resolved. The required direct acceptance test is: The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:The monitoring system has continuous trend samples and also receives test asynchronous fault notifications. This outcome would support snmp polling versus traps, but does not establish that the reported service health-check signal versus process running problem is resolved. The required direct acceptance test is: The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
Question 749
During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
- Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository. - Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.
Explanation
Correct Answers
A:Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Pair this evidence with the targeted change: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
D:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Pair it with the supporting check: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
Incorrect Answers
B:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This choice concerns ai-generated dependency licensing review rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.).
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 choice concerns filesystem hierarchy standard log location rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services.
E:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This choice concerns name-resolution failure versus route failure rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services.
Question 750
During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway. df -i shows sufficient free inodes and representative small-file creation succeeds.- Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.
ip route get selects the primary next hop while the backup remains in the table for the documented failover case.
Explanation
Correct Answer
D:ip route get selects the primary next hop while the backup remains in the table for the documented failover case. This is direct acceptance evidence for route metrics for preferred uplink rather than a generic process check. Linux route selection weighs prefix length and metrics; a second default route is not always harmless when priorities are wrong. It validates the correction: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 route metrics for preferred uplink problem is resolved. The required direct acceptance test is: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.
B:df -i shows sufficient free inodes and representative small-file creation succeeds. This outcome would support inode exhaustion on linux filesystem, but does not establish that the reported route metrics for preferred uplink problem is resolved. The required direct acceptance test is: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.
C:Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. This outcome would support rsync source trailing slash semantics, but does not establish that the reported route metrics for preferred uplink problem is resolved. The required direct acceptance test is: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.