Scenario: A Citrix Administrator made changes to a Citrix ADC, deleting parts of the configuration and saving
some new ones. The changes caused an outage that needs to be resolved as quickly as possible. There is no Citrix ADC backup.
What does the administrator need to do to recover the configuration quickly?
What can a Citrix Administrator use to restrict access to the Citrix ADC management IP (NSIP) address?
Scenario: A Citrix Administrator observes that when the client gets redirected to an HTTP 503 response is received from the content switching vServer.
The relevant configuration is as follows:
> add cs action CS_Act_1 -targetLBVserver SERVER_1
> add cs action CS_Act_2 -targetLBVserver SERVER_2
> add cs action CS_Act_3 -targetLBVserver SERVER_3
> add cs action CS_Act_4 -targetLBVserver SERVER_4
> add cs policy CS_Pol_1 -rule "http.REQ.URL path_and_queryCONTAINS(\"connect\")" -action CS_Act_1
> add cs policy CS_Pol_2 -rule "http.REQ.URL path_and_query EQ(\"owa\")" -action CS_Act_2
> add cs policy CS_Pol_3 -rule "http REQ.URL path_and_query CONTAINS(\"owa\")" -action CS_Act_3
> add cs policy CS_Pol_4 -rule "http.REQ.IS_VALID" -action CS_Act_4
> bind cs vServer CS_vserver1 -policyName CS_Pol_1 -priority 110
> bind cs vServer CS_vserver1 -policyName CS_Pol_4 -priority 120
How can the administrator correct the issue?
Where do the monitor probes originate by default, after creating and correctly configuring a custom user monitor?