FortiManager provisioning templates provide centralized, standardized, and scalable configuration management across FortiGate devices. They are particularly valuable in Secure SD-WAN deployments involving multiple branches, hubs, and overlay networks.

Option C is correct because a provisioning template group can contain both a system template and an SD-WAN template. System templates configure device-level settings, while SD-WAN templates define interfaces, zones, performance SLAs, and traffic-steering rules. FortiManager coordinates their installation according to configuration dependencies.

Option D is correct because CLI template groups support different template types, specifically standard CLI scripts and Jinja scripts. CLI scripts contain FortiOS commands, while Jinja templates support dynamic configuration generation using variables and conditional logic.

Option E is correct because CLI templates within a group are processed sequentially, from top to bottom. Administrators can organize their execution order to ensure prerequisite configurations are established before dependent settings.

Option A is incorrect because current FortiManager releases support CLI and Jinja scripts, not Perl scripts as a provisioning-template type.

Option B is incorrect because a standard template group supports one IPsec tunnel template assignment, not three separate IPsec templates.