Question 530
An instructor presents the following real-world Linux situation: A group project needs a shared Unix group but team members receive permission errors because the group has never been created. Why does the recommended action work?
Explanation
Correct Answer
A shared numeric GID provides a basis for Unix group access permissions to common files. This explains the stated Linux behavior. The corresponding safe action is: Create an appropriate group with groupadd and assign authorized members through account-management tools. Confirm it with: id for the authorized test member reports the new group and a nonmember does not.
Incorrect Answers
The alternative mechanism is: The account database stores UIDs and primary GID references, while the group database maps group names and member lists. The present evidence instead rests on: A shared numeric GID provides a basis for Unix group access permissions to common files.
The offered principle concerns: User-management utilities update coordinated account and group databases rather than treating them as arbitrary text files. That is not what the current scenario establishes. Its controlling mechanism is: A shared numeric GID provides a basis for Unix group access permissions to common files.
Password changes must maintain authentication database integrity and use properly generated protected hash records. That principle governs the offered alternative, but the facts in this question are explained by: A shared numeric GID provides a basis for Unix group access permissions to common files. The two technical dependencies must be distinguished.