Question 370
A Linux administrator evaluates: A filesystem team needs a new directory to inherit group access without making it world writable. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A filesystem team needs a new directory to inherit group access without making it world writable. The recommended direct administrative response is: Use chmod, chown, getfacl and setfacl to grant the minimum file access required, with an appropriate umask for new files. The relevant failure or security risk is: World-writable permissions and overly permissive default ACLs can expose secrets to other local users. Validate success with: getfacl and controlled read/write tests show approved users can work and unrelated users are denied.
For the specific observation (A filesystem team needs a new directory to inherit group access without making it world writable), the acceptance evidence is: getfacl and controlled read/write tests show approved users can work and unrelated users are denied. This verifies the action (Use chmod, chown, getfacl and setfacl to grant the minimum file access required, with an appropriate umask for new files.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: World-writable permissions and overly permissive default ACLs can expose secrets to other local users.
Incorrect Answers
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 filesystem team needs a new directory to inherit group access without making it world writable. The most direct paired action and test is: Use chmod, chown, getfacl and setfacl to grant the minimum file access required, with an appropriate umask for new files.
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 File ACL permissions and secure umask defaults; the choice measures or changes another part of the system.
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 paired action and test concerns File ACL permissions and secure umask defaults; a passing result for this alternative could leave that requirement unresolved.