Which feature of Panorama allows an administrator to create a single network configuration that can be reused repeatedly for large-scale deployments even if values of configured objects, such as routes and interface addresses, change?
Which feature of Panorama allows an administrator to create a single network configuration that can be reused repeatedly for large-scale deployments even if values of configured objects, such as routes and interface addresses, change?
Template variables allow an administrator to create a single network configuration that is reusable for large-scale deployments while adapting to different configurations such as routes and interface addresses. By defining variables, the base configuration can remain consistent, and the specific details can be varied as needed for each deployment instance, thus ensuring efficiency and consistency.
A here's my thought you can have "variables" without "stacks" = achieve single template that can be used on multiple devices, but you can't have "stacks" without "variables" to achieve the same
Re-Usability Reference: https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/panorama-web-interface/panorama-templates/panorama-templates-template-variable
New link https://docs.paloaltonetworks.com/pan-os/11-0/pan-os-web-interface-help/panorama-web-interface/panorama-templates/panorama-templates-template-variable
It is a single network configuration, so I think that's why is not C, but A.
I think the answer is C. I stand to be corrected. https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/panorama-web-interface/panorama-templates
I think that's the correct answer too.
Actually C is correct but normally this cert questions can be as well, which is the MOST correct. So its A. The statement says single network configuration. You dont need a Template stack necessarily to achieve this. A Template variable can be suffice. So I will go for A.
Definitely A because while A requires C, C by itself cannot achieve the goal
It's A. Sure you reference them in templates/template stacks, but the template variables are the things that are reusable. You create a single config with a single variable and it can have different meaning depending on the variable value. Gotta be A.
config reuse is mainly through template and the template with have variable in it.
see #169
I think a) if you then went to use the same configuration to deploy another network, you'd presumably need different interface IPs etc.