Difficulty: Medium
Correct Answer: A workgroup mode, with each engineer administering his or her own computer
Explanation:
Introduction / Context:
Choosing between a workgroup and a domain hinges on administrative centralization, policy needs, and scale. In small teams with fluid membership and no appointed administrator, minimizing central dependencies while still controlling access to shared data can be practical.
Given Data / Assumptions:
Concept / Approach:
A workgroup allows local control on each machine, ad-hoc file sharing, and NTFS permissions to restrict access to the team. While domains provide stronger centralized control (Group Policy, centralized authentication), they require domain controller management and clear administrative roles. For this scenario’s constraints, a workgroup satisfies the ‘‘no single admin’’ requirement while still enabling engineers to protect and share resources locally.
Step-by-Step Solution:
Verification / Alternative check:
Test access from a non-team machine/user; permissions should deny entry. Confirm that team members can read/write as required. Assess administrative overhead versus a small domain—if later growth occurs, migrating to a domain may be justified.
Why Other Options Are Wrong:
Common Pitfalls:
Using the same local password across many machines can be risky. Document procedures for onboarding/offboarding to keep permissions current.
Final Answer:
A workgroup mode, with each engineer administering his or her own computer
Discussion & Comments