Which statement accurately explains why testing SIP SRST fallback behavior under a simulated WAN outage is an important validation step, rather than assuming a syntactically correct configuration guarantees correct fallback behavior?
Correct Answer: A syntactically valid SRST configuration can still fail to provide working fallback service due to issues such as incomplete dial-peer coverage, incorrect directory number matching, or unreachable PSTN paths from the branch router, so simulated testing confirms the fallback actually functions as intended
Explanation: Syntactic correctness doesn't guarantee working fallback since dial-peer coverage, DN matching, or PSTN reachability could still be wrong, so simulated testing validates actual behavior, unlike claiming syntax guarantees correctness, calling testing purely cosmetic, restricting testing to non-UCME deployments, limiting testing to initial installation, or claiming testing requires an actual unplanned outage.
Correct Answer: A syntactically valid SRST configuration can still fail to provide working fallback service due to issues such as incomplete dial-peer coverage, incorrect directory number matching, or unreachable PSTN paths from the branch router, so simulated testing confirms the fallback actually functions as intended
Explanation: Syntactic correctness doesn't guarantee working fallback since dial-peer coverage, DN matching, or PSTN reachability could still be wrong, so simulated testing validates actual behavior, unlike claiming syntax guarantees correctness, calling testing purely cosmetic, restricting testing to non-UCME deployments, limiting testing to initial installation, or claiming testing requires an actual unplanned outage.