CompTIA XK0-006 Practice Test 23
Question 220
While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. 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?
- Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
- Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually. - Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
Explanation
Correct Answer
C:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This action corrects atomic file replacement and ownership without substituting an unrelated change. Same-filesystem rename provides atomic pathname replacement; piecemeal in-place writes expose partial content to concurrent readers. Before acting, verify: Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. Afterward confirm: Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. This is a change associated with symbolic link across filesystems, not a targeted repair of atomic file replacement and ownership. The described signal instead calls for: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
B:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This is a change associated with systemd enable versus start, not a targeted repair of atomic file replacement and ownership. The described signal instead calls for: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. 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 is a change associated with sensitive data leakage into prompts, not a targeted repair of atomic file replacement and ownership. The described signal instead calls for: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
Question 221
During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect boot journal and
systemctl --failed for the mount unit plus fstab options and network reachability. - Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. - Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure. - Inspect exception handling and the observed failure traceback in a controlled test run.
Explanation
Correct Answer
C:Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This checks the mechanism behind oom-killed process root-cause analysis. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. Once identified, the targeted correction is: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. Confirm by checking: Peak workload completes without an OOM kill and memory utilization remains within the approved budget. Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. This can investigate corrupted fstab mount at boot, but the given incident points to oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.
B:Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This can investigate dhcp lease and address conflict, but the given incident points to oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.
D: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 oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.
Question 222
While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. 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 known fixture yields the correct count for target records while excluding headers and unrelated numeric fields.
- The task executes once at the planned time and is absent from subsequent recurring schedules.
id in the new session includes both the old supplemental groups and the newly granted group.- Password authentication for the account is blocked while the account UID and home files remain intact for retention.
Explanation
Correct Answer
C:id in the new session includes both the old supplemental groups and the newly granted group. This is direct acceptance evidence for supplementary group membership append rather than a generic process check. -G sets the supplementary-group list; -aG appends without removing existing groups. It validates the correction: Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. This outcome would support text filtering with grep and awk, but does not establish that the reported supplementary group membership append problem is resolved. The required direct acceptance test is: id in the new session includes both the old supplemental groups and the newly granted group. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:The task executes once at the planned time and is absent from subsequent recurring schedules. This outcome would support one-time versus recurring scheduling, but does not establish that the reported supplementary group membership append problem is resolved. The required direct acceptance test is: id in the new session includes both the old supplemental groups and the newly granted group. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 supplementary group membership append problem is resolved. The required direct acceptance test is: id in the new session includes both the old supplemental groups and the newly granted group. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 223
During a forensic reproduction of the fault at a secondary Linux test site, A microservice sometimes returns HTTP 503, but centralized logs lack host identity and timestamps are unsynchronized, so events cannot be correlated. 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?
- Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting. - Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
- Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
- Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
Explanation
Correct Answer
B:Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This action corrects correlating service logs with host metrics without substituting an unrelated change. Time alignment and common identifiers enable diagnosis across distributed logs; raw unlabelled messages are hard to connect. Before acting, verify: Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. Afterward confirm: A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
Incorrect Answers
A:Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This is a change associated with stable fstab identifiers, not a targeted repair of correlating service logs with host metrics. The described signal instead calls for: Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A microservice sometimes returns HTTP 503, but centralized logs lack host identity and timestamps are unsynchronized, so events cannot be correlated. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. This is a change associated with slo burn-rate alert selection, not a targeted repair of correlating service logs with host metrics. The described signal instead calls for: Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
D:Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This is a change associated with high i/o wait mistaken for cpu saturation, not a targeted repair of correlating service logs with host metrics. The described signal instead calls for: Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
Question 224
During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. 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.
- Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. - Inspect the container's published-port mapping and host listening sockets with
ss -ltnp plus firewall exposure. - Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.
Explanation
Correct Answers
B:Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This supplies the decisive diagnostic observation for the stated fault. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. Pair this evidence with the targeted change: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
E:Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. This is the targeted change needed after establishing the fault. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. Pair it with the supporting check: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 container port publishing scope. Compare the needed evidence (Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.) with the repair (Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
C:Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. This choice concerns container image provenance by digest rather than the required diagnosis-and-change pair for container port publishing scope. Compare the needed evidence (Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.) with the repair (Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
D:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This choice concerns git history rewrite on shared branch rather than the required diagnosis-and-change pair for container port publishing scope. Compare the needed evidence (Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.) with the repair (Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
Question 225
During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. 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.
- Redirect both standard output and standard error explicitly using supported shell syntax, such as
>job.log 2>&1, while checking the exit status. - Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. - Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
- Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
- Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.
Explanation
Correct Answers
A:Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This is the targeted change needed after establishing the fault. > redirects file descriptor 1; 2>&1 redirects stderr to stdout's current destination when ordered correctly. Pair it with the supporting check: Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.
C:Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This supplies the decisive diagnostic observation for the stated fault. > redirects file descriptor 1; 2>&1 redirects stderr to stdout's current destination when ordered correctly. Pair this evidence with the targeted change: Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B: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 shell redirection stderr capture. Compare the needed evidence (Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.) with the repair (Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.
D:Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. This choice concerns container image provenance by digest rather than the required diagnosis-and-change pair for shell redirection stderr capture. Compare the needed evidence (Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.) with the repair (Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.
E:Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for shell redirection stderr capture. Compare the needed evidence (Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.) with the repair (Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.
Question 226
During a production incident affecting a Linux application node, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. 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 monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
- The service performs the authorized operation with the intended label and no matching AVC denial remains.
- A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold.
Explanation
Correct Answer
D:A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold. This is direct acceptance evidence for ssh login denied by account lock policy rather than a generic process check. An authentication lockout policy can reject access independently of the validity of a provided SSH public key. It validates the correction: Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.
Incorrect Answers
A:The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume. This outcome would support service health-check signal versus process running, but does not establish that the reported ssh login denied by account lock policy problem is resolved. The required direct acceptance test is: A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold.
B:The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This outcome would support selinux persistent file context, but does not establish that the reported ssh login denied by account lock policy problem is resolved. The required direct acceptance test is: A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold.
C:The service performs the authorized operation with the intended label and no matching AVC denial remains. This outcome would support selinux avc denial versus unix mode, but does not establish that the reported ssh login denied by account lock policy problem is resolved. The required direct acceptance test is: A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold.
Question 227
While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. 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?
id in the new session includes both the old supplemental groups and the newly granted group.lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging.readlink -f resolves the expected target and application access works while the link resides on another filesystem.- The same mounted XFS path shows increased available space and passes a controlled file-write test.
Explanation
Correct Answer
B:lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. This is direct acceptance evidence for open deleted log consumes disk rather than a generic process check. An unlinked file occupies storage until its last open file descriptor is closed. It validates the correction: Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:id in the new session includes both the old supplemental groups and the newly granted group. This outcome would support supplementary group membership append, but does not establish that the reported open deleted log consumes disk problem is resolved. The required direct acceptance test is: lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 open deleted log consumes disk problem is resolved. The required direct acceptance test is: lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 open deleted log consumes disk problem is resolved. The required direct acceptance test is: lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 228
During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access. - Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.
- Inspect
getfacl, directory mode, ACL mask and the required group principals. - Use the distribution-aware package manager (
dnf on the host) with trusted configured repositories to install the package and its dependencies. - Assign the correct persistent SELinux file-context mapping with
semanage fcontext and apply it using restorecon instead of disabling SELinux.
Explanation
Correct Answers
A:Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This is the targeted change needed after establishing the fault. ACLs extend permissions to named users/groups without granting access to every user on the host. Pair it with the supporting check: Inspect getfacl, directory mode, ACL mask and the required group principals. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect getfacl, directory mode, ACL mask and the required group principals. This supplies the decisive diagnostic observation for the stated fault. ACLs extend permissions to named users/groups without granting access to every user on the host. Pair this evidence with the targeted change: Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. This choice concerns tls server certificate name mismatch rather than the required diagnosis-and-change pair for posix acl restrictive shared directory. Compare the needed evidence (Inspect getfacl, directory mode, ACL mask and the required group principals.) with the repair (Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.). Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
D:Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This choice concerns distribution package dependency resolution rather than the required diagnosis-and-change pair for posix acl restrictive shared directory. Compare the needed evidence (Inspect getfacl, directory mode, ACL mask and the required group principals.) with the repair (Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.). Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
E:Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. This choice concerns selinux persistent file context rather than the required diagnosis-and-change pair for posix acl restrictive shared directory. Compare the needed evidence (Inspect getfacl, directory mode, ACL mask and the required group principals.) with the repair (Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.). Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
Question 229
While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. 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?
- Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
- Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module. - Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
Explanation
Correct Answer
C:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This action corrects rebuilding early-boot driver inventory without substituting an unrelated change. Early boot cannot use modules only present on the root disk when the driver to reach that disk is absent from initramfs. Before acting, verify: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Afterward confirm: A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This is a change associated with kernel module dependency loading, not a targeted repair of rebuilding early-boot driver inventory. The described signal instead calls for: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This is a change associated with kvm virtual networking bridge selection, not a targeted repair of rebuilding early-boot driver inventory. The described signal instead calls for: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This is a change associated with inode exhaustion on linux filesystem, not a targeted repair of rebuilding early-boot driver inventory. The described signal instead calls for: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 230
During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- The service performs the authorized operation with the intended label and no matching AVC denial remains.
- The device enumerates with the new kernel and logs show successful module initialization without signature errors.
ip route get selects the primary next hop while the backup remains in the table for the documented failover case.- The installed kernel boots from the intended root filesystem without emergency root-not-found failures.
Explanation
Correct Answer
B:The device enumerates with the new kernel and logs show successful module initialization without signature errors. This is direct acceptance evidence for missing storage driver after kernel update rather than a generic process check. Kernel modules must match the running kernel ABI and any enforced module-signature policy. It validates the correction: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
Incorrect Answers
A:The service performs the authorized operation with the intended label and no matching AVC denial remains. This outcome would support selinux avc denial versus unix mode, but does not establish that the reported missing storage driver after kernel update problem is resolved. The required direct acceptance test is: The device enumerates with the new kernel and logs show successful module initialization without signature errors.
C:ip route get selects the primary next hop while the backup remains in the table for the documented failover case. This outcome would support route metrics for preferred uplink, but does not establish that the reported missing storage driver after kernel update problem is resolved. The required direct acceptance test is: The device enumerates with the new kernel and logs show successful module initialization without signature errors. Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
D: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 missing storage driver after kernel update problem is resolved. The required direct acceptance test is: The device enumerates with the new kernel and logs show successful module initialization without signature errors.