CompTIA XK0-006 Practice Test 71
Question 700
While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
- Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
- Run
rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. - Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces.
Explanation
Correct Answers
C:Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This is the targeted change needed after establishing the fault. rsync source/ dest/ copies the contents of source, while rsync source dest/ can create a source subdirectory. Pair it with the supporting check: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. 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 supplies the decisive diagnostic observation for the stated fault. rsync source/ dest/ copies the contents of source, while rsync source dest/ can create a source subdirectory. Pair this evidence with the targeted change: Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This choice concerns tar permissions preservation on restore rather than the required diagnosis-and-change pair for rsync source trailing slash semantics. Compare the needed evidence (Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.) with the repair (Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B: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 rsync source trailing slash semantics. Compare the needed evidence (Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.) with the repair (Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for rsync source trailing slash semantics. Compare the needed evidence (Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.) with the repair (Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 701
During a repeatability test on an independently built recovery environment, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. 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.
- Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.
- Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
- Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Inspect the conflict markers,
git diff and both parents' intended changes before staging the resolution. - Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
Explanation
Correct Answers
A: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.
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.
Incorrect Answers
C:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This choice concerns kernel module dependency loading 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.). Scenario context: During a repeatability test on an independently built recovery environment, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 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.). Scenario context: During a repeatability test on an independently built recovery environment, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E: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.).
Question 702
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. What targeted corrective action best addresses the underlying problem?
- Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
Explanation
Correct Answer
C:Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. This action corrects symbolic link across filesystems without substituting an unrelated change. Hard links refer to inodes within one filesystem; symbolic links store path references and can cross filesystems. Before acting, verify: Inspect stat -c %d for source and destination devices and confirm link creation requirements. Afterward confirm: 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.
Incorrect Answers
A: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 symbolic link across filesystems. The described signal instead calls for: Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
B:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is a change associated with systemd journal correlation, not a targeted repair of symbolic link across filesystems. The described signal instead calls for: Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
D: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 symbolic link across filesystems. The described signal instead calls for: Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
Question 703
While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. 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?
- Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
- Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
- Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.
Explanation
Correct Answer
A:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This action corrects bootloader versus initramfs stages without substituting an unrelated change. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Before acting, verify: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. Afterward confirm: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
Incorrect Answers
B:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This is a change associated with apt package origin pinning, not a targeted repair of bootloader versus initramfs stages. The described signal instead calls for: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
C:Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This is a change associated with persistent grub kernel arguments, not a targeted repair of bootloader versus initramfs stages. The described signal instead calls for: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
D:Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This is a change associated with quoting filenames in shell loops, not a targeted repair of bootloader versus initramfs stages. The described signal instead calls for: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 704
While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?
- Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
- Inspect representative input lines, the expected delimiter, and
awk field positions before changing the record filter. - Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. - Inspect
chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.
Explanation
Correct Answer
B:Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. This checks the mechanism behind text filtering with grep and awk. Line-wide regular-expression matches do not enforce column semantics; field-aware filtering must use the actual delimiter. Once identified, the targeted correction is: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Confirm by checking: A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This can investigate shell redirection stderr capture, but the given incident points to text filtering with grep and awk. It is not the most decisive first evidence here. The discriminating test is: Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. 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 can investigate kernel module dependency loading, but the given incident points to text filtering with grep and awk. It is not the most decisive first evidence here. The discriminating test is: Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This can investigate user password expiry visibility, but the given incident points to text filtering with grep and awk. It is not the most decisive first evidence here. The discriminating test is: Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 705
During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. 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?
- Use the absolute executable path or set a minimal explicit safe
PATH for the scheduled job rather than relying on a login profile. - Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
- Use
usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed.
Explanation
Correct Answer
B:Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This action corrects local account lock versus password expiration without substituting an unrelated change. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. Before acting, verify: Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. Afterward confirm: Password authentication for the account is blocked while the account UID and home files remain intact for retention. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. This is a change associated with path in noninteractive jobs, not a targeted repair of local account lock versus password expiration. The described signal instead calls for: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
C:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This is a change associated with apt package origin pinning, not a targeted repair of local account lock versus password expiration. The described signal instead calls for: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
D:Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. This is a change associated with supplementary group membership append, not a targeted repair of local account lock versus password expiration. The described signal instead calls for: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
Question 706
While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. 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?
- Set an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs. - Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
- Create a project virtual environment and install pinned project requirements into that isolated environment.
Explanation
Correct Answer
D:Create a project virtual environment and install pinned project requirements into that isolated environment. This action corrects python application isolation from os packages without substituting an unrelated change. Python virtual environments isolate project packages from the operating system's Python installation. Before acting, verify: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Afterward confirm: The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment.
C:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This is a change associated with apt package origin pinning, not a targeted repair of python application isolation from os packages. The described signal instead calls for: Create a project virtual environment and install pinned project requirements into that isolated environment.
Question 707
During a repeatability test on an independently built recovery environment, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?
- Examine pipeline stage dependencies, test job exit codes and deploy
needs or equivalent gating rules. - Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.
- Inspect the conflict markers,
git diff and both parents' intended changes before staging the resolution. - Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
Explanation
Correct Answer
A:Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. This checks the mechanism behind ci pipeline test gate before deployment. Deployment ordering must be conditioned on test success; executing tests without enforcing their result is not a release gate. Once identified, the targeted correction is: Make deployment depend on successful required build, security and integration test jobs with protected approval for production. Confirm by checking: An intentionally failing test blocks deployment while the successful branch passes all required gates. Scenario context: During a repeatability test on an independently built recovery environment, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. This can investigate openscap policy scan interpretation, but the given incident points to ci pipeline test gate before deployment. It is not the most decisive first evidence here. The discriminating test is: Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. Scenario context: During a repeatability test on an independently built recovery environment, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. This can investigate git conflict resolution without loss, but the given incident points to ci pipeline test gate before deployment. It is not the most decisive first evidence here. The discriminating test is: Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. Scenario context: During a repeatability test on an independently built recovery environment, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. This can investigate opentofu plan and state protection, but the given incident points to ci pipeline test gate before deployment. It is not the most decisive first evidence here. The discriminating test is: Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. Scenario context: During a repeatability test on an independently built recovery environment, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 708
During a planned automation rollout to a Linux fleet, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. 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
umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. - Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
- Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.
- Inspect the conflict markers,
git diff and both parents' intended changes before staging the resolution.
Explanation
Correct Answer
D:Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. This checks the mechanism behind git conflict resolution without loss. Git conflicts require semantic reconciliation of competing edits, not automatically discarding a whole side. Once identified, the targeted correction is: Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. Confirm by checking: The merge commit retains both intended settings and tests pass without unresolved conflict markers. Scenario context: During a planned automation rollout to a Linux fleet, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. This can investigate secure default umask for sensitive files, but the given incident points to git conflict resolution without loss. It is not the most decisive first evidence here. The discriminating test is: Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. Scenario context: During a planned automation rollout to a Linux fleet, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. This can investigate sensitive data leakage into prompts, but the given incident points to git conflict resolution without loss. It is not the most decisive first evidence here. The discriminating test is: Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. Scenario context: During a planned automation rollout to a Linux fleet, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. This can investigate git history rewrite on shared branch, but the given incident points to git conflict resolution without loss. It is not the most decisive first evidence here. The discriminating test is: Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. Scenario context: During a planned automation rollout to a Linux fleet, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The operator must identify the affected mechanism before approving changes to other services.
Question 709
During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. 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?
- Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
- Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
- Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
Explanation
Correct Answer
B:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This action corrects name-resolution failure versus route failure without substituting an unrelated change. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Before acting, verify: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Afterward confirm: The service name resolves to the intended address and both name-based and IP-based connectivity work. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.
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 is a change associated with cloud-init initialization boundary, not a targeted repair of name-resolution failure versus route failure. The described signal instead calls for: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
C:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This is a change associated with xfs online filesystem growth, not a targeted repair of name-resolution failure versus route failure. The described signal instead calls for: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.
D:Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This is a change associated with network interface mtu configuration, not a targeted repair of name-resolution failure versus route failure. The described signal instead calls for: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
Question 710
During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. - Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem. - Inspect
ufw status numbered, host listeners and the approved management subnet requirement.
Explanation
Correct Answers
B:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This supplies the decisive diagnostic observation for the stated fault. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. Pair this evidence with the targeted change: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This is the targeted change needed after establishing the fault. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. Pair it with the supporting check: Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This choice concerns gpg artifact signature validation rather than the required diagnosis-and-change pair for luks2 encrypted block-volume opening. Compare the needed evidence (Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.) with the repair (Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This choice concerns ai-generated dependency licensing review rather than the required diagnosis-and-change pair for luks2 encrypted block-volume opening. Compare the needed evidence (Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.) with the repair (Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect ufw status numbered, host listeners and the approved management subnet requirement. This choice concerns ufw least-privilege inbound port rather than the required diagnosis-and-change pair for luks2 encrypted block-volume opening. Compare the needed evidence (Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.) with the repair (Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.