CompTIA XK0-006 Practice Test 48
Question 470
During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Use
findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. - Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend.
Explanation
Correct Answer
C:Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This checks the mechanism behind filesystem mount hardening options. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. Once identified, the targeted correction is: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Confirm by checking: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This can investigate inode exhaustion on linux filesystem, but the given incident points to filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
B:Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This can investigate xfs online filesystem growth, but the given incident points to filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
D:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
Question 471
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. 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?
- Insert a tightly scoped
ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. - Set an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs. - Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository. - Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
Explanation
Correct Answer
D:Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This action corrects ssh key authorization and root login without substituting an unrelated change. Disabling SSH passwords alone does not necessarily prohibit root key authentication; sshd policies must be evaluated together. Before acting, verify: Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. Afterward confirm: Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This is a change associated with stateful nftables established connections, not a targeted repair of ssh key authorization and root login. The described signal instead calls for: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This is a change associated with secure default umask for sensitive files, not a targeted repair of ssh key authorization and root login. The described signal instead calls for: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. This is a change associated with filesystem hierarchy standard log location, not a targeted repair of ssh key authorization and root login. The described signal instead calls for: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 472
While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. 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?
- Inspect the application's
sys.executable, active Python environment, pip show paths and dependency requirements. - Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. - Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.
Explanation
Correct Answer
C:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This checks the mechanism behind distribution package dependency resolution. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. Once identified, the targeted correction is: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Confirm by checking: The package manager reports a consistent transaction and the application starts with all required libraries. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This can investigate python application isolation from os packages, but the given incident points to distribution package dependency resolution. It is not the most decisive first evidence here. The discriminating test is: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 distribution package dependency resolution. It is not the most decisive first evidence here. The discriminating test is: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This can investigate local account lock versus password expiration, but the given incident points to distribution package dependency resolution. It is not the most decisive first evidence here. The discriminating test is: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 473
While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect
nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. - Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. - Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Inspect
chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.
Explanation
Correct Answer
B:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This checks the mechanism behind network interface mtu configuration. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Once identified, the targeted correction is: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. Confirm by checking: Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. This can investigate persistent networkmanager static address, but the given incident points to network interface mtu configuration. It is not the most decisive first evidence here. The discriminating test is: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to network interface mtu configuration. It is not the most decisive first evidence here. The discriminating test is: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This can investigate user password expiry visibility, but the given incident points to network interface mtu configuration. It is not the most decisive first evidence here. The discriminating test is: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 474
During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. 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.
- Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually. - Compare
systemctl is-active, is-enabled, unit install metadata and boot journal. - Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Inspect the application's
sys.executable, active Python environment, pip show paths and dependency requirements.
Explanation
Correct Answers
A:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This is the targeted change needed after establishing the fault. start activates a unit now; enable configures its installation links for automatic activation under the selected targets. Pair it with the supporting check: Compare systemctl is-active, is-enabled, unit install metadata and boot journal. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
B:Compare systemctl is-active, is-enabled, unit install metadata and boot journal. This supplies the decisive diagnostic observation for the stated fault. start activates a unit now; enable configures its installation links for automatic activation under the selected targets. Pair this evidence with the targeted change: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
C:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This choice concerns systemd journal correlation rather than the required diagnosis-and-change pair for systemd enable versus start. Compare the needed evidence (Compare systemctl is-active, is-enabled, unit install metadata and boot journal.) with the repair (Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
D:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This choice concerns dns resolution versus tcp connectivity fault rather than the required diagnosis-and-change pair for systemd enable versus start. Compare the needed evidence (Compare systemctl is-active, is-enabled, unit install metadata and boot journal.) with the repair (Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This choice concerns python application isolation from os packages rather than the required diagnosis-and-change pair for systemd enable versus start. Compare the needed evidence (Compare systemctl is-active, is-enabled, unit install metadata and boot journal.) with the repair (Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
Question 475
While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect the process PID, service unit behavior and prior journal messages around forced termination.
- Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. - Query
systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. - Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
Explanation
Correct Answer
C:Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This checks the mechanism behind systemd journal correlation. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. Once identified, the targeted correction is: Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. Confirm by checking: systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect the process PID, service unit behavior and prior journal messages around forced termination. This can investigate graceful process shutdown signal, but the given incident points to systemd journal correlation. It is not the most decisive first evidence here. The discriminating test is: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This can investigate systemd timer activation and calendar, but the given incident points to systemd journal correlation. It is not the most decisive first evidence here. The discriminating test is: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 systemd journal correlation. It is not the most decisive first evidence here. The discriminating test is: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 476
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 TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Inspect the actual argument vector by testing with a filename containing spaces and compare
"$@" with unquoted $* expansion. - Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
- Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.
Explanation
Correct Answers
A:Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. A ConfigMap is for nonsensitive configuration; a Secret is a distinct Kubernetes object but still requires access and at-rest protection. Pair it with the supporting check: Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
D:Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. A ConfigMap is for nonsensitive configuration; a Secret is a distinct Kubernetes object but still requires access and at-rest protection. Pair this evidence with the targeted change: 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:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This choice concerns opentofu plan and state protection rather than the required diagnosis-and-change pair for kubernetes configmap versus secret handling. Compare the needed evidence (Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.) with the repair (Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.).
C:Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. This choice concerns bash quoted positional arguments rather than the required diagnosis-and-change pair for kubernetes configmap versus secret handling. Compare the needed evidence (Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.) with the repair (Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.). Scenario context: 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.
E:Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. This choice concerns ssh login denied by account lock policy rather than the required diagnosis-and-change pair for kubernetes configmap versus secret handling. Compare the needed evidence (Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.) with the repair (Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.).
Question 477
During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. 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?
- Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path. - Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
Explanation
Correct Answer
A:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This action corrects bash quoted positional arguments without substituting an unrelated change. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. Before acting, verify: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Afterward confirm: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This is a change associated with tar permissions preservation on restore, not a targeted repair of bash quoted positional arguments. The described signal instead calls for: Forward arguments with "$@" to retain each original positional argument as a separate shell word. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is a change associated with file existence conditional in bash, not a targeted repair of bash quoted positional arguments. The described signal instead calls for: Forward arguments with "$@" to retain each original positional argument as a separate shell word. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. This is a change associated with kubernetes configmap versus secret handling, not a targeted repair of bash quoted positional arguments. The described signal instead calls for: Forward arguments with "$@" to retain each original positional argument as a separate shell word. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 478
While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
- Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
Explanation
Correct Answer
D:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This action corrects name-resolution failure versus route failure without substituting an unrelated change. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Before acting, verify: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Afterward confirm: The service name resolves to the intended address and both name-based and IP-based connectivity work. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 name-resolution failure versus route failure. The described signal instead calls for: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
B:Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. This is a change associated with persistent networkmanager static address, not a targeted repair of name-resolution failure versus route failure. The described signal instead calls for: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
C:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This is a change associated with bootloader versus initramfs stages, not a targeted repair of name-resolution failure versus route failure. The described signal instead calls for: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
Question 479
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. 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?
- Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
- Inspect
/proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. - Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events. - Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
Explanation
Correct Answer
D:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This checks the mechanism behind mfa for administrative shell entry. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. Once identified, the targeted correction is: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. Confirm by checking: The test user needs both permitted factors and a single stolen password cannot complete administrative login.
Incorrect Answers
A:Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. This can investigate pam password history policy, but the given incident points to mfa for administrative shell entry. It is not the most decisive first evidence here. The discriminating test is: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
B:Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. This can investigate degraded software raid detection, but the given incident points to mfa for administrative shell entry. It is not the most decisive first evidence here. The discriminating test is: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This can investigate sudo action auditing, but the given incident points to mfa for administrative shell entry. It is not the most decisive first evidence here. The discriminating test is: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 480
During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. 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?
- Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Create a project virtual environment and install pinned project requirements into that isolated environment.
- Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
- Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
Explanation
Correct Answer
B:Create a project virtual environment and install pinned project requirements into that isolated environment. This action corrects python application isolation from os packages without substituting an unrelated change. Python virtual environments isolate project packages from the operating system's Python installation. Before acting, verify: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Afterward confirm: The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
C:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This is a change associated with apt package origin pinning, not a targeted repair of python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment.
D: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 python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment.