An operator needs to configure a second Virtual Service that re-uses an existing VS IP on a separate service port. How is this handled in the Create VS configuration?

Question

Options

• AIn the Basic Setup Wizard, create the second VS without Auto Allocate, and then type in the
• BIn the Advanced Setup Wizard, create the second VS as a Child Virtual Service.
• CIn the Advanced Setup Wizard, create the second VS without Auto Allocate, and then type in the
• DIn the Advanced Setup Wizard, create the second VS with a "Virtual Service for VIP Sharing":

• A
  16% (5)
• B
  6% (2)
• C
  72% (23)
• D
  6% (2)

Explanation

Option C is correct because sharing an existing VIP across multiple Virtual Services requires manual IP entry, which means disabling Auto Allocate and typing the IP address yourself - the system won't automatically assign an address you've already used. The Advanced Setup Wizard must be used because it exposes the full IP configuration controls needed to override auto-allocation, something the Basic Wizard does not provide.

Why the distractors are wrong:

• A fails because the Basic Setup Wizard lacks the granular IP configuration options required for VIP sharing - basic wizards are intentionally simplified.
• B is wrong because a "Child Virtual Service" is a distinct concept used for SNI-based SSL offloading with parent-child VS relationships, not for sharing a VIP on a different port.
• D is a fabricated option - there is no dedicated "Virtual Service for VIP Sharing" toggle in the create workflow; manual IP entry is the sharing mechanism.

Memory tip: Think "Advanced + Manual = Share" - you need the Advanced wizard for full control, and you go Manual (no Auto Allocate) to reuse the same IP. If the system is picking the IP for you, it will never give you one that's already taken.

No community discussion yet for this question.