A physical interface bound to the VRF instance cannot be divided into sub-interfaces.

Question

Options

• ATRUE
• BFALSE

• A
  80% (12)
• B
  20% (3)

Explanation

Option A is correct because once a physical interface is directly bound to a VRF instance, the system treats that interface as fully allocated to that VRF - sub-interface creation requires the physical interface to remain in a "free" or default state so that each sub-interface can be independently assigned (potentially to different VRFs or routing contexts). Binding the VRF at the physical layer locks the interface and prevents further logical subdivision.

Option B is wrong because it implies sub-interfaces can still be created after a VRF binding, which contradicts how VRF binding operates at the physical interface level. The binding is not partial - it applies to the whole interface, leaving no room for sub-interface configuration.

Memory tip: Think of it as a lease agreement - once a physical interface "signs a lease" with a VRF, it can't sublease individual rooms (sub-interfaces) to other tenants. If you need sub-interfaces, assign the VRF to each sub-interface individually instead of to the parent physical interface.

No community discussion yet for this question.