Which component enables centralized management of user permissions across the network?

Which component enables centralized management of user permissions across the network?

• A. Local user accounts on each PC
• B. Per-resource permission lists
• C. Directory service such as Active Directory
• D. No authentication required

Answer: (C)

Centralized management of who can access resources across a network is provided by a directory service. A directory service, like Active Directory, stores user accounts, groups, and permissions in a single, authoritative database and runs on dedicated servers (domain controllers). It lets administrators assign access rights to groups rather than individual users, apply uniform security policies, and enforce authentication and authorization across all devices and resources in the domain. This enables consistent, scalable control as users move between machines or as resources are added. Local user accounts on each PC are treated separately, so permissions would have to be managed on every machine, leading to inconsistent access controls and higher administrative overhead. Per-resource permission lists exist at the resource level but aren’t centralized; they’re scattered across resources and don’t provide a single way to manage who can do what across the network. No authentication required would eliminate security and make it impossible to enforce access control. So, using a directory service like Active Directory is the best way to centrally manage user permissions throughout the network.

Centralized management of who can access resources across a network is provided by a directory service. A directory service, like Active Directory, stores user accounts, groups, and permissions in a single, authoritative database and runs on dedicated servers (domain controllers). It lets administrators assign access rights to groups rather than individual users, apply uniform security policies, and enforce authentication and authorization across all devices and resources in the domain. This enables consistent, scalable control as users move between machines or as resources are added.

Local user accounts on each PC are treated separately, so permissions would have to be managed on every machine, leading to inconsistent access controls and higher administrative overhead. Per-resource permission lists exist at the resource level but aren’t centralized; they’re scattered across resources and don’t provide a single way to manage who can do what across the network. No authentication required would eliminate security and make it impossible to enforce access control.

So, using a directory service like Active Directory is the best way to centrally manage user permissions throughout the network.