JN0-106 ยท Interfaces and system services
Configuration groups
Defining groups, apply-groups, wildcards, inheritance and show | display inheritance.
Key points
- Group: reusable configuration block under [edit groups name], applied with apply-groups where it should take effect.
- Wildcards: in angle brackets, such as <ge-*>; one group can configure many interfaces.
- Inheritance is dynamic; a value set directly at a level beats an inherited one.
- Several groups: the first listed has priority.
- show | display inheritance: shows which group each inherited line comes from.
Practice questions
Which statement makes a configuration group take effect at a hierarchy level?
- use-group
- inherit
- apply-groups
- include-groups
Show answer
Answer: C. apply-groups
apply-groups, listing group names, is the statement that activates inheritance. The other three are not Junos statements.
Which statements about configuration groups are correct?
- Changing a group updates everything that inherits from it
- Several apply-groups statements may be used at one hierarchy level
- Groups are removed from the config once applied
- A wildcard pattern is written inside angle brackets
- With several groups in apply-groups, the first has priority
Show answer
Answer: A. Changing a group updates everything that inherits from it, D. A wildcard pattern is written inside angle brackets, E. With several groups in apply-groups, the first has priority
Wildcards use <>, the first listed group wins and inheritance is live. Only one apply-groups statement is allowed per level, and groups stay defined after being applied.
True or false: show configuration lists inherited statements and the group they come from.
Show answer
Answer: False
False. Plain show configuration displays only what is written at each level. Use show | display inheritance to see inherited lines and their source group.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
