nerdexam
GIAC

GSEC · Question #55

Which of the following would be a valid reason to use a Windows workgroup?

The correct answer is D. Consistent permissions and rights. A Windows workgroup is a valid choice when consistent local permissions and rights are needed across a small set of machines without the overhead of centralized domain infrastructure.

Operating System Security

Question

Which of the following would be a valid reason to use a Windows workgroup?

Options

  • ALower initial cost
  • BSimplicity of single sign-on
  • CCentralized control
  • DConsistent permissions and rights

How the community answered

(29 responses)
  • A
    3% (1)
  • B
    10% (3)
  • C
    3% (1)
  • D
    83% (24)

Why each option

A Windows workgroup is a valid choice when consistent local permissions and rights are needed across a small set of machines without the overhead of centralized domain infrastructure.

ALower initial cost

While workgroups require no dedicated server, the per-machine administration overhead for managing individual accounts and permissions on every computer often results in a higher total cost of ownership than a domain at scale, making 'lower initial cost' a misleading justification.

BSimplicity of single sign-on

Workgroups do not support single sign-on - users must authenticate separately to each computer or shared resource because there is no centralized directory service or Kerberos ticket-granting mechanism.

CCentralized control

Centralized control is a defining feature of Windows Active Directory domains, not workgroups - each computer in a workgroup independently manages its own local accounts and group policies.

DConsistent permissions and rightsCorrect

In a Windows workgroup, each computer maintains its own local security accounts database, and administrators can manually create matching local accounts and assign identical permissions on each machine to achieve a consistent security posture. This makes workgroups valid for small environments where locally enforced, uniform rights are sufficient and a domain controller is not warranted. Unlike a domain, the permissions are enforced independently per machine, which provides direct local control without additional infrastructure.

Concept tested: Windows workgroup vs domain use cases

Source: https://support.microsoft.com/en-us/windows/which-setting-is-right-for-my-network-domain-or-workgroup-b94db0e4-7a4c-43a4-8c06-c0b1d4aed1ea

Topics

#Windows workgroup#domain vs workgroup#network administration#Windows configuration

Community Discussion

No community discussion yet for this question.

Full GSEC Practice