READ Free Dumps For Cisco- 400-051
| Question ID 12901 | When a Cisco IOS gatekeeper receives an LRQ, what is the first step it will take in an
attempt to resolve the destination address?
|
| Option A | Check to see if the LRQ reject-unknown-prefix flag is set.
|
| Option B | Check to see if the destination address matches the technology prefix.
|
| Option C | Check to see if the destination address matches the hop-off technology prefix.
|
| Option D | Check to see if the destination address matches the remote zone prefix.
|
| Option E | Check to see if the LRQ forward-queries flag is set.
|
| Correct Answer | B |
Explanation Explanation: LRQ These messages are exchanged between gatekeepers and are used for inter-zone (remote zone) calls. For example, gatekeeper A receives an ARQ from a local zone gateway requesting call admission for a remote zone device. Gatekeeper A then sends an LRQ message to gatekeeper B. Gatekeeper B replies to the LRQ message with either a Location Confirm (LCF) or Location Reject (LRJ) message, which depends on whether it is configured to admit or reject the inter-zone call request and whether the requested resource is registered.
| Question ID 12902 | To which SIP response category does 301 Moved Permanently belong?
|
| Option A | Provisional
|
| Option B | Successful
|
| Option C | Redirection
|
| Option D | Client Failure
|
| Option E | Server Failure
|
| Correct Answer | C |
Explanation Explanation: The 301 response from the Web server should always include an alternative URL to which redirection should occur. If it does, a Web browser will immediately retry the alternative URL. So you never actually see a 301 error in a Web browser, unless perhaps you have a corrupt redirection chain e.g. URL A redirects to URL B which in turn redirects back to URL A. If your client is not a Web browser, it should behave in the same way as a Web browser i.e. immediately retry the alternative URL.