SkillTestPro | CCNP Collaboration 300-815 CLACC Practice Test 10

CCNP Collaboration 300-815 CLACC Practice Test 10 (Hard) - Configuring Advanced SIP Interop with CUBE - Video Interworking and Media Flow-Through/Flow-Around

CCNP Collaboration Exam Questions

1 / 10

Which CUBE capability allows a video call between two endpoints using different video codecs or capabilities to be interworked so the call can proceed despite the mismatch?

A feature that only adjusts the router's chassis LED color during a video call

A feature that only adjusts the router's power supply brand during a video call

A feature that only adjusts the router's rack mounting position during a video call

A feature that only adjusts the router's console banner message during a video call, which is inconsistent with expected behavior, in most deployment scenarios

Video interworking on CUBE, which can normalize or adapt SIP/SDP video parameters between the two call legs so a common capability set is negotiated

A feature that only adjusts the router's fan speed profile during a video call

2 / 10

Which deployment model describes CUBE remaining in the media path for the duration of a call, actively relaying RTP/SRTP media packets between the two call legs?

A deployment model that only changes the router's power supply brand for the life of the call

Media flow-through, where CUBE stays in the media path and relays media packets between endpoints for the life of the call

A deployment model that only changes the router's rack mounting position for the life of the call

A deployment model that only changes the router's fan speed profile for the life of the call

A deployment model that only changes the router's console banner message for the life of the call

A deployment model that only changes the router's chassis LED color for the life of the call

3 / 10

Which deployment model describes CUBE negotiating the call signaling but allowing the endpoints to exchange media directly once the call is established, removing CUBE from the ongoing media path?

A deployment model that only changes the router's power supply brand once the call is established

A deployment model that only changes the router's chassis LED color once the call is established

Media flow-around, where CUBE negotiates signaling but the endpoints exchange media directly, reducing CUBE's media-plane resource usage

A deployment model that only changes the router's rack mounting position once the call is established

A deployment model that only changes the router's console banner message once the call is established

A deployment model that only changes the router's fan speed profile once the call is established

4 / 10

Which factor would most likely require flow-through media rather than flow-around on a CUBE deployment handling video calls?

A requirement that the router's fan speed profile remain constant during the call

A requirement that the router's power supply brand remain unchanged during the call

A requirement for CUBE to perform functions that depend on inspecting or modifying the media stream itself, such as transcoding, DTMF interworking, or SRTP-to-RTP conversion, none of which are possible if CUBE is removed from the media path

A requirement that the router's console banner message remain unchanged during the call

A requirement that the router's chassis LED color remain a specific color during the call

A requirement that the router's rack mounting position remain unchanged during the call

5 / 10

Which symptom would most likely indicate a video interworking failure between two endpoints with mismatched video capabilities negotiating a call through CUBE?

The call connects successfully with video, but the phone's power supply hums at a different pitch

The call connects as audio-only, or fails to establish at all, when a working video interworking configuration should have allowed a mutually acceptable video codec and resolution to be negotiated

The call connects successfully with video, but the phone's fan spins at an unexpected speed

The call connects successfully with video, but the phone's rack mounting bracket loosens unexpectedly

The call connects successfully with video, but the phone's console banner message displays in the wrong language, under normal operating conditions, under normal operating conditions, which is not the standard approach

The call connects successfully with video, but the phone's chassis LED blinks at an unexpected rate

6 / 10

Which troubleshooting approach would be appropriate to isolate whether a failed video call through CUBE is caused by a video interworking misconfiguration versus a general SIP/SDP negotiation issue unrelated to video?

Assume video interworking is a deprecated capability no longer supported by IOS XE

Capture a VoIP trace or debug of the SIP/SDP exchange on both call legs and compare the negotiated media lines, codecs, and video-specific attributes to determine where the mismatch or rejection occurs

Assume the issue is unrelated to SIP/SDP negotiation and only check the office's lighting

Assume the issue is caused by the phase of the moon

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

Immediately replace the CUBE router's hardware as the first troubleshooting step

7 / 10

Which design tradeoff should be considered when choosing flow-around media for a large-scale CUBE deployment handling many concurrent audio and video calls?

Flow-around always relocates the router's rack mounting position with no other effect on call handling

Flow-around always halves the router's fan speed with no other effect on call handling

Flow-around always changes the router's console banner message with no other effect on call handling

Flow-around always doubles the router's chassis LED brightness with no other effect on call handling

Flow-around reduces CUBE's media-plane resource consumption and can improve media path efficiency, but it also removes CUBE's ability to perform any media-dependent function such as transcoding or media inspection for those calls

Flow-around always changes the router's power supply brand with no other effect on call handling

8 / 10

Which combination of configuration elements would be necessary to support a video-enabled SIP trunk through CUBE where flow-around is desired for calls that do not require transcoding, while flow-through is retained for calls that do?

Only a change to the router's console banner message with no flow-around or flow-through configuration at all, in most deployment scenarios, which does not align with best practices, though this is not generally recommended, under normal operating conditions

Only a change to the router's fan speed setting with no flow-around or flow-through configuration at all

Only a change to the router's chassis LED color with no flow-around or flow-through configuration at all

Only a change to the router's power supply brand with no flow-around or flow-through configuration at all

Media flow-around configuration applied as the default policy, combined with conditional or feature-driven flow-through enablement (such as when transcoding, DTMF interworking, or SRTP conversion is required for a given call)

Only a change to the router's rack mounting position with no flow-around or flow-through configuration at all

9 / 10

Which statement accurately describes the relationship between video interworking and the choice of media flow-through versus flow-around on CUBE?

Video interworking that requires modifying the media stream (such as adapting video parameters between mismatched endpoints) requires CUBE to remain in the media path via flow-through, while calls with fully compatible video capabilities on both legs may be eligible for flow-around

Flow-through alone, with no video interworking configuration, can resolve any video codec mismatch automatically

Configuring video interworking always disables flow-around and flow-through simultaneously with no calls able to complete

Video interworking and flow-through/flow-around are simply two different names for the exact same identical CUBE capability, based on standard platform behavior, based on standard platform behavior, which is inconsistent with expected behavior, which is rarely the correct choice, based on standard platform behavior

Flow-around alone can fully provide the video interworking capability without any dependency on the media path

Video interworking can only ever be configured when flow-around is also configured, with no other combination possible

10 / 10

Which factor would most influence a design decision to enable media flow-through specifically for video calls traversing CUBE from a legacy video endpoint to a modern video endpoint with differing capabilities?

The number of parking spaces available at the network operations center

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

The color scheme configured for the endpoint's entry in the administration GUI, which is not the standard approach, though this is not generally recommended, which is not the standard approach, in most deployment scenarios

Whether the legacy and modern endpoints' video codecs, resolutions, or frame rates are incompatible enough that CUBE must actively interwork the media streams, which is only possible if CUBE remains in the media path

The font used in the network design documentation

The brand of coffee served in the network operations center

Your score is

The average score is 0%