Device Identification and Policy Management
Which of the following would best enable a systems administrator to easily determine which devices are located at a remote facility and allow policy to be pushed to only those devices?
Community Votes
81% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests the ability to link device identification methods with automated policy application; the trap is confusing visual documentation (network diagrams) with actionable configuration identifiers.
Standard naming conventions allow systems administrators to identify remote devices by name, enabling targeted policy enforcement. This method is preferred over static documentation for dynamic configuration management.
Choosing Network Diagrams because they show location visually, but failing to recognize that diagrams are static references and cannot be used to push policies to specific endpoints.
Community Discussion (10 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Standard naming conventions (Option C) provide a structured, logical way to identify devices based on their location, function, or department. By embedding location information into the hostname or FQDN (e.g., 'NYC-SRV-01'), an administrator can easily query directories or management consoles to identify all devices at a remote facility. More importantly, these names serve as keys for grouping in configuration management tools (like SCCM or Ansible), allowing policies to be pushed specifically to those groups.Why the Other Options Are Wrong
Network diagrams (Option B) provide a visual topology of the network but are static documents. They do not integrate with configuration management systems, making it impossible to "push" policies directly from a diagram. Baseline configurations (Option A) define the desired state of a device but do not inherently help identify where a device is located. Hot sites (Option D) refer to disaster recovery facilities, not a method for identifying individual devices within a network.Community Comment Notes
The majority of voters selected C, agreeing that naming conventions facilitate both identification and policy application. One user noted that naming allows creating computer groups for policy deployment. Another commenter argued for network diagrams, stating they show layout and connectivity, but this ignores the operational requirement to actively manage and push settings to devices rather than just viewing them.Official Reference
Exam Strategy
When a question asks about "pushing policies" or "automated management," prioritize technical identifiers like naming conventions or directory attributes over static documentation like diagrams or spreadsheets.
Frequently Asked Questions
Why can't I use network diagrams to push policies?
Network diagrams are static visual representations. They cannot interact with configuration management software to automatically apply settings to specific devices.
How do naming conventions help with policy pushing?
Consistent names allow admins to create dynamic groups in management tools. Policies can then be assigned to these groups based on the naming pattern.