CompTIA XK0-006 Practice Test 64
Question 630
During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
- Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
- Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
- Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.
Explanation
Correct Answer
B:Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This action corrects sssd central identity lookup without substituting an unrelated change. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Before acting, verify: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Afterward confirm: The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This is a change associated with name-resolution failure versus route failure, not a targeted repair of sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
C:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This is a change associated with auditable configuration drift detection, not a targeted repair of sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
D: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 sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
Question 631
While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
- Inspect image metadata with
qemu-img info and verify the chain of backing files exists and paths resolve. - Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. - Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
- 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
B:Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. This supplies the decisive diagnostic observation for the stated fault. A qcow2 overlay contains changed blocks and depends on its referenced backing file unless converted or flattened. Pair this evidence with the targeted change: Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This is the targeted change needed after establishing the fault. A qcow2 overlay contains changed blocks and depends on its referenced backing file unless converted or flattened. Pair it with the supporting check: Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This choice concerns kvm virtual networking bridge selection rather than the required diagnosis-and-change pair for qemu overlay disk and backing file. Compare the needed evidence (Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.) with the repair (Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This choice concerns kernel module dependency loading rather than the required diagnosis-and-change pair for qemu overlay disk and backing file. Compare the needed evidence (Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.) with the repair (Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 qemu overlay disk and backing file. Compare the needed evidence (Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.) with the repair (Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 632
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 investigation should the administrator prioritize to distinguish the likely cause?
- Inspect
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. - Compare
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
Explanation
Correct Answer
A:Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This checks the mechanism behind incorrect default gateway on dual subnet host. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Once identified, the targeted correction is: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. Confirm by checking: 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
B:Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This can investigate dns resolution versus tcp connectivity fault, but the given incident points to incorrect default gateway on dual subnet host. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. 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.
C:Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. This can investigate open deleted log consumes disk, but the given incident points to incorrect default gateway on dual subnet host. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. 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.
D: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 incorrect default gateway on dual subnet host. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. 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 633
During a forensic reproduction of the fault at a secondary Linux test site, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The package manager reports a consistent transaction and the application starts with all required libraries.
- Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
- The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
- A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
Explanation
Correct Answer
C:The monitoring system has continuous trend samples and also receives test asynchronous fault notifications. This is direct acceptance evidence for snmp polling versus traps rather than a generic process check. SNMP traps are event notifications; periodic polling produces the measurements needed for capacity trends. It validates the correction: Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.
Incorrect Answers
A:The package manager reports a consistent transaction and the application starts with all required libraries. This outcome would support distribution package dependency resolution, but does not establish that the reported snmp polling versus traps problem is resolved. The required direct acceptance test is: The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
B:Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. This outcome would support swapping-induced application latency, but does not establish that the reported snmp polling versus traps problem is resolved. The required direct acceptance test is: The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
D:A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID. This outcome would support correlating service logs with host metrics, but does not establish that the reported snmp polling versus traps problem is resolved. The required direct acceptance test is: The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
Question 634
During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. - Review
nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. - Inspect
ufw status numbered, host listeners and the approved management subnet requirement. - Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
Explanation
Correct Answer
C:Inspect ufw status numbered, host listeners and the approved management subnet requirement. This checks the mechanism behind ufw least-privilege inbound port. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. Once identified, the targeted correction is: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. Confirm by checking: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent. Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This can investigate luks2 encrypted block-volume opening, but the given incident points to ufw least-privilege inbound port. It is not the most decisive first evidence here. The discriminating test is: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.
B:Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This can investigate stateful nftables established connections, but the given incident points to ufw least-privilege inbound port. It is not the most decisive first evidence here. The discriminating test is: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. This can investigate snmp polling versus traps, but the given incident points to ufw least-privilege inbound port. It is not the most decisive first evidence here. The discriminating test is: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.
Question 635
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. How should the administrator correct the underlying configuration rather than mask the symptom?
- Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. - Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
- Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
Explanation
Correct Answer
C:Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This action corrects mfa for administrative shell entry without substituting an unrelated change. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. Before acting, verify: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. Afterward confirm: The test user needs both permitted factors and a single stolen password cannot complete administrative login.
Incorrect Answers
A:Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This is a change associated with local account lock versus password expiration, not a targeted repair of mfa for administrative shell entry. The described signal instead calls for: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. 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.
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 mfa for administrative shell entry. The described signal instead calls for: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. 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.
D:Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This is a change associated with least privilege for service processes, not a targeted repair of mfa for administrative shell entry. The described signal instead calls for: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
Question 636
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. What acceptance result would show the fix actually resolves the reported failure?
- The USB device enumerates in
lsusb, binds to a driver, and exposes its intended network interface. - The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway. - A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains.
- Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
Explanation
Correct Answer
C:A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. This is direct acceptance evidence for rebuilding early-boot driver inventory rather than a generic process check. Early boot cannot use modules only present on the root disk when the driver to reach that disk is absent from initramfs. It validates the correction: 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.
Incorrect Answers
A:The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. This outcome would support detecting pci versus usb hardware, but does not establish that the reported rebuilding early-boot driver inventory problem is resolved. The required direct acceptance test is: 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.
B: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 rebuilding early-boot driver inventory problem is resolved. The required direct acceptance test is: 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.
D:Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This outcome would support dns resolution versus tcp connectivity fault, but does not establish that the reported rebuilding early-boot driver inventory problem is resolved. The required direct acceptance test is: A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains.
Question 637
During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Compare
id username before and after and review the difference between replacing and appending supplementary groups. - Inspect the process PID, service unit behavior and prior journal messages around forced termination.
- Inspect the proposed recurrence and confirm whether
at or a one-shot systemd timer is available for the host. - Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
Explanation
Correct Answer
C:Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. This checks the mechanism behind one-time versus recurring scheduling. Cron describes repeated schedules; at is suited to a one-time future execution when installed and permitted. Once identified, the targeted correction is: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Confirm by checking: The task executes once at the planned time and is absent from subsequent recurring schedules. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare id username before and after and review the difference between replacing and appending supplementary groups. This can investigate supplementary group membership append, but the given incident points to one-time versus recurring scheduling. It is not the most decisive first evidence here. The discriminating test is: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services.
B: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 one-time versus recurring scheduling. It is not the most decisive first evidence here. The discriminating test is: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services.
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 one-time versus recurring scheduling. It is not the most decisive first evidence here. The discriminating test is: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The operator must identify the affected mechanism before approving changes to other services.
Question 638
During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
- Use a narrowly scoped
find command with explicit file type and modification-time predicate, safely printing selected paths.
Explanation
Correct Answer
D:Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. This action corrects find modified files without broad recursion without substituting an unrelated change. find selects file type and timestamps using explicit predicates; recursive ls output is unsuitable for precise time filtering. Before acting, verify: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Afterward confirm: A controlled set of files at known modification times yields the expected in-scope list only. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This is a change associated with opentofu plan and state protection, not a targeted repair of find modified files without broad recursion. The described signal instead calls for: Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.
B:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This is a change associated with atomic file replacement and ownership, not a targeted repair of find modified files without broad recursion. The described signal instead calls for: Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. 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 is a change associated with container image provenance by digest, not a targeted repair of find modified files without broad recursion. The described signal instead calls for: Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.
Question 639
During a repeatability test on an independently built recovery environment, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. 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?
- A simulated connection failure yields a non-success health status and an actionable log entry.
- The script handles the unset optional variable with the documented default and still fails for missing required settings.
- Two subsequent deployments resolve the same digest and reproduce the approved package version.
- A failing producer causes the job to fail visibly instead of recording a false successful backup result.
Explanation
Correct Answer
B:The script handles the unset optional variable with the documented default and still fails for missing required settings. This is direct acceptance evidence for bash parameter expansion default rather than a generic process check. Bash ${name:-word} substitutes a default when a variable is unset or null, unlike an unguarded expansion under nounset. It validates the correction: Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. Scenario context: During a repeatability test on an independently built recovery environment, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:A simulated connection failure yields a non-success health status and an actionable log entry. This outcome would support python exception handling specificity, but does not establish that the reported bash parameter expansion default problem is resolved. The required direct acceptance test is: The script handles the unset optional variable with the documented default and still fails for missing required settings.
C:Two subsequent deployments resolve the same digest and reproduce the approved package version. This outcome would support container image provenance by digest, but does not establish that the reported bash parameter expansion default problem is resolved. The required direct acceptance test is: The script handles the unset optional variable with the documented default and still fails for missing required settings.
D:A failing producer causes the job to fail visibly instead of recording a false successful backup result. This outcome would support pipeline exit status propagation, but does not establish that the reported bash parameter expansion default problem is resolved. The required direct acceptance test is: The script handles the unset optional variable with the documented default and still fails for missing required settings.
Question 640
While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. 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.
- Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. - Apply the approved password aging settings to the specific account with
chage and verify the new dates. - Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Inspect
chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. - Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access.
Explanation
Correct Answers
B:Apply the approved password aging settings to the specific account with chage and verify the new dates. This is the targeted change needed after establishing the fault. Existing account aging values do not automatically change when global defaults are modified for future accounts. Pair it with the supporting check: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. 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 supplies the decisive diagnostic observation for the stated fault. Existing account aging values do not automatically change when global defaults are modified for future accounts. Pair this evidence with the targeted change: Apply the approved password aging settings to the specific account with chage and verify the new dates. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This choice concerns find modified files without broad recursion rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This choice concerns local account lock versus password expiration rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This choice concerns posix acl restrictive shared directory rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.