You manage an SD-WAN topology.

FortiManager supports advance model-device creation and per-device metadata variable mappings for large-scale onboarding. Model devices can be assigned configuration templates and policy packages before physical installation. When DHCP-based discovery is selected, DHCP options can also be prepared to direct new FortiGates toward FortiManager. Custom metadata values provide branch-specific addresses, site identifiers and gateway settings. The terms “ZTP template” and “policy blueprint” do not accurately identify the documented FortiManager objects in the candidate answers: device blueprints and policy packages are distinct components. Consequently, options A, B and D are valid under a DHCP-based ZTP design. This choice is dependent on the selected bootstrap method. Reference: FortiManager 7.6 — Model Devices, Metadata Variables, Zero-Touch Provisioning and Device Blueprints. FortiManager templates reduce repetitive work but must resolve to valid, device-specific configurations at installation time. Device assignments, metadata mappings, ADOM scope, policy-package interfaces and provisioning order should be inspected together rather than troubleshooting any one object in isolation.

Verification qualification: The DHCP-server step depends on the zero-touch-provisioning method; it is not universally mandatory.