FortiManager provides centralized SD-WAN management primarily through the use of SD-WAN templates. This is the core mechanism for defining and deploying consistent SD-WAN configurations across multiple FortiGate devices. A key feature within these templates is the support for normalized interfaces. This allows administrators to create a single template that works across different FortiGate hardware models by mapping device-specific physical interface names (e.g., port1, wan1) to a common logical name. This abstraction is crucial for scalable and heterogeneous deployments.

A. The objects are saved in the ADOM common object database.

While factually true, this describes a general architectural principle of FortiManager for all managed objects (like addresses or policies), not a feature specific to the SD-WAN central management process itself.

B. It does not support meta fields.

This is incorrect. Meta fields (variables) are a core feature in FortiManager provisioning and can be used in CLI templates to configure device-specific SD-WAN settings, such as member gateway IP addresses.

---

1. FortiManager Administration Guide 7.2.4, "SD-WAN templates".

Page 638, "SD-WAN templates" section: "You can use FortiManager to centrally create and manage SD-WAN templates and then assign the templates to supported devices." (Supports answer C).

Page 641, "SD-WAN members" section: "From the Interface dropdown, select a physical or normalized interface." (Supports answer D).

2. FortiManager Administration Guide 7.2.4, "Provisioning Templates".

Page 498, "About provisioning templates" section: This section details the use of meta fields (variables) to push unique, per-device configurations, which contradicts the claim in option B. For example, a CLI template can be used to set a unique gateway for an SD-WAN member using a meta field.

3. FortiManager Administration Guide 7.2.4, "Objects".

Page 318, "Policy & Objects" section: This section explains that objects are managed within the ADOM database. This confirms that statement A is generally true for FortiManager but does not make it a better answer than C or D, which are specific to the SD-WAN management feature set.