Q: 2
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?
Options
Discussion
Option B, they get auto-unassigned after the first install. Pretty sure that’s how ZTP/LTP pre-run templates work with FortiManager.
Wouldn't C be correct if you had to prevent config conflicts by unassigning manually in some scenarios?
Why would B not need a manual step here? Doesn't it always need some admin intervention on pre-run templates?
I think C fits better for this, since you sometimes have to manually unassign pre-run CLI templates to avoid policy package import issues. Pretty sure that's how it works on some setups, but maybe I'm missing something small here. Agree?
Yeah that fits with what I've seen too-it's B. FortiManager just unassigns the pre-run CLI template automatically after initial use in ZTP or LTP. If you're not on a much older version, you don't have to do anything extra.
B not C. FortiManager now unassigns pre-run CLI templates automatically after they're pushed out in ZTP or LTP flows. You used to have to do it by hand but on current versions that's handled for you. Correct me if I'm off for a weird firmware build.
Feels like B, since FortiManager auto-unassigns pre-run templates after they're used once for ZTP/LTP scenarios. Pretty sure that's always the case unless a custom workflow overrides it, but let me know if someone saw otherwise.
Makes sense to me, I'd pick B too. FortiManager unassigns pre-run templates automatically after first use.
B
I’d say it's B since FortiManager unassigns pre-run CLI templates automatically after they're installed, that's what the doc and hands-on labs show. Saw a similar question in practice tests, so I'd stick with B unless there's an odd version caveat. Agree?
Be respectful. No spam.