A regional ISP is provisioning a new subscriber VLAN on aggregation port ge-1/0/5. Logical unit 100 needs the address 10.20.30.1/24 so subscriber CPE devices can route through it. Which configuration statement correctly assigns that address?
Select an answer to reveal the explanation.
Short Explanation
The address always rides under a specific unit, never bolted straight onto the physical port. Say the interface, then the unit, then the family and address — that order is the whole trick here.
Full Explanation
An IP address in Junos is a property of a logical unit's address family, so the full path is interface, then unit number, then family inet, then address: set interfaces ge-1/0/5 unit 100 family inet address 10.20.30.1/24. Omitting the unit stanza entirely leaves the address with no logical unit to attach to, which is invalid syntax for a port that is meant to carry a specific numbered VLAN subscriber unit rather than an implicit default. Reversing the interface name and the unit keyword breaks the required hierarchy order that the Junos CLI parser expects — unit must follow the interface name, not precede it. Pointing the address at lo0 instead of the physical aggregation port misapplies the address to the loopback interface, which is a device-wide virtual interface unrelated to subscriber-facing traffic on ge-1/0/5. As an operational check, show interfaces ge-1/0/5.100 after commit should display the address bound to that exact unit, confirming it landed where intended rather than on the physical interface or a different unit number.