What should be described for network management responsibilities?

What should be described for network management responsibilities?

• A. Groups, roles, and responsibilities for management of network components.
• B. A vendor contact list.
• C. A description of incident response procedures.
• D. A map of the geographic locations of servers.

Answer: (A)

Defining who is responsible for each network component, including groups, roles, and responsibilities, sets clear ownership and authority for configuring, monitoring, securing, and changing network devices. This clarity is essential for a secure network posture because it prevents confusing or conflicting actions, supports proper change management, and enforces segregation of duties. When the organization knows exactly who can approve and perform actions on routers, switches, firewalls, and other devices, it becomes much easier to apply consistent security policies, track accountability, and respond effectively to issues. The other items describe useful elements of a broader security program, but they don’t capture who manages the network components. A vendor contact list is for external communications, incident response procedures outline how to act during events, and a map of server locations is about asset placement, not ongoing management responsibilities.

Defining who is responsible for each network component, including groups, roles, and responsibilities, sets clear ownership and authority for configuring, monitoring, securing, and changing network devices. This clarity is essential for a secure network posture because it prevents confusing or conflicting actions, supports proper change management, and enforces segregation of duties. When the organization knows exactly who can approve and perform actions on routers, switches, firewalls, and other devices, it becomes much easier to apply consistent security policies, track accountability, and respond effectively to issues.

The other items describe useful elements of a broader security program, but they don’t capture who manages the network components. A vendor contact list is for external communications, incident response procedures outline how to act during events, and a map of server locations is about asset placement, not ongoing management responsibilities.