FCSS_EFW_AD-7.6 · Question #54
Refer to the exhibit. A pre-run CLI template that is used in zero-touch provisioning (ZTP) and low- touch provisioning (LTP) with FortiManager is shown. The template is not assigned even though the…
The correct answer is B. Pre-run CLI templates are automatically unassigned after their initial installation. In FortiManager, pre-run CLI templates are used in Zero-Touch Provisioning (ZTP) and Low- Touch Provisioning (LTP) to configure a FortiGate device before it is fully managed by These templates apply configurations when a device is initially provisioned. Once the pre-run CLI…
Question
Refer to the exhibit. A pre-run CLI template that is used in zero-touch provisioning (ZTP) and low- touch provisioning (LTP) with FortiManager is shown. The template is not assigned even though the configuration has already been installed on FortiGate. What is true about this scenario?
Exhibit
Options
- AThe administrator did not assign the template correctly when adding the model device because
- BPre-run CLI templates are automatically unassigned after their initial installation
- CPre-run CLI templates for ZTP and LTP must be unassigned manually after the first installation
- DThe administrator must use post-run CLI templates that are designed for ZTP and LTP
How the community answered
(50 responses)- A8% (4)
- B74% (37)
- C2% (1)
- D16% (8)
Explanation
In FortiManager, pre-run CLI templates are used in Zero-Touch Provisioning (ZTP) and Low- Touch Provisioning (LTP) to configure a FortiGate device before it is fully managed by These templates apply configurations when a device is initially provisioned. Once the pre-run CLI template is executed, FortiManager automatically unassigns it from the device because it is not meant to persist like other policy configurations. This prevents conflicts and ensures that the FortiGate configuration is not repeatedly applied after the initial setup.
Topics
Community Discussion
No community discussion yet for this question.