Question 190
A Linux administrator evaluates: A helpdesk creates an account but cannot explain why its /etc/skel profile files are missing. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A helpdesk creates an account but cannot explain why its /etc/skel profile files are missing), the acceptance evidence is: getent passwd, id and the home directory show the approved identity, primary group, login shell and initial files. This verifies the action (Create the intended local account using supported useradd/adduser options, home-directory skeleton and shell, then confirm entries with getent and id.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: An account with no intended home, wrong shell or duplicate UID can cause login failure or unexpected filesystem access.
The observed Linux condition is: A helpdesk creates an account but cannot explain why its /etc/skel profile files are missing. The recommended direct administrative response is: Create the intended local account using supported useradd/adduser options, home-directory skeleton and shell, then confirm entries with getent and id. The relevant failure or security risk is: An account with no intended home, wrong shell or duplicate UID can cause login failure or unexpected filesystem access. Validate success with: getent passwd, id and the home directory show the approved identity, primary group, login shell and initial files.
Incorrect Answers
Distribution package manager and repository selection (2.4) addresses another technical failure: Running the wrong distribution package tool or installing from an untrusted arbitrary repository can leave unresolved dependencies or compromised packages. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: getent passwd, id and the home directory show the approved identity, primary group, login shell and initial files.
Find files by permissions and type without destructive action (2.1) would demonstrate or implement: A dry-run file list contains only the intended candidates, and any later remediation excludes protected paths. This choice can be useful for that problem, but it does not establish the Local account creation with useradd and defaults control being assessed here.
Persistent container data volumes (2.6) would demonstrate or implement: Writing databases only inside a disposable container writable layer can lose data when the container is replaced. The required paired action and test concerns Local account creation with useradd and defaults; a passing result for this alternative could leave that requirement unresolved.