Refer to the exhibit. The FortiManager device is set to central management mode for FortiSwitch devices. How are configuration changes applied to multiple FortiSwitch devices?

Question

Exhibit

Options

• AConfiguration changes require manually updating each device.
• BChanges are applied only to switches that share the same model number.
• CChanges are made through a template.
• DConfiguration changes are made on individual switches.

• A
  2% (1)
• B
  5% (2)
• C
  7% (3)
• D
  85% (35)

Explanation

Option D is correct because in FortiManager's central management mode for FortiSwitch, configuration changes are applied at the individual switch level - each FortiSwitch device is configured separately within the FortiManager interface, giving administrators granular, per-device control rather than a blanket policy push.

Why the distractors are wrong:

• A is wrong because central management mode exists precisely to eliminate manual, device-by-device CLI/GUI access; changes are made from FortiManager, not on the device itself.
• B is wrong because there is no such model-number restriction in how FortiManager applies configurations - switch model is irrelevant to the update mechanism.
• C is the trickiest distractor: templates are used in FortiManager for FortiGate device provisioning, but in central management mode for FortiSwitch, individual switch configuration (not template-based push) is how changes are applied.

Memory tip: Think of "central management" as meaning where you manage (FortiManager as the single pane of glass), not how many at once. The "individual switch" answer (D) reflects that each FortiSwitch still gets its own config applied through that central interface - centralized access, per-device application.

No community discussion yet for this question.