Question 660
For this Linux administration lab: A team requires a default primary group different from the user-private group created with the account. Which safety and lifecycle check best prevents the same problem returning?
Explanation
Correct Answer
Review file ownership and service permissions after primary GID changes. This guards against recurrence of: Primary group and supplementary group settings have different semantics. Confirm the lab's final state by: `id -gn svc_labs` reports `appops` and application file permissions remain appropriate.
Incorrect Answers
Apply secure home defaults and review them at account creation. That control is best suited to a separate scenario: A new user must have a private home directory rather than inherited group-read access. It is not the best safeguard for the current mechanism: Primary group and supplementary group settings have different semantics.
Audit membership before and after group changes and use `-aG` for additive grants. That control is best suited to a separate scenario: A user must join the `analysts` group without losing their existing supplementary groups. It is not the best safeguard for the current mechanism: Primary group and supplementary group settings have different semantics.
Always validate sudoers changes with `visudo -c` before ending the recovery session. That control is best suited to a separate scenario: An operator edits `/etc/sudoers` using an ordinary editor and introduces invalid syntax, breaking privilege escalation. It is not the best safeguard for the current mechanism: Primary group and supplementary group settings have different semantics.