mcAfee Secure Website
23

CompTIA XK0-006 Bundle

Exam Code: XK0-006

Exam Name CompTIA Linux+

Certification Provider: CompTIA

Corresponding Certification: CompTIA Linux+

XK0-006 Training Materials $19.99

Reliable & Actual Study Materials for XK0-006 Exam Success

The Latest XK0-006 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    XK0-006 Questions & Answers

    160 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • exam =30
    Study Guide

    XK0-006 Study Guide

    1297 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

CompTIA Linux+ (XK0-006) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable CompTIA Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $154.98
Bundle Price: $134.99

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    160 Questions

    $124.99
    exam =35
  • exam =36
    Study Guide

    Study Guide

    1297 PDF Pages

    $29.99

CompTIA XK0-006 Practice Test 41

Question 400

A Linux administrator evaluates: A nonhuman application account should continue running its process without inheriting human administrator login rights. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. A tested privileged operator connects with an approved key, invalid keys fail, and effective sshd settings match policy.
  2. Run an approved OpenSCAP or equivalent compliance benchmark assessment, review findings and remediate only validated deviations with change control.
  3. Apply an approved multi-factor login flow for interactive privileged access while keeping noninteractive service accounts narrowly scoped and non-login where suitable.
  4. A valid directory password cannot bypass a missing NSS identity mapping or restrictive PAM account policy.
  5. A privileged login exercises the required additional factor while the service identity cannot initiate an interactive shell.

Explanation

Correct Answers

C:

The observed Linux condition is: A nonhuman application account should continue running its process without inheriting human administrator login rights. The recommended direct administrative response is: Apply an approved multi-factor login flow for interactive privileged access while keeping noninteractive service accounts narrowly scoped and non-login where suitable. The relevant failure or security risk is: Shared interactive service credentials or an MFA bypass for privileged sessions weakens identity assurance and incident attribution. Validate success with: A privileged login exercises the required additional factor while the service identity cannot initiate an interactive shell.

E:

For the specific observation (A nonhuman application account should continue running its process without inheriting human administrator login rights), the acceptance evidence is: A privileged login exercises the required additional factor while the service identity cannot initiate an interactive shell. This verifies the action (Apply an approved multi-factor login flow for interactive privileged access while keeping noninteractive service accounts narrowly scoped and non-login where suitable.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Shared interactive service credentials or an MFA bypass for privileged sessions weakens identity assurance and incident attribution.

Incorrect Answers

A:

OpenSSH server key authentication and root login hardening (3.3) would demonstrate or implement: A tested privileged operator connects with an approved key, invalid keys fail, and effective sshd settings match policy. The case states: A nonhuman application account should continue running its process without inheriting human administrator login rights. The most direct paired action and test is: Apply an approved multi-factor login flow for interactive privileged access while keeping noninteractive service accounts narrowly scoped and non-login where suitable.

B:

Baseline compliance scanning with OpenSCAP (3.6) addresses another technical failure: Blindly applying every hardening recommendation can break required services and does not by itself prove regulatory compliance. This choice can be useful for that problem, but it does not establish the MFA and restricted service identity practices control being assessed here.

D:

PAM and SSSD identity authentication diagnosis (3.1) would demonstrate or implement: A valid directory password cannot bypass a missing NSS identity mapping or restrictive PAM account policy. The required paired action and test concerns MFA and restricted service identity practices; a passing result for this alternative could leave that requirement unresolved.

Question 401

A Linux administrator investigates: A portable Linux data disk containing regulated customer records must remain confidential if stolen. Which action BEST addresses the specific Linux technical requirement?

  1. Edit a narrowly scoped sudoers drop-in through visudo and grant only the documented commands to the intended group or user.
  2. Inspect SELinux enforcement and AVC denials; restore or assign the correct context or supported boolean instead of disabling SELinux.
  3. Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.
  4. Configure narrowly scoped auditd rules and journal or rsyslog retention for security-relevant events, then verify collection.

Explanation

Correct Answer

C:

The observed Linux condition is: A portable Linux data disk containing regulated customer records must remain confidential if stolen. The recommended direct administrative response is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data. The relevant failure or security risk is: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss. Validate success with: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

Incorrect Answers

A:

Least-privilege sudoers policy with visudo (3.3) addresses another technical failure: An unrestricted NOPASSWD rule or syntax error can expose root authority or lock administrators out of required maintenance. The case states: A portable Linux data disk containing regulated customer records must remain confidential if stolen. The most direct diagnosis is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.

B:

SELinux context and boolean troubleshooting (3.3) addresses another technical failure: Changing enforcing to disabled hides the mislabeled resource and weakens access controls for unrelated services. This choice can be useful for that problem, but it does not establish the LUKS2 full-volume encryption and key recovery control being assessed here.

D:

Linux audit trails with auditd and journalctl (3.1) addresses another technical failure: An uncollected privileged action or volatile journal cannot provide reliable post-incident accountability evidence. The required diagnosis concerns LUKS2 full-volume encryption and key recovery; a passing result for this alternative could leave that requirement unresolved.

Question 402

In the post-change validation, the team sees: A portable Linux data disk containing regulated customer records must remain confidential if stolen. Which evidence MOST directly confirms the appropriate correction succeeded?

  1. A tested privileged operator connects with an approved key, invalid keys fail, and effective sshd settings match policy.
  2. Zone and rule inspection before and after reload shows only the approved ports available to approved test sources.
  3. cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.
  4. A repeat scan records reviewed findings, documented exceptions and improvements without breaking approved service checks.

Explanation

Correct Answer

C:

For the specific observation (A portable Linux data disk containing regulated customer records must remain confidential if stolen), the acceptance evidence is: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable. This verifies the action (Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss.

Incorrect Answers

A:

OpenSSH server key authentication and root login hardening (3.3) would demonstrate or implement: A tested privileged operator connects with an approved key, invalid keys fail, and effective sshd settings match policy. The case states: A portable Linux data disk containing regulated customer records must remain confidential if stolen. The most direct evidence is: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

B:

Firewalld runtime versus permanent configuration (3.2) would demonstrate or implement: Zone and rule inspection before and after reload shows only the approved ports available to approved test sources. This choice can be useful for that problem, but it does not establish the LUKS2 full-volume encryption and key recovery control being assessed here.

D:

Baseline compliance scanning with OpenSCAP (3.6) would demonstrate or implement: A repeat scan records reviewed findings, documented exceptions and improvements without breaking approved service checks. The required evidence concerns LUKS2 full-volume encryption and key recovery; a passing result for this alternative could leave that requirement unresolved.

Question 403

A change review on a Linux server identifies: A volume is encrypted but its only recovery passphrase was stored on the same failed server. Which action BEST addresses the specific Linux technical requirement?

  1. Use firewall-cmd with the intended zone and explicit runtime or --permanent options, then reload and verify the effective service access.
  2. Configure sshd to use approved public-key authentication and limit root or user access, then validate syntax and preserve a recovery session.
  3. Run an approved OpenSCAP or equivalent compliance benchmark assessment, review findings and remediate only validated deviations with change control.
  4. Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.

Explanation

Correct Answer

D:

The observed Linux condition is: A volume is encrypted but its only recovery passphrase was stored on the same failed server. The recommended direct administrative response is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data. The relevant failure or security risk is: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss. Validate success with: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

Incorrect Answers

A:

Firewalld runtime versus permanent configuration (3.2) addresses another technical failure: A runtime-only allowance may disappear after reload, while changing the wrong zone can open a service on an unintended interface. The case states: A volume is encrypted but its only recovery passphrase was stored on the same failed server. The most direct corrective action is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.

B:

OpenSSH server key authentication and root login hardening (3.3) addresses another technical failure: Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure. This choice can be useful for that problem, but it does not establish the LUKS2 full-volume encryption and key recovery control being assessed here.

C:

Baseline compliance scanning with OpenSCAP (3.6) addresses another technical failure: Blindly applying every hardening recommendation can break required services and does not by itself prove regulatory compliance. This case instead tests LUKS2 full-volume encryption and key recovery; the choice measures or changes another part of the system.

Question 404

A Linux administrator reviews a reported issue: A volume is encrypted but its only recovery passphrase was stored on the same failed server. Which failure mode or risk is MOST relevant to this condition?

  1. Shared interactive service credentials or an MFA bypass for privileged sessions weakens identity assurance and incident attribution.
  2. A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss.
  3. Blindly applying every hardening recommendation can break required services and does not by itself prove regulatory compliance.
  4. Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure.

Explanation

Correct Answer

B:

The reported situation (A volume is encrypted but its only recovery passphrase was stored on the same failed server) most directly creates this failure risk: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss. The corresponding safe response is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data. An appropriate outcome check is: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

Incorrect Answers

A:

MFA and restricted service identity practices (3.4) would demonstrate or implement: Shared interactive service credentials or an MFA bypass for privileged sessions weakens identity assurance and incident attribution. The case states: A volume is encrypted but its only recovery passphrase was stored on the same failed server. The most direct risk is: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss.

C:

Baseline compliance scanning with OpenSCAP (3.6) would demonstrate or implement: Blindly applying every hardening recommendation can break required services and does not by itself prove regulatory compliance. This case instead tests LUKS2 full-volume encryption and key recovery; the choice measures or changes another part of the system.

D:

OpenSSH server key authentication and root login hardening (3.3) would demonstrate or implement: Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure. The required risk concerns LUKS2 full-volume encryption and key recovery; a passing result for this alternative could leave that requirement unresolved.

Question 405

A production incident ticket states: A workstation replacement requires proving an encrypted LUKS2 filesystem can be unlocked on a recovery host. Which action BEST addresses the specific Linux technical requirement?

  1. Apply an approved multi-factor login flow for interactive privileged access while keeping noninteractive service accounts narrowly scoped and non-login where suitable.
  2. Run an approved OpenSCAP or equivalent compliance benchmark assessment, review findings and remediate only validated deviations with change control.
  3. Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.
  4. Configure sshd to use approved public-key authentication and limit root or user access, then validate syntax and preserve a recovery session.

Explanation

Correct Answer

C:

The observed Linux condition is: A workstation replacement requires proving an encrypted LUKS2 filesystem can be unlocked on a recovery host. The recommended direct administrative response is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data. The relevant failure or security risk is: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss. Validate success with: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

Incorrect Answers

A:

MFA and restricted service identity practices (3.4) addresses another technical failure: Shared interactive service credentials or an MFA bypass for privileged sessions weakens identity assurance and incident attribution. The case states: A workstation replacement requires proving an encrypted LUKS2 filesystem can be unlocked on a recovery host. The most direct corrective action is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.

B:

Baseline compliance scanning with OpenSCAP (3.6) addresses another technical failure: Blindly applying every hardening recommendation can break required services and does not by itself prove regulatory compliance. This choice can be useful for that problem, but it does not establish the LUKS2 full-volume encryption and key recovery control being assessed here.

D:

OpenSSH server key authentication and root login hardening (3.3) addresses another technical failure: Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure. The required corrective action concerns LUKS2 full-volume encryption and key recovery; a passing result for this alternative could leave that requirement unresolved.

Question 406

An infrastructure engineer checks a specific situation: A workstation replacement requires proving an encrypted LUKS2 filesystem can be unlocked on a recovery host. Which evidence MOST directly confirms the appropriate correction succeeded?

  1. A controlled policy event has the intended principal, action, timestamp and searchable retained record.
  2. A tested privileged operator connects with an approved key, invalid keys fail, and effective sshd settings match policy.
  3. cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.
  4. The service works with SELinux enforcing and its resources have persistent expected contexts without repeated AVC denials.

Explanation

Correct Answer

C:

For the specific observation (A workstation replacement requires proving an encrypted LUKS2 filesystem can be unlocked on a recovery host), the acceptance evidence is: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable. This verifies the action (Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss.

Incorrect Answers

A:

Linux audit trails with auditd and journalctl (3.1) would demonstrate or implement: A controlled policy event has the intended principal, action, timestamp and searchable retained record. The case states: A workstation replacement requires proving an encrypted LUKS2 filesystem can be unlocked on a recovery host. The most direct evidence is: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

B:

OpenSSH server key authentication and root login hardening (3.3) would demonstrate or implement: A tested privileged operator connects with an approved key, invalid keys fail, and effective sshd settings match policy. This choice can be useful for that problem, but it does not establish the LUKS2 full-volume encryption and key recovery control being assessed here.

D:

SELinux context and boolean troubleshooting (3.3) would demonstrate or implement: The service works with SELinux enforcing and its resources have persistent expected contexts without repeated AVC denials. The required evidence concerns LUKS2 full-volume encryption and key recovery; a passing result for this alternative could leave that requirement unresolved.

Question 407

An authorized Linux operations assessment observes: An engineer assumes changing ordinary UNIX file permissions also encrypts data at rest. Which action BEST addresses the specific Linux technical requirement?

  1. Inspect SELinux enforcement and AVC denials; restore or assign the correct context or supported boolean instead of disabling SELinux.
  2. Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.
  3. Configure narrowly scoped auditd rules and journal or rsyslog retention for security-relevant events, then verify collection.
  4. Configure sshd to use approved public-key authentication and limit root or user access, then validate syntax and preserve a recovery session.

Explanation

Correct Answer

B:

The observed Linux condition is: An engineer assumes changing ordinary UNIX file permissions also encrypts data at rest. The recommended direct administrative response is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data. The relevant failure or security risk is: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss. Validate success with: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

Incorrect Answers

A:

SELinux context and boolean troubleshooting (3.3) addresses another technical failure: Changing enforcing to disabled hides the mislabeled resource and weakens access controls for unrelated services. The case states: An engineer assumes changing ordinary UNIX file permissions also encrypts data at rest. The most direct corrective action is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.

C:

Linux audit trails with auditd and journalctl (3.1) addresses another technical failure: An uncollected privileged action or volatile journal cannot provide reliable post-incident accountability evidence. This case instead tests LUKS2 full-volume encryption and key recovery; the choice measures or changes another part of the system.

D:

OpenSSH server key authentication and root login hardening (3.3) addresses another technical failure: Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure. The required corrective action concerns LUKS2 full-volume encryption and key recovery; a passing result for this alternative could leave that requirement unresolved.

Question 408

In a controlled system validation, the observation is: An engineer assumes changing ordinary UNIX file permissions also encrypts data at rest. Which failure mode or risk is MOST relevant to this condition?

  1. Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure.
  2. Accepting unrestricted forwarding or dropping established return packets can either expose networks or break allowed flows.
  3. Accounts that never expire or continue authenticating after offboarding create persistent unauthorized access risk.
  4. A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss.

Explanation

Correct Answer

D:

The reported situation (An engineer assumes changing ordinary UNIX file permissions also encrypts data at rest) most directly creates this failure risk: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss. The corresponding safe response is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data. An appropriate outcome check is: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

Incorrect Answers

A:

OpenSSH server key authentication and root login hardening (3.3) would demonstrate or implement: Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure. The case states: An engineer assumes changing ordinary UNIX file permissions also encrypts data at rest. The most direct evidence is: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss.

B:

Stateful nftables filtering and IP forwarding (3.2) would demonstrate or implement: Accepting unrestricted forwarding or dropping established return packets can either expose networks or break allowed flows. This choice can be useful for that problem, but it does not establish the LUKS2 full-volume encryption and key recovery control being assessed here.

C:

Password aging and inactive account enforcement (3.4) would demonstrate or implement: Accounts that never expire or continue authenticating after offboarding create persistent unauthorized access risk. This case instead tests LUKS2 full-volume encryption and key recovery; the choice measures or changes another part of the system.

Question 409

During a planned service review, engineers find: A security review needs to document who holds recovery keys before deploying encrypted volumes across branch offices. Which action BEST addresses the specific Linux technical requirement?

  1. Review and enforce supported local password aging, account expiry and lock status with chage, passwd and policy-appropriate PAM controls.
  2. Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.
  3. Design an nftables ruleset with appropriate state, interface and address matches; enable IP forwarding only for a documented routed use case.
  4. Configure sshd to use approved public-key authentication and limit root or user access, then validate syntax and preserve a recovery session.

Explanation

Correct Answer

B:

The observed Linux condition is: A security review needs to document who holds recovery keys before deploying encrypted volumes across branch offices. The recommended direct administrative response is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data. The relevant failure or security risk is: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss. Validate success with: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

Incorrect Answers

A:

Password aging and inactive account enforcement (3.4) addresses another technical failure: Accounts that never expire or continue authenticating after offboarding create persistent unauthorized access risk. The case states: A security review needs to document who holds recovery keys before deploying encrypted volumes across branch offices. The most direct corrective action is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.

C:

Stateful nftables filtering and IP forwarding (3.2) addresses another technical failure: Accepting unrestricted forwarding or dropping established return packets can either expose networks or break allowed flows. This case instead tests LUKS2 full-volume encryption and key recovery; the choice measures or changes another part of the system.

D:

OpenSSH server key authentication and root login hardening (3.3) addresses another technical failure: Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure. The required corrective action concerns LUKS2 full-volume encryption and key recovery; a passing result for this alternative could leave that requirement unresolved.

Question 410

A Linux administrator evaluates: A security review needs to document who holds recovery keys before deploying encrypted volumes across branch offices. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. A repeat scan records reviewed findings, documented exceptions and improvements without breaking approved service checks.
  2. World-writable permissions and overly permissive default ACLs can expose secrets to other local users.
  3. cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.
  4. Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.
  5. Configure narrowly scoped auditd rules and journal or rsyslog retention for security-relevant events, then verify collection.

Explanation

Correct Answers

C:

For the specific observation (A security review needs to document who holds recovery keys before deploying encrypted volumes across branch offices), the acceptance evidence is: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable. This verifies the action (Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss.

D:

The observed Linux condition is: A security review needs to document who holds recovery keys before deploying encrypted volumes across branch offices. The recommended direct administrative response is: Use supported LUKS2 volume encryption with approved passphrase or key management and practice recovery before storing sensitive data. The relevant failure or security risk is: A volume encrypted without safely recoverable key material can remain permanently inaccessible after host loss. Validate success with: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

Incorrect Answers

A:

Baseline compliance scanning with OpenSCAP (3.6) would demonstrate or implement: A repeat scan records reviewed findings, documented exceptions and improvements without breaking approved service checks. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: cryptsetup status and an authorized unlock/restore rehearsal confirm that data is encrypted at rest and recoverable.

B:

File ACL permissions and secure umask defaults (3.3) would demonstrate or implement: World-writable permissions and overly permissive default ACLs can expose secrets to other local users. This choice can be useful for that problem, but it does not establish the LUKS2 full-volume encryption and key recovery control being assessed here.

E:

Linux audit trails with auditd and journalctl (3.1) addresses another technical failure: An uncollected privileged action or volatile journal cannot provide reliable post-incident accountability evidence. The paired-answer requirement concerns LUKS2 full-volume encryption and key recovery; this alternative does not provide the matching intervention and separate acceptance evidence.