2. Compare Controller-Level to Device-Level Management 200-901 Practice Questions (Page 3)

Questions 11–15

1. 11foundation · medium

   In terms of monitoring, how does controller-level management differ from device-level management?

   • AController-level management can only monitor, not configure, devices.
   • BDevice-level management provides a centralized dashboard, while controller-level management does not.
   • CController-level management provides a centralized view of network health, while device-level management requires checking each device separately.
   • DBoth approaches provide the same level of centralized monitoring.
   Reveal Solution Discussion Select an answer first
2. 12foundation · medium

   Which of the following is a typical characteristic of device-level management?

   • APolicy is defined once and pushed to all devices from a single point.
   • BEach device is configured and monitored individually, often using CLI or SNMP.
   • CThe management system maintains a real-time topology of the entire network.
   • DConfiguration is stored centrally and applied to devices automatically.
   Reveal Solution Discussion Select an answer first
4. 13foundation · medium

   In a controller-level management model, how does a centralized controller typically manage network devices?

   • AIt replaces the device's local configuration with a static file that the device must use unchanged.
   • BIt requires an administrator to manually configure each device through a command-line interface before the controller can monitor it.
   • CIt uses protocols such as NETCONF or RESTCONF to push configuration and collect operational state from devices.
   • DIt only monitors devices and cannot change their configuration.
   Reveal Solution Discussion Select an answer first
5. 14foundation · medium

   Which scenario is a strong use case for controller-level management?

   • AA university campus with hundreds of access points that must enforce consistent security policies.
   • BA home network with two routers and a switch that are configured once and left alone.
   • CA branch office with a single router that is rarely reconfigured.
   • DA lab environment with three switches used for testing static configurations.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A network engineer is troubleshooting an issue where a controller-managed switch is not reflecting a change that was made directly on the switch via CLI. The change was made outside the controller. What is the most likely cause of this discrepancy?

   • AThe switch's firmware is outdated and does not support the controller's features.
   • BThe controller's configuration model is the source of truth, and direct CLI changes may be overwritten or not tracked.
   • CThe switch is not compatible with the controller's API.
   • DThe controller is using SNMP to monitor, which does not reflect CLI changes.
   Reveal Solution Discussion Select an answer first