Hello @MarioMarquez For templates, If all the network and device config on all 3 firewalls are different, then there is no point of using template stack. You can simply create one template for each firewall and start configuring on them. If you have common config for all the 3 firewalls, then usage of template stack is efficient and preferred way. Create a template, say 'global' on which you will have all the common configuration. Create another individual template, say 'firewall1' for configuring device specific settings. Grouping of these two templates into a stack will ensure that you have all the configuration from both templates committed to firewall. Similarly you can group same global template along with other device sepcific template in different stacks. Note that order of template in template stack matters. You can find more info on how they work at here For device group, If you have individual device group for each firewall, configuration changes on one device group will not effect the other firewall. Device groups follow tree like hierarchy. You can have parent device group (shared) which can have child device groups. Aany common rules on all firewalls can be configured on parent device group where as the device specific rules can be configured under child device groups. You can find more info here. In short, templates and device groups provides greater felxibility for efficient management of your firewalls and usage of them will completely depends upon your network architecture and your requirements.
... View more
