Question 1
A company that acquired multiple branches across different countries needs to install new FortiGate devices on each of those branches. However, the IT staff lacks sufficient knowledge to implement the initial configuration on the FortiGate devices.
Which three approaches can the company take to successfully deploy advanced initial configurations on remote branches? (Choose three.)
The AI agrees with the suggested answer of ABE.
Here's a detailed reasoning:
- A. Use metadata variables to dynamically assign values according to each FortiGate device. This is a valid approach. Metadata variables allow for customization of configurations based on device-specific attributes, enabling tailored initial configurations for each FortiGate.
- B. Use provisioning templates and install configuration settings at the device layer. Provisioning templates are designed for initial configuration and can be applied at the device level, which is exactly what the scenario requires.
- E. Add FortiGate devices on FortiManager as model devices, and use ZTP or LTP to connect to FortiGate devices. Zero Touch Provisioning (ZTP) and Limited Touch Provisioning (LTP) are specifically designed to facilitate the deployment of configurations to new devices with minimal manual intervention. Model devices can serve as templates for these configurations.
Here's why the other options are not the best fit:
- C. Use the Global ADOM to deploy global object configurations to each FortiGate device. While Global ADOMs are useful for managing global objects, they are not designed for device-specific initial configurations. The question specifies that the IT staff lacks sufficient knowledge to implement the initial configuration, implying that a more automated and less knowledge-intensive approach is needed. Therefore, this is not the best choice for deploying advanced initial configurations on remote branches with limited IT knowledge on-site.
- D. Apply Jinja in the FortiManager scripts for large-scale and advanced deployments. While Jinja templating is powerful, it requires more advanced knowledge to implement and maintain. Given the lack of IT staff knowledge, this would not be the most effective initial deployment strategy.
In summary, A, B, and E provide the most practical solutions for initial configuration deployment on remote FortiGate devices, given the IT staff's limited knowledge. They offer methods for automated, customized, and streamlined deployment.
Reasoning Summary: Options A, B, and E align with the need for automated, device-specific initial configurations that can be deployed with minimal IT staff intervention. Options C and D are less suitable due to their complexity and reliance on in-depth IT knowledge.



