Describe the role of a Template in vManage and differentiate between Device Template and Feature Template.

• A. Device Template defines network-wide QoS policies.
• B. Feature Template defines how devices are physically provisioned.
• C. Device Template defines the overlay routing protocol to use.
• D. Device Template defines device-level settings; Feature Template defines configurable features that can be applied across devices; templates enable mass provisioning.

Answer: (D)

In vManage, templates are the mechanism that makes provisioning scalable and consistent. The Device Template handles device-level settings that are specific to each box—things like device hostname, IP addressing basics, interface configurations, and other base system parameters. The Feature Template, on the other hand, captures configurable features that can be applied across many devices—such as VPNs, QoS policies, routing, security policies, and service configurations.

The reason this distinction matters is that it allows you to design reusable, modular configurations. Create a Device Template with the common, device-specific basics, then create one or more Feature Templates for the policies and features you want to enable across multiple devices. When you combine a Device Template with the appropriate Feature Templates in a Template Stack, you can push the same set of configurations to a fleet of devices quickly, ensuring consistency and enabling mass provisioning.

The other statements miss the separation of concerns: device-level settings are not used to define network-wide QoS policies; those QoS and other features belong in Feature Templates. And device templates aren’t about how devices are physically provisioned in terms of routing protocols—the actual routing behavior is defined by feature configurations inside Feature Templates.