What are three industry best practices for configuration management? (Choose three.)

Question

Options

• ADefine a consistent device naming convention.
• BUse a central logging server.
• CUse the rollback feature frequently.
• DBack up all of the configurations frequently.
• EUse descriptive fields in device configurations.

• A
  86% (24)
• B
  4% (1)
• C
  11% (3)

Explanation

A (naming conventions), D (frequent backups), and E (descriptive fields) are all proactive, documentation-focused practices that make configurations easier to manage, audit, and recover - core pillars of configuration management.

Why the distractors are wrong:

• B (central logging server) is a best practice for log management/monitoring, not configuration management - it tracks events, not device configs.
• C (use rollback frequently) is backwards: rollback is an emergency recovery tool, not a routine practice. Frequent rollbacks signal poor change control, not good management.

Memory tip: Think of configuration management as "know it, keep it, label it" - Know your devices by name (A), Keep copies of configs (D), and Label configs with descriptive info (E). If a practice is reactive (rollback) or belongs to another domain (logging), it's a distractor.

No community discussion yet for this question.