350-801

Free 350-801 practice questions

10 questions from our 350-801 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.

Back to the 350-801 practice exams

Question 1 of 10, Infrastructure and Design

After SAML SSO is enabled cluster-wide on Unified CM, users intermittently fail to sign in. The SSO trace on Unified CM shows that the assertion from the identity provider is rejected because its NotBefore condition lies in the future. What is the MOST likely fix?

  1. ARe-import the identity provider metadata so that the new token-signing certificate is trusted by every node
  2. BPoint Unified CM and the identity provider at the same reliable NTP source so that their clocks agree Correct answer
  3. CEnable OAuth with refresh tokens so that clients stop requesting a new SAML assertion at every sign-in
  4. DSwitch from cluster-wide SSO to per-node agreements so that every node builds its own SAML trust

Answer and explanation: A NotBefore or NotOnOrAfter violation means the clocks of the identity provider and the service provider differ, so the fix is common, accurate NTP. A changed signing certificate produces a signature validation error rather than a timing error. OAuth refresh tokens reduce how often users re-authenticate but would not make a skewed assertion valid. Per-node agreements change how metadata is exchanged and have nothing to do with assertion validity windows.

Question 2 of 10, Infrastructure and Design

A TLS SIP trunk from CUBE to a carrier fails. A debug on CUBE shows that CUBE sends a TLS alert 'unknown CA' after receiving the carrier's certificate. What is the correct fix?

  1. AChange the transport on the dial peer to TCP so that the certificate exchange is skipped entirely
  2. BGenerate a new RSA key pair on CUBE and enroll its identity certificate with the enterprise CA
  3. CAdd the carrier's IP address to the trusted IP address list under voice service voip settings
  4. DImport the carrier's root CA certificate into a trustpoint that CUBE uses for SIP TLS signaling Correct answer

Answer and explanation: The 'unknown CA' alert comes from CUBE, meaning it cannot build a chain to a trusted root for the carrier's certificate, so the carrier's root CA must be trusted on the relevant trustpoint. CUBE's own identity certificate is a separate issue that would cause the carrier to complain instead. Falling back to TCP removes encryption, contradicting the requirement. The IP trust list is a toll-fraud control and does not affect TLS validation.

Question 3 of 10, Protocols and Endpoints

An administrator wants employees to plug in a new auto-registered phone, dial an IVR, enter their primary extension and PIN, and have the phone assigned to them automatically. Which configuration on the end user makes this possible?

  1. AAn activation code generated for the user and a device pool that allows activation code onboarding
  2. BA device mobility info entry for the user's subnet and a default device profile for each phone model
  3. CA user profile with self-provisioning enabled, plus universal line and universal device templates Correct answer
  4. DA BAT phone template plus a CSV file that maps each MAC address to the corresponding user ID

Answer and explanation: Self-provisioning relies on a user profile that allows self-provisioning and references universal device and line templates, combined with the self-provisioning IVR and auto-registration. BAT with a CSV is bulk provisioning done by the administrator, not by the user. Activation codes onboard phones by entering a code rather than through an IVR with extension and PIN. Device mobility and default device profiles do not assign phones to users.

Question 4 of 10, On-Premises Call Control

In a globalized dial plan, incoming PSTN calls arrive with a +E.164 calling number. Users want local callers displayed as seven-digit numbers on their phones. Where should the localization be applied?

  1. AIn the Calling Party Transformation CSS of the called phone or its device pool, reaching local patterns Correct answer
  2. BIn the Incoming Calling Party Settings of the gateway, which prefix or strip digits on calls received from the PSTN
  3. CIn the Called Party Transformation CSS of the gateway, so that outbound digits are localized on egress to the PSTN
  4. DIn a translation pattern placed in the gateway's inbound CSS that strips the country and area code from callers

Answer and explanation: Localizing the number shown on a phone is done with calling party transformation patterns reached through the Calling Party Transformation CSS of the called device or its device pool. Incoming Calling Party Settings on the gateway globalize numbers on entry, the opposite step. A translation pattern in the inbound CSS would localize the number for every destination and break globalized call history and callback. The Called Party Transformation CSS changes the dialed number on egress, not the caller display.

Question 5 of 10, On-Premises Call Control

A company with six branches wants a single +E.164 route pattern for PSTN calls. Each call must leave through the gateway of the branch where the calling phone is located. Which design meets this with the LEAST configuration?

  1. APoint the pattern to a route list containing the Standard Local Route Group and set it per device pool Correct answer
  2. BUse AAR groups per branch so that calls follow the local gateway when bandwidth to the hub runs out
  3. CConfigure Device Mobility so that phones roaming between branches change their route list automatically
  4. DCreate one partition and one route pattern per branch and give each branch's phones a dedicated line CSS

Answer and explanation: The Standard Local Route Group in a route list is resolved at call time from the Local Route Group set on the caller's device pool, so one pattern serves every branch. Per-branch partitions and patterns work but multiply the dial plan, which is what local route groups avoid. AAR reroutes calls blocked by call admission control and does not select the normal egress gateway. Device Mobility changes device pool settings for roaming phones but still relies on local route groups to pick the gateway.

Question 6 of 10, On-Premises Call Control

An attacker calls in through the PSTN gateway, reaches a user's phone, and transfers the call to an international number. Which Unified CM configuration directly blocks this off-net-to-off-net transfer?

  1. ASet the Block OffNet To OffNet Transfer service parameter to True and classify gateways and trunks as OffNet Correct answer
  2. BRemove the international route pattern from the gateway's inbound CSS and keep it in the phone line CSS
  3. CConfigure a Forced Authorization Code on the international pattern so that every user must enter a code first
  4. DSet the Drop Ad Hoc Conference parameter so conferences end when the conference controller hangs up

Answer and explanation: With Block OffNet To OffNet Transfer enabled, Unified CM refuses transfers between two parties classified as OffNet, which stops the gateway-to-gateway pattern described. The transfer is made with the user's CSS, so trimming the gateway's inbound CSS alone does not help. FAC would prompt the transferring user for a code but is not aimed at inbound callers abusing a transfer. Drop Ad Hoc Conference settings address conference-based fraud, not blind or consultative transfers.

Question 7 of 10, Voice Gateways and Session Border Controllers

A CUBE has no dial peer with incoming called-number configured. Dial peer 100 has destination-pattern 408555.... and dial peer 200 has answer-address 408555.... An inbound SIP call arrives from 4085551234. Which inbound dial peer is matched?

  1. ADial peer 200, because answer-address is evaluated before destination-pattern during inbound matching Correct answer
  2. BDefault dial peer 0, because no dial peer contains incoming called-number for the dialed DNIS digits
  3. CDial peer 100, because destination-pattern is checked against the calling number before answer-address
  4. DDial peer 100, because when two inbound candidates tie, the lower dial peer tag is always selected

Answer and explanation: For inbound matching, IOS XE checks incoming URI, then incoming called-number, then answer-address against the calling number, and only then destination-pattern against the calling number, so dial peer 200 wins. Destination-pattern is a later fallback for inbound matching. Default dial peer 0 is used only when nothing matches at all. Dial peer tag order does not decide between different match criteria.

Question 8 of 10, Cloud and Hybrid Services

A small Webex Calling location has no gateway of its own. Its PSTN calls must use the Local Gateway trunk that already serves headquarters, with the headquarters numbers range unaffected. Which configuration achieves this?

  1. AConfigure unknown extension routing at the small location toward the headquarters trunk
  2. BMove all users of the small location into the headquarters location so that they share its PSTN access
  3. CSet the small location's PSTN connection to the route group that contains the headquarters trunk Correct answer
  4. DCreate a dial plan with a +! pattern pointing to the headquarters trunk for every location

Answer and explanation: A location's premises-based PSTN connection can point to a route group whose trunks belong to another location, so the small site can share the headquarters gateway while keeping its own location settings. Merging users loses location-specific settings such as emergency data. Dial plans route enterprise patterns, not PSTN breakout for all numbers. Unknown extension routing handles internal extensions, not PSTN calls.

Question 9 of 10, Cloud and Hybrid Services

During a phased migration, Webex Calling users must reach 4-digit extensions 5000–5999 that still live on an on-premises PBX through a Local Gateway. Which Webex Calling configuration is required?

  1. AAn outgoing calling permission that allows internal calls to numbers outside the org
  2. BA virtual line for each extension so that Webex Calling users see them as internal
  3. CA translation pattern that converts the extensions to E.164 and sends them to the PSTN
  4. DA dial plan with that pattern, pointing to a trunk or route group toward the gateway Correct answer

Answer and explanation: Dial plans in Webex Calling hold dial patterns for premises-based destinations and send matching calls to a trunk or route group, here the Local Gateway toward the PBX. Routing extensions through the PSTN adds cost and fails if the numbers are not DID-capable. Outgoing permissions control what users may dial, not where the call goes. Virtual lines are cloud lines, not a way to reach a PBX.

Question 10 of 10, Media and QoS

An engineer reviews streaming statistics on a Cisco IP phone after a poor-quality call. Which metric shows the proportion of received audio that had to be synthesized because packets were lost or late?

  1. AAvg Jitter
  2. BConcealment ratio Correct answer
  3. CRcvr Lost Packets count
  4. DSender Codec

Answer and explanation: Concealment ratio and related conceal seconds measure how much audio the phone had to fill in because packets were missing or late. The lost packet count shows how many packets never arrived but not how much audio was synthesized, and late packets are not counted there. Average jitter describes delay variation, not concealment. The sender codec only describes the codec in use.