1Y0-231 · Question #41
Scenario: The policies below are bound to a content-switching virtual server. bind cs vserver vserver1 -policyName CSPOL_7 -priority 100 - gotoPriorityExpression NEXT bind cs vserver vserver1…
The correct answer is A. CSPOL_9. CSPOL_9 is correct because NetScaler evaluates content-switching policies in ascending priority order (lower number = evaluated first), and the gotoPriorityExpression NEXT on CSPOL_7 (priority 100) instructs the engine to continue to the very next policy in sequence - which is…
Question
Scenario: The policies below are bound to a content-switching virtual server. bind cs vserver vserver1 -policyName CSPOL_7 -priority 100 - gotoPriorityExpression NEXT bind cs vserver vserver1 -policyName CSPOL_5 -priority 90 bind cs vserver vserver1 -policyName CSPOL_9 -priority 110 bind cs vserver vserver1 -policyName CSPOL_4 -priority 120 bind cs vserver vserver1 -policyName CSPOL_8 -priority 210 If policy CSPOL_7 is invoked, which policy should be invoked next?
Options
- ACSPOL_9
- BCSPOL_8
- CCSPOL_5
- DCSPOL_4
How the community answered
(31 responses)- A81% (25)
- B3% (1)
- C10% (3)
- D6% (2)
Explanation
CSPOL_9 is correct because NetScaler evaluates content-switching policies in ascending priority order (lower number = evaluated first), and the gotoPriorityExpression NEXT on CSPOL_7 (priority 100) instructs the engine to continue to the very next policy in sequence - which is CSPOL_9 at priority 110.
Why the distractors are wrong:
- C (CSPOL_5, priority 90) was already evaluated before CSPOL_7 since 90 < 100 -
NEXTnever goes backward. - D (CSPOL_4, priority 120) is skipped because CSPOL_9 (priority 110) sits between 100 and 120 in the sequence.
- B (CSPOL_8, priority 210) is far down the chain and is not the immediately next policy.
Memory tip: Think of NEXT like a linked list - it always moves to the adjacent higher priority number, not a random jump. Sort the priorities numerically (90 → 100 → 110 → 120 → 210) and NEXT simply advances one step forward in that sorted list.
Topics
Community Discussion
No community discussion yet for this question.