While configuring the VRF Selection feature, you get an error message after typing the below statement: Router(config)#no vrf selection source 172.16.0.0 255.255.0.0 vrf VRF1 Which action caused this

Question

Options

• Athe entry of an inconsistent IP address and mask for VRF Selection
• Ban attempt to configure a VRF instance on an interface that already has VRF Selection configured
• Can attempt to remove a VRF Selection entry that does not exist
• Dan attempt to configure a VRF Selection table that does not exist

• A
  13% (3)
• B
  8% (2)
• C
  75% (18)
• D
  4% (1)

Explanation

Option C is correct because the no keyword attempts to remove an existing VRF Selection entry, and if that exact entry (source network 172.16.0.0 255.255.0.0 mapped to VRF1) was never configured in the first place, the router has nothing to delete and returns an error.

Why the distractors are wrong:

• A is incorrect because 172.16.0.0 255.255.0.0 is a perfectly valid and consistent network/mask pair (a standard /16); there is no mismatch.
• B is incorrect because this is a global configuration command (config#), not an interface-level command, so interface VRF conflicts are not the issue here.
• D is incorrect because the error is not about the VRF instance (VRF1) being undefined - it's about the source entry being absent from the VRF Selection table.

Memory tip: Think of the no command like trying to erase writing that was never on the whiteboard - the router will complain because there is nothing there to erase. Whenever you see a no form of a command producing an error, your first instinct should be "does this entry actually exist?"

No community discussion yet for this question.