CompTIA XK0-006 Practice Test 51
Question 500
While reproducing a service change on a separately provisioned Linux integration 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- Connections from unapproved interfaces fail while the intended local or management path remains functional.
- A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
- The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision.
systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events.
Explanation
Correct Answer
C:The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision. This is direct acceptance evidence for systemd enable versus start rather than a generic process check. start activates a unit now; enable configures its installation links for automatic activation under the selected targets. It validates the correction: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: While reproducing a service change on a separately provisioned Linux integration 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Connections from unapproved interfaces fail while the intended local or management path remains functional. This outcome would support container port publishing scope, but does not establish that the reported systemd enable versus start problem is resolved. The required direct acceptance test is: The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision.
B: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 systemd enable versus start problem is resolved. The required direct acceptance test is: The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision.
D:systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. This outcome would support systemd journal correlation, but does not establish that the reported systemd enable versus start problem is resolved. The required direct acceptance test is: The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision. Scenario context: While reproducing a service change on a separately provisioned Linux integration 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 501
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. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
- Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
- Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
- Run
rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. - Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.
Explanation
Correct 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 the targeted change needed after establishing the fault. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Pair it with the supporting check: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. 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.
E:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This supplies the decisive diagnostic observation for the stated fault. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Pair this evidence with the targeted change: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. 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
B:Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. This choice concerns persistent networkmanager static address rather than the required diagnosis-and-change pair for name-resolution failure versus route failure. Compare the needed evidence (Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.) with the repair (Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.). 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.
C:Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This choice concerns dhcp lease and address conflict rather than the required diagnosis-and-change pair for name-resolution failure versus route failure. Compare the needed evidence (Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.) with the repair (Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.). 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.
D:Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This choice concerns rsync source trailing slash semantics rather than the required diagnosis-and-change pair for name-resolution failure versus route failure. Compare the needed evidence (Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.) with the repair (Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.). 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.
Question 502
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 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. - Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.
- Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. - Inspect the distribution's PAM auth stack,
faillock --user data and authentication logs for the user and service.
Explanation
Correct Answer
B:Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. This checks the mechanism behind tls server certificate name mismatch. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. Once identified, the targeted correction is: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. Confirm by checking: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
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 tls server certificate name mismatch. It is not the most decisive first evidence here. The discriminating test is: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. Scenario context: 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.
C: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 tls server certificate name mismatch. It is not the most decisive first evidence here. The discriminating test is: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. Scenario context: 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.
D:Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This can investigate pam failed-login lockout configuration, but the given incident points to tls server certificate name mismatch. It is not the most decisive first evidence here. The discriminating test is: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. Scenario context: 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.
Question 503
During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?
- A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
- The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
- The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
Explanation
Correct Answer
A:A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This is direct acceptance evidence for auditable configuration drift detection rather than a generic process check. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. It validates the correction: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
Incorrect Answers
B:The monitoring system has continuous trend samples and also receives test asynchronous fault notifications. This outcome would support snmp polling versus traps, but does not establish that the reported auditable configuration drift detection problem is resolved. The required direct acceptance test is: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
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 auditable configuration drift detection problem is resolved. The required direct acceptance test is: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
D:The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services. This outcome would support openscap policy scan interpretation, but does not establish that the reported auditable configuration drift detection problem is resolved. The required direct acceptance test is: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
Question 504
During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path. - Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. - Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
Explanation
Correct Answer
B:Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This action corrects pam failed-login lockout configuration without substituting an unrelated change. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. Before acting, verify: Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. Afterward confirm: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 pam failed-login lockout configuration. The described signal instead calls for: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This is a change associated with sudo action auditing, not a targeted repair of pam failed-login lockout configuration. The described signal instead calls for: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock 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 pam failed-login lockout configuration. The described signal instead calls for: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 505
During a forensic reproduction of the fault at a secondary Linux test site, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. 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?
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
- Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
- Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
Explanation
Correct Answer
C:Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This action corrects thread contention versus raw cpu capacity without substituting an unrelated change. Serial lock contention limits parallelism even when total machine CPU capacity is available. Before acting, verify: Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. Afterward confirm: Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
Incorrect Answers
A:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is a change associated with dns resolution versus tcp connectivity fault, not a targeted repair of thread contention versus raw cpu capacity. The described signal instead calls for: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
B:Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This is a change associated with cpu throttling under cgroup quota, not a targeted repair of thread contention versus raw cpu capacity. The described signal instead calls for: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
D:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This is a change associated with ai-generated dependency licensing review, not a targeted repair of thread contention versus raw cpu capacity. The described signal instead calls for: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
Question 506
During a planned automation rollout to a Linux fleet, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. 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 task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
- Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.
Explanation
Correct Answers
B:Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. Ansible state modules support idempotent convergence; arbitrary repeated shell installers do not inherently preserve it. Pair this evidence with the targeted change: Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.
E:Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset. Ansible state modules support idempotent convergence; arbitrary repeated shell installers do not inherently preserve it. Pair it with the supporting check: Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
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 ansible idempotent package management. Compare the needed evidence (Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.) with the repair (Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.).
C:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for ansible idempotent package management. Compare the needed evidence (Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.) with the repair (Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.).
D:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This choice concerns auditable configuration drift detection rather than the required diagnosis-and-change pair for ansible idempotent package management. Compare the needed evidence (Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.) with the repair (Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.).
Question 507
During a production incident affecting a Linux application node, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. 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?
- Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
- Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
- Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
- Set an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs.
Explanation
Correct Answer
A:Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. This action corrects path mtu black-hole in vpn link without substituting an unrelated change. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. Before acting, verify: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. Afterward confirm: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.
Incorrect Answers
B:Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This is a change associated with dhcp lease and address conflict, not a targeted repair of path mtu black-hole in vpn link. The described signal instead calls for: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
C:Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This is a change associated with thread contention versus raw cpu capacity, not a targeted repair of path mtu black-hole in vpn link. The described signal instead calls for: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
D: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 path mtu black-hole in vpn link. The described signal instead calls for: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. Scenario context: During a production incident affecting a Linux application node, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The operator must identify the affected mechanism before approving changes to other services.
Question 508
While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. 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?
lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint.mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete.- A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears.
Explanation
Correct Answer
A:lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. This is direct acceptance evidence for ext4 logical-volume expansion rather than a generic process check. Filesystem expansion cannot consume unallocated VG extents until the underlying logical volume provides that capacity. It validates the correction: Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. This outcome would support degraded software raid detection, but does not establish that the reported ext4 logical-volume expansion problem is resolved. The required direct acceptance test is: lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. This outcome would support gpg artifact signature validation, but does not establish that the reported ext4 logical-volume expansion problem is resolved. The required direct acceptance test is: lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears. This outcome would support kernel module dependency loading, but does not establish that the reported ext4 logical-volume expansion problem is resolved. The required direct acceptance test is: lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 509
During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Examine pipeline stage dependencies, test job exit codes and deploy
needs or equivalent gating rules. - Inspect
getfacl output including the mask:: entry and #effective permissions for the named group. - Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.
- Inspect the actual argument vector by testing with a filename containing spaces and compare
"$@" with unquoted $* expansion.
Explanation
Correct Answer
C:Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. This checks the mechanism behind git history rewrite on shared branch. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. Once identified, the targeted correction is: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. Confirm by checking: Other contributors can fetch the agreed release head without unexpected rewritten public commits.
Incorrect Answers
A:Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. This can investigate ci pipeline test gate before deployment, but the given incident points to git history rewrite on shared branch. It is not the most decisive first evidence here. The discriminating test is: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Scenario context: During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect getfacl output including the mask:: entry and #effective permissions for the named group. This can investigate posix acl mask denies expected access, but the given incident points to git history rewrite on shared branch. It is not the most decisive first evidence here. The discriminating test is: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Scenario context: During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. This can investigate bash quoted positional arguments, but the given incident points to git history rewrite on shared branch. It is not the most decisive first evidence here. The discriminating test is: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Scenario context: During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 510
While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. 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
nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events. - Compare
lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.
Explanation
Correct Answer
B:Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This checks the mechanism behind xfs online filesystem growth. XFS online growth uses xfs_growfs; resize2fs is for ext-family filesystems, not XFS. Once identified, the targeted correction is: Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. Confirm by checking: The same mounted XFS path shows increased available space and passes a controlled file-write test. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. 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 xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. 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 xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This can investigate ext4 logical-volume expansion, but the given incident points to xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.