SkillTestPro | CCNP Collaboration 300-815 CLACC Practice Test 2

CCNP Collaboration 300-815 CLACC Practice Test 2 (Hard) - Media Optimization and NAT Traversal Protocols - STUN, TURN, and ICE

CCNP Collaboration Exam Questions

1 / 10

Which protocol allows an endpoint behind a NAT device to discover its own public-facing IP address and port as seen by devices outside the NAT?

STUN (Session Traversal Utilities for NAT)

A protocol used exclusively for managing badge access control readers

A protocol used exclusively for tracking printer toner levels across the network

A protocol used exclusively for synchronizing phone firmware update schedules

A protocol used exclusively for distributing voicemail greeting audio files

A protocol used exclusively for scheduling conference room bookings

2 / 10

Which protocol provides a relay service that endpoints can use to exchange media when a direct peer-to-peer path cannot be established due to restrictive NAT or firewall behavior?

A protocol used exclusively for badge access control readers with no relationship to media relay

A protocol used exclusively for phone firmware update scheduling with no relationship to media relay

A protocol used exclusively for voicemail greeting distribution with no relationship to media relay

A protocol used exclusively for conference room booking with no relationship to media relay

TURN (Traversal Using Relays around NAT)

A protocol used exclusively for printer toner level tracking with no relationship to media relay

3 / 10

Which framework combines candidate address gathering (including STUN and TURN candidates) with connectivity checks to determine the best available media path between two endpoints?

A framework used exclusively for scheduling conference room bookings

A framework used exclusively for managing badge access control readers

A framework used exclusively for tracking printer toner levels across the network

A framework used exclusively for synchronizing phone firmware update schedules

ICE (Interactive Connectivity Establishment)

A framework used exclusively for distributing voicemail greeting audio files

4 / 10

Which ICE candidate type represents an endpoint's locally assigned IP address and port before any NAT translation is applied?

A server-reflexive candidate obtained exclusively from a STUN server with no local addressing involved

A relay candidate obtained exclusively from a TURN server with no local addressing involved

A candidate type that represents only the phone's ringtone configuration

A candidate type that represents only the phone's wallpaper image

A candidate type that represents only the phone's display brightness setting

A host candidate

5 / 10

Which ICE candidate type is obtained by querying a STUN server and represents the endpoint's translated public address and port as seen from outside a NAT?

A host candidate, which represents the endpoint's own local address before translation

A relay candidate, which represents an address allocated on a TURN relay server

A candidate type that represents only the phone's display brightness setting

A candidate type that represents only the phone's wallpaper image

A candidate type that represents only the phone's ringtone configuration

A server-reflexive candidate

6 / 10

Which outcome would occur during ICE connectivity checks if no direct host-to-host or server-reflexive path succeeds between two endpoints behind restrictive, symmetric NAT devices?

ICE would fall back to using relay candidates obtained via TURN, routing media through the relay server since a direct peer-to-peer path could not be established

The call would automatically disable all media encryption to simplify NAT traversal

The call would automatically be converted into a video-only call with no audio component

The call would automatically be routed to voicemail regardless of call state

The call would automatically double its allocated bandwidth to compensate for the NAT restriction

The call would automatically be logged as answered even though no media path was established

7 / 10

Which troubleshooting step would be appropriate if two endpoints behind different NAT devices experience call setup success but no media flows, with SDP showing only host candidates and no server-reflexive or relay candidates present?

Assume the issue is caused by the phase of the moon

Verify that the endpoints or intermediary devices are correctly configured with reachable STUN and/or TURN server addresses, since the absence of server-reflexive or relay candidates suggests ICE candidate gathering did not complete successfully

Assume the issue is unrelated to candidate gathering and only check the office's lighting

Immediately replace both endpoints' hardware as the first troubleshooting step

Assume the issue is caused by the endpoints' ringtone assignment with no further investigation

Assume ICE, STUN, and TURN are deprecated capabilities no longer relevant to modern deployments, in most deployment scenarios, based on standard platform behavior, under normal operating conditions, which is inconsistent with expected behavior, under typical configuration conditions

8 / 10

Which design consideration would most influence whether an organization deploys a dedicated TURN relay server as part of its remote access media traversal strategy?

The font used in the network design documentation

The brand of coffee served in the network operations center

The color scheme configured for the TURN server's administration interface

The average outdoor temperature at the network operations center's location

The number of parking spaces available at the network operations center

The expected proportion of remote or external endpoints behind restrictive, symmetric NAT or firewall configurations where direct or server-reflexive media paths are unlikely to succeed, requiring relay fallback

9 / 10

Which combination of ICE, STUN, and TURN behaviors would provide the most efficient media path selection for a call between two endpoints, one on the internal network and one remote behind restrictive NAT?

Disabling candidate gathering entirely and assuming a direct host-to-host path will always succeed

Performing connectivity checks in a purely random order with no preference for more direct paths

ICE gathers host, server-reflexive (via STUN), and relay (via TURN) candidates from both endpoints, performs connectivity checks in priority order favoring more direct paths, and only falls back to the TURN relay path if direct or server-reflexive connectivity checks fail

Selecting the relay candidate first and only falling back to host or server-reflexive candidates if the relay fails, which is inconsistent with expected behavior, though this is not generally recommended, which is rarely the correct choice, in a properly maintained environment

Always using the TURN relay path exclusively regardless of whether a more direct path would succeed

Disabling STUN entirely and relying solely on manually configured static public IP addresses for every endpoint

10 / 10

Which statement accurately explains why STUN, TURN, and ICE are typically used together rather than any single one alone being sufficient for reliable NAT traversal in collaboration deployments?

Using all three of STUN, TURN, and ICE together always causes call setup to fail

STUN alone only reveals translated addresses but does not help when NAT behavior prevents direct connectivity even with that knowledge, TURN alone would always relay media even when a more efficient direct path exists, and ICE ties both together with connectivity checks to select the best available path only falling back to relay when necessary

TURN alone can perform every function that ICE is designed for, making ICE unnecessary

STUN, TURN, and ICE are simply three different names for the exact same identical NAT traversal mechanism

Only one of STUN, TURN, or ICE could ever be relevant to a given NAT traversal scenario

STUN alone can perform every function that TURN is designed for, making TURN unnecessary

Your score is

The average score is 0%