Q: 8
An administrator must standardize the deployment of FortiGate devices across branches with consistent interface roles and policy packages using FortiManager. What is the recommended best practice for interface assignment in this scenario?
Options
Discussion
Its A, D looks good but it's a bit of a trap since metadata variables are what let you standardize across branches.
A not D, D just auto-identifies interface types but A (metadata variables) actually makes configs consistent per branch.
A not D. Trap here is assuming D does per-device mapping, but metadata variables (A) actually solve that for standardization.
A tbh
A is right here imo. Metadata variables let you use one policy package and swap out values per branch, so config stays clean and flexible. Install On doesn’t solve the variable interface problem as easily. Someone let me know if they’ve made B or D work for this.
A imo. Using metadata variables lets you push a single standard config but still handle each branch's unique details (like IPs or VLANs). Pretty common best practice, seen it in several official guides.
A tbh, because with metadata variables you can set standard configs and the unique details for each site automatically fill in. It's scalable and Fortinet's docs push that method. Not 100 percent if D works as seamlessly but open to counterpoints.
Its D, since normalized interface types help when there are lots of naming inconsistencies, not just metadata.
A is the way to go since metadata variables let you keep one policy package and just plug in branch-specific details. Makes deployments cleaner and less manual editing. Pretty sure that's what Fortinet recommends for this scenario but open if someone saw different in production.
Nah, I think A is correct, not D-using metadata variables covers dynamic configs even with some name variation.
Be respectful. No spam.