CompTIA XK0-006 Practice Test 68
Question 670
During a compliance review of a production Linux endpoint, A client rejects an internal HTTPS endpoint after it was moved behind a new hostname even though the service presents a validly signed certificate for the old name. 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?
- Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
- Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
Explanation
Correct Answer
A:Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This action corrects tls server certificate name mismatch without substituting an unrelated change. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. Before acting, verify: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. Afterward confirm: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
Incorrect Answers
B:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is a change associated with gpg artifact signature validation, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
C:Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This is a change associated with mfa for administrative shell entry, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
D:Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. This is a change associated with graceful process shutdown signal, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
Question 671
During a forensic reproduction of the fault at a secondary Linux test site, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
- Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying
chmod 777. - Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
- Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
Explanation
Correct Answer
D:Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This action corrects host firewall rejects container port without substituting an unrelated change. A local listener can be healthy while network traffic is filtered upstream or by host firewall policy. Before acting, verify: Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. Afterward confirm: Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. 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 is a change associated with kvm virtual networking bridge selection, not a targeted repair of host firewall rejects container port. The described signal instead calls for: Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
B:Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This is a change associated with selinux avc denial versus unix mode, not a targeted repair of host firewall rejects container port. The described signal instead calls for: Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. This is a change associated with swapping-induced application latency, not a targeted repair of host firewall rejects container port. The described signal instead calls for: Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
Question 672
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. 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?
- Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.
- Insert a tightly scoped
ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. - Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
- Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
Explanation
Correct Answer
B:Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This action corrects stateful nftables established connections without substituting an unrelated change. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Before acting, verify: Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. Afterward confirm: Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. This is a change associated with open deleted log consumes disk, not a targeted repair of stateful nftables established connections. The described signal instead calls for: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 stateful nftables established connections. The described signal instead calls for: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This is a change associated with ufw least-privilege inbound port, not a targeted repair of stateful nftables established connections. The described signal instead calls for: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 673
During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. - Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.
Explanation
Correct Answers
B:Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This supplies the decisive diagnostic observation for the stated fault. Two hosts claiming the same IP can cause intermittent ARP traffic redirection regardless of link status. Pair this evidence with the targeted change: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
C:Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This is the targeted change needed after establishing the fault. Two hosts claiming the same IP can cause intermittent ARP traffic redirection regardless of link status. Pair it with the supporting check: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 dhcp lease and address conflict. Compare the needed evidence (Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.) with the repair (Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.). Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. 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 dhcp lease and address conflict. Compare the needed evidence (Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.) with the repair (Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.). Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
E:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for dhcp lease and address conflict. Compare the needed evidence (Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.) with the repair (Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.). Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
Question 674
During a forensic reproduction of the fault at a secondary Linux test site, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Compare process presence with an end-to-end application health-check request, response code and representative latency.
- Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
- Correlate the AVC source/target contexts and the expected service policy using
ausearch and ls -Z. - Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.
Explanation
Correct Answers
A:Compare process presence with an end-to-end application health-check request, response code and representative latency. A live process is not proof that its application endpoint can successfully serve real requests. Pair this evidence with the targeted change: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
B:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. A live process is not proof that its application endpoint can successfully serve real requests. Pair it with the supporting check: Compare process presence with an end-to-end application health-check request, response code and representative latency.
Incorrect Answers
C:Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. This choice concerns selinux avc denial versus unix mode rather than the required diagnosis-and-change pair for service health-check signal versus process running. Compare the needed evidence (Compare process presence with an end-to-end application health-check request, response code and representative latency.) with the repair (Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This choice concerns sensitive data leakage into prompts rather than the required diagnosis-and-change pair for service health-check signal versus process running. Compare the needed evidence (Compare process presence with an end-to-end application health-check request, response code and representative latency.) with the repair (Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.).
E:Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported. This choice concerns snmp polling versus traps rather than the required diagnosis-and-change pair for service health-check signal versus process running. Compare the needed evidence (Compare process presence with an end-to-end application health-check request, response code and representative latency.) with the repair (Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.).
Question 675
During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. - Inspect
chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. - Compare process presence with an end-to-end application health-check request, response code and representative latency.
- Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
Explanation
Correct Answer
A:Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This checks the mechanism behind dns resolution versus tcp connectivity fault. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Once identified, the targeted correction is: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. Confirm by checking: Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B: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 dns resolution versus tcp connectivity fault. It is not the most decisive first evidence here. The discriminating test is: Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.
C:Compare process presence with an end-to-end application health-check request, response code and representative latency. This can investigate service health-check signal versus process running, but the given incident points to dns resolution versus tcp connectivity fault. It is not the most decisive first evidence here. The discriminating test is: Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.
D:Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This can investigate path mtu black-hole in vpn link, but the given incident points to dns resolution versus tcp connectivity fault. It is not the most decisive first evidence here. The discriminating test is: Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.
Question 676
During a planned automation rollout to a Linux fleet, An infrastructure-as-code change would delete a production volume, but the team applies it without reviewing the planned resource changes or protecting state. 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.
- Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
- Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
- Inspect the conflict markers,
git diff and both parents' intended changes before staging the resolution.
Explanation
Correct Answers
B:Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. IaC tools reconcile declared and recorded state; plan review and state protection prevent unintended destructive changes. Pair this evidence with the targeted change: Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
C:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. IaC tools reconcile declared and recorded state; plan review and state protection prevent unintended destructive changes. Pair it with the supporting check: Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
Incorrect Answers
A:Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel. This choice concerns cloud-init initialization boundary rather than the required diagnosis-and-change pair for opentofu plan and state protection. Compare the needed evidence (Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.) with the repair (Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.).
D:Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This choice concerns sssd central identity lookup rather than the required diagnosis-and-change pair for opentofu plan and state protection. Compare the needed evidence (Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.) with the repair (Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.).
E:Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. This choice concerns git conflict resolution without loss rather than the required diagnosis-and-change pair for opentofu plan and state protection. Compare the needed evidence (Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.) with the repair (Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.). Scenario context: During a planned automation rollout to a Linux fleet, An infrastructure-as-code change would delete a production volume, but the team applies it without reviewing the planned resource changes or protecting state. The operator must identify the affected mechanism before approving changes to other services.
Question 677
During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.
- The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.
- Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct.
readlink -f resolves the expected target and application access works while the link resides on another filesystem.
Explanation
Correct Answer
D:readlink -f resolves the expected target and application access works while the link resides on another filesystem. This is direct acceptance evidence for symbolic link across filesystems rather than a generic process check. Hard links refer to inodes within one filesystem; symbolic links store path references and can cross filesystems. It validates the correction: Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. This outcome would support network interface mtu configuration, but does not establish that the reported symbolic link across filesystems problem is resolved. The required direct acceptance test is: readlink -f resolves the expected target and application access works while the link resides on another filesystem. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services.
B:The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. This outcome would support python application isolation from os packages, but does not establish that the reported symbolic link across filesystems problem is resolved. The required direct acceptance test is: readlink -f resolves the expected target and application access works while the link resides on another filesystem. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services.
C:Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct. This outcome would support atomic file replacement and ownership, but does not establish that the reported symbolic link across filesystems problem is resolved. The required direct acceptance test is: readlink -f resolves the expected target and application access works while the link resides on another filesystem. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services.
Question 678
During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. 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?
- Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
- A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
- The expected directory account resolves through
getent and an authorized login succeeds without changing local accounts. - Timestamped events from the daemon appear in its configured journal or log destination for the test request.
Explanation
Correct Answer
C:The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. This is direct acceptance evidence for sssd central identity lookup rather than a generic process check. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. It validates the correction: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. This outcome would support firewalld zone and interface binding, but does not establish that the reported sssd central identity lookup problem is resolved. The required direct acceptance test is: The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. This outcome would support pam failed-login lockout configuration, but does not establish that the reported sssd central identity lookup problem is resolved. The required direct acceptance test is: The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Timestamped events from the daemon appear in its configured journal or log destination for the test request. This outcome would support filesystem hierarchy standard log location, but does not establish that the reported sssd central identity lookup problem is resolved. The required direct acceptance test is: The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 679
During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Create a project virtual environment and install pinned project requirements into that isolated environment.
- Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
- Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option.
Explanation
Correct Answer
D:Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. This action corrects default home-directory skeleton without substituting an unrelated change. /etc/skel supplies initial files for new home directories; it does not retroactively change existing user homes. Before acting, verify: Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. Afterward confirm: A fresh test account receives the intended starter files without overwriting settings of existing accounts. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Create a project virtual environment and install pinned project requirements into that isolated environment. This is a change associated with python application isolation from os packages, not a targeted repair of default home-directory skeleton. The described signal instead calls for: Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
B:Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. This is a change associated with grub root uuid boot repair, not a targeted repair of default home-directory skeleton. The described signal instead calls for: Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
C: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 default home-directory skeleton. The described signal instead calls for: Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
Question 680
During a compliance review of a production Linux endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
- A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
- A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
Explanation
Correct Answer
D:A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. This is direct acceptance evidence for gpg artifact signature validation rather than a generic process check. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. It validates the correction: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
Incorrect Answers
A:A standards-compliant TLS client validates the chain and hostname without disabling certificate checks. This outcome would support tls server certificate name mismatch, but does not establish that the reported gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
B: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 gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
C: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 gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.