A. The metadata format is $<metadata_variable_name>.
True. Metadata variables in Fortinet systems follow the format $<metadata_variable_name>, where the variable name is enclosed in angle brackets. This is the standard format for referencing metadata variables.
B. You create them on FortiGate.
False. Metadata variables are typically defined and managed on FortiManager or in FortiCloud, not directly on FortiGate. FortiGate uses these variables in policies or configurations pushed from FortiManager.
C. They can be used as variables in scripts.
True. Metadata variables can be utilized in scripts to dynamically reference objects or configurations, making them versatile for automation and templating.
D. They apply only to non-firewall objects.
False. Metadata variables can apply to various objects, including firewall policies and other security-related configurations, not just non-firewall objects.
As it is a "choose two" solution, the most correct second answer is A, even though the format isn't entirely correct. A metafield is called upon in a CLI script with $(your_metafield_name), if it's jinja2 it's called upon with {{your_metafield_name}}. C is definitely correct. The format for variables and usage is explained in page 158 in the Study Guide (jinja2 is not described though, only as a side note in comparison with TCL).
C, page 158, A https://docs.fortinet.com/document/fortimanager/7.2.0/new-features/218740/metadata-variables-are-supported-in-firewall-objects-configuration
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
myrmidon3
2 months, 2 weeks agoTotoahren
6 months, 2 weeks agotruserud
6 months, 3 weeks ago5deee77
7 months agoArtbrut
7 months, 1 week ago