CompTIA XK0-006 Practice Test 61
Question 600
During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
- Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
- Inspect
/proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. - Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
Explanation
Correct Answer
C:Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This checks the mechanism behind bonded nic failover detection. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Once identified, the targeted correction is: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. Confirm by checking: A planned member failure causes traffic to use a healthy link without retaining the dead member as active. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This can investigate path mtu black-hole in vpn link, but the given incident points to bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
B:Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. This can investigate correlating service logs with host metrics, but the given incident points to bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
D:Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This can investigate shell redirection stderr capture, but the given incident points to bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
Question 601
During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Compare
ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. - Compare
uname -r, modinfo for target kernels, dmesg and module build/signing status. - Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
- Inspect
getfacl output including the mask:: entry and #effective permissions for the named group.
Explanation
Correct Answer
D:Inspect getfacl output including the mask:: entry and #effective permissions for the named group. This checks the mechanism behind posix acl mask denies expected access. The POSIX ACL mask limits effective rights for named users/groups and group-class entries even when their raw entry lists more bits. Once identified, the targeted correction is: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Confirm by checking: The intended group can read the directory and unrelated users remain denied according to the ACL. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. This can investigate host firewall rejects container port, but the given incident points to posix acl mask denies expected access. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl output including the mask:: entry and #effective permissions for the named group. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.
B:Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. This can investigate missing storage driver after kernel update, but the given incident points to posix acl mask denies expected access. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl output including the mask:: entry and #effective permissions for the named group. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.
C: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 posix acl mask denies expected access. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl output including the mask:: entry and #effective permissions for the named group. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.
Question 602
During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. 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.
- Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. - Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Inspect
/proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. - Replace the failed physical member and re-add the healthy replacement with
mdadm under an approved rebuild procedure.
Explanation
Correct Answers
D:Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. This supplies the decisive diagnostic observation for the stated fault. A mounted filesystem can remain available when RAID redundancy has been lost; array state must be checked explicitly. Pair this evidence with the targeted change: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
E:Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This is the targeted change needed after establishing the fault. A mounted filesystem can remain available when RAID redundancy has been lost; array state must be checked explicitly. Pair it with the supporting check: Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This choice concerns network interface mtu configuration rather than the required diagnosis-and-change pair for degraded software raid detection. Compare the needed evidence (Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array.) with the repair (Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
B:Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This choice concerns filesystem mount hardening options rather than the required diagnosis-and-change pair for degraded software raid detection. Compare the needed evidence (Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array.) with the repair (Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
C: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 degraded software raid detection. Compare the needed evidence (Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array.) with the repair (Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
Question 603
During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Use an explicit safe default expansion such as
${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. - Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
- Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
- Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
Explanation
Correct Answer
C:Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This action corrects pipeline exit status propagation without substituting an unrelated change. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. Before acting, verify: Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. Afterward confirm: A failing producer causes the job to fail visibly instead of recording a false successful backup result. Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. This is a change associated with bash parameter expansion default, not a targeted repair of pipeline exit status propagation. The described signal instead calls for: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This is a change associated with python exception handling specificity, not a targeted repair of pipeline exit status propagation. The described signal instead calls for: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
D: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 pipeline exit status propagation. The described signal instead calls for: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
Question 604
During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
Explanation
Correct Answer
C:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This action corrects git history rewrite on shared branch without substituting an unrelated change. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. Before acting, verify: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Afterward confirm: Other contributors can fetch the agreed release head without unexpected rewritten public commits.
Incorrect Answers
A:Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This is a change associated with process scheduling priority adjustment, not a targeted repair of git history rewrite on shared branch. The described signal instead calls for: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. Scenario context: During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This is a change associated with bash quoted positional arguments, not a targeted repair of git history rewrite on shared branch. The described signal instead calls for: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. Scenario context: During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Make deployment depend on successful required build, security and integration test jobs with protected approval for production. This is a change associated with ci pipeline test gate before deployment, not a targeted repair of git history rewrite on shared branch. The described signal instead calls for: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
Question 605
During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services. Which controlled change is the most appropriate next step after verifying this failure?
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. - Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Apply the approved password aging settings to the specific account with
chage and verify the new dates.
Explanation
Correct Answer
C:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This action corrects sudo action auditing without substituting an unrelated change. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. Before acting, verify: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Afterward confirm: A test privileged command produces an attributable event with acting user, command, time and success or failure. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is a change associated with gpg artifact signature validation, not a targeted repair of sudo action auditing. The described signal instead calls for: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.
B:Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This is a change associated with pam failed-login lockout configuration, not a targeted repair of sudo action auditing. The described signal instead calls for: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. 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 sudo action auditing. The described signal instead calls for: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.
Question 606
While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Replace the failed physical member and re-add the healthy replacement with
mdadm under an approved rebuild procedure. - Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
Explanation
Correct Answer
D:Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This action corrects tar permissions preservation on restore without substituting an unrelated change. Recovering bytes alone is insufficient for Linux services that depend on discretionary ownership and mode semantics. Before acting, verify: List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. Afterward confirm: The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This is a change associated with rsync source trailing slash semantics, not a targeted repair of tar permissions preservation on restore. The described signal instead calls for: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
B:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is a change associated with gpg artifact signature validation, not a targeted repair of tar permissions preservation on restore. The described signal instead calls for: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
C:Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This is a change associated with degraded software raid detection, not a targeted repair of tar permissions preservation on restore. The described signal instead calls for: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 607
During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
- Inspect the
if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. - Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
- Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
Explanation
Correct Answers
A:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. Generated code can introduce third-party obligations; provenance and license validation are necessary even when the code runs. Pair it with the supporting check: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
B:Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. Generated code can introduce third-party obligations; provenance and license validation are necessary even when the code runs. Pair this evidence with the targeted change: Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
Incorrect Answers
C:Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This choice concerns file existence conditional in bash rather than the required diagnosis-and-change pair for ai-generated dependency licensing review. Compare the needed evidence (Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.) with the repair (Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.). Scenario context: During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. This choice concerns graceful process shutdown signal rather than the required diagnosis-and-change pair for ai-generated dependency licensing review. Compare the needed evidence (Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.) with the repair (Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.).
E:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for ai-generated dependency licensing review. Compare the needed evidence (Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.) with the repair (Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.).
Question 608
During a production incident affecting a Linux application node, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. 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?
- Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.
- The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
- Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected.
- 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:Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall. This outcome would support host firewall rejects container port, 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:Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected. This outcome would support ssh key authorization and root login, 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.
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 609
During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services. Which controlled change is the most appropriate next step after verifying this failure?
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.
- Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
- Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module.
Explanation
Correct Answer
C:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This action corrects incorrect default gateway on dual subnet host without substituting an unrelated change. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Before acting, verify: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. Afterward confirm: The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. Scenario context: During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is a change associated with dns resolution versus tcp connectivity fault, not a targeted repair of incorrect default gateway on dual subnet host. The described signal instead calls for: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
B:Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. This is a change associated with ssh login denied by account lock policy, not a targeted repair of incorrect default gateway on dual subnet host. The described signal instead calls for: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
D:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This is a change associated with rebuilding early-boot driver inventory, not a targeted repair of incorrect default gateway on dual subnet host. The described signal instead calls for: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. Scenario context: During a production incident affecting a Linux application node, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The operator must identify the affected mechanism before approving changes to other services.
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.