5 Network Management Free Online FlashCards

What is the primary aim of network management?

Network management keeps services available and reliable while controlling security and operational risk.

What information should a network inventory record for each item?

Record each item’s name or identifier, type, location, owner, management address, software or firmware version, support status, and dependencies.

Which systems and services belong in a network inventory?

Include routers, switches, firewalls, access points, servers, circuits, and essential services such as DNS and DHCP.

What should an addressing plan specify for each subnet?

Document each subnet’s purpose, prefix, gateway, location, and allocation method; size it for its purpose and expected growth, and avoid overlapping ranges.

What DHCP details should administrators document?

Document DHCP scopes, exclusions, reservations, lease settings, and relay paths to help prevent conflicts between dynamically and statically addressed devices.

What should network monitoring reveal?

Track availability, performance, capacity, and security-relevant events, using thresholds tied to service requirements and reviewing trends over time.

Why centralize and time-synchronize network logs?

Centralized, time-synchronized logs help correlate events across devices. Protect access, retain records according to organizational requirements, and use secure transport where supported.

What belongs in an operational incident record?

Record what happened and when, affected services and devices, observations and test results, actions, approvals, and the outcome.

What is a configuration baseline?

A configuration baseline is the approved reference state for a device or service, including relevant settings, software versions, and security controls.

What should a controlled network change include?

A controlled change includes its reason, affected systems, risk and security-impact analysis, approval, implementation and test plans, communications, and rollback procedure.

How should emergency network changes be handled?

They may use an accelerated process, but they should still be documented and reviewed afterward.

What is the core sequence for systematic troubleshooting?

Define the symptom and scope, check dependencies, test from basic to specific, change one relevant thing at a time, then verify and document recovery.