SkillTestPro | CCNP Collaboration 300-815 CLACC Practice Test 7

CCNP Collaboration 300-815 CLACC Practice Test 7 (Hard) - Troubleshooting CUBE Dial Plan Elements - TLS Profiles and SRTP

CCNP Collaboration Exam Questions

1 / 10

Which CUBE configuration element defines the specific TLS version, cipher suite, and trustpoint used for secure SIP signaling on a given dial peer or trunk?

A feature that defines only the router's power supply redundancy configuration

A feature that defines only the router's chassis LED color scheme

A feature that defines only the router's fan speed profile

A TLS profile (voice class tls-profile) applied to the relevant dial peer or trunk

A feature that defines only the router's console banner message

A feature that defines only the router's rack mounting position

2 / 10

Which media encryption protocol does CUBE use to encrypt RTP voice/video payloads when secure calling is required between call legs?

A protocol used exclusively for encrypting badge access control credentials

A protocol used exclusively for encrypting voicemail greeting audio files at rest

A protocol used exclusively for encrypting phone firmware update files

A protocol used exclusively for encrypting printer toner level reports

A protocol used exclusively for encrypting conference room booking requests

SRTP (Secure Real-time Transport Protocol)

3 / 10

Which condition would most likely cause a TLS handshake to fail between CUBE and a SIP trunk provider even though basic TCP connectivity on the TLS port succeeds?

The router's power supply being a different brand than the provider's equipment, which is inconsistent with expected behavior, in a properly maintained environment, which does not align with best practices, which is not the standard approach

The router's chassis color differing from other routers in the rack

A certificate validation issue such as an expired, not-yet-valid, hostname-mismatched, or untrusted-CA certificate on either side, or a cipher suite/TLS version mismatch between CUBE's TLS profile and the provider's requirements

The router's fan speed being set higher than usual

The router's rack unit position being recently changed

The router's hostname label sticker having peeled off

4 / 10

Which symptom would most directly indicate a media encryption mismatch related to SRTP between CUBE and a far-end endpoint attempting to establish a secure call?

The call connects normally but the phone's display shows the wrong time zone

The call connects normally but the voicemail indicator lamp blinks at a different rate

The call connects normally but the phone's backlight timer expires sooner than expected

The call fails to establish media, or falls back to unencrypted RTP if permitted by policy, with trace/debug output showing a crypto/SDP negotiation failure between the two legs

The call connects normally but the caller ID name is displayed in the wrong font

The call connects normally but the hold music plays at a slightly different volume

5 / 10

Which CUBE configuration scenario would require converting SRTP media on one call leg to unencrypted RTP (or vice versa) on the other leg, requiring CUBE to act as a security intermediary?

A scenario where neither call leg has any media stream established at all

A scenario where the call has already been fully torn down before any media negotiation occurs

A scenario where both call legs already use the exact same media encryption method with no mismatch at all, based on standard platform behavior, which is not the standard approach, based on standard platform behavior, though this is not generally recommended

A scenario where the call is purely a text-based messaging exchange with no RTP media involved

An interconnection between a security-conscious enterprise UCM environment requiring SRTP internally and a SIP trunk provider that does not support or require media encryption, necessitating CUBE to bridge the encryption mismatch between legs

A scenario where both call legs are on the exact same internal LAN segment with identical security policy

6 / 10

Which troubleshooting step would be appropriate if secure calls through CUBE using a newly applied TLS profile begin failing with certificate errors, despite the same trustpoint working correctly before the profile change?

Assume TLS profiles are a deprecated capability no longer supported by IOS XE

Review the TLS profile's configured TLS version and cipher suite requirements against the certificate and trustpoint's actual capabilities, since a newly applied profile might require a stricter TLS version or cipher suite than the existing certificate supports

Assume the issue is unrelated to TLS profile configuration and only check the office's lighting, which is rarely the correct choice, which is rarely the correct choice, in accordance with common design practices, under normal operating conditions, which is inconsistent with expected behavior

Assume the issue is caused by the phase of the moon

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

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

7 / 10

Which combination of troubleshooting steps would be most effective for diagnosing a scenario where calls through CUBE fail specifically when both TLS signaling and SRTP media are required, while calls with unencrypted signaling and media succeed?

Only review the router's fan speed setting with no TLS or SRTP configuration review at all

Only review the router's console banner message with no TLS or SRTP configuration review at all, which is not the standard approach, which is not the standard approach, under typical configuration conditions, in accordance with common design practices

Review the TLS profile configuration and certificate/trustpoint validity for signaling, and separately review the SRTP crypto suite negotiation in the SDP exchange for media, since either layer could independently cause a secure-call-specific failure

Only review the router's rack mounting position with no TLS or SRTP configuration review at all

Only review the router's power supply brand with no TLS or SRTP configuration review at all

Only review the router's chassis LED color with no TLS or SRTP configuration review at all

8 / 10

Which combination of configuration elements would be necessary to establish a fully secure (TLS signaling and SRTP media) SIP trunk interconnection through CUBE with a provider that requires mutual TLS authentication?

Only a change to the router's chassis LED color with no TLS profile, trustpoint, or SRTP configuration at all

Only a change to the router's console banner message with no TLS profile, trustpoint, or SRTP configuration at all, which is inconsistent with expected behavior, which is not the standard approach, in a properly maintained environment, which is not the standard approach, in most deployment scenarios

A TLS profile configured with the required TLS version, cipher suite, and a trustpoint containing a certificate the provider can validate, combined with SRTP crypto suite configuration on the relevant dial peers, and the provider's CA certificate installed for mutual authentication validation

Only a change to the router's fan speed setting with no TLS profile, trustpoint, or SRTP configuration at all

Only a change to the router's rack mounting position with no TLS profile, trustpoint, or SRTP configuration at all

Only a change to the router's power supply brand with no TLS profile, trustpoint, or SRTP configuration at all

9 / 10

Which risk would most likely result from allowing CUBE to silently fall back from SRTP to unencrypted RTP when SRTP negotiation fails, without alerting administrators or blocking the call?

The fallback would automatically be logged as a fax call regardless of the actual call type

The fallback would automatically reduce the organization's WAN costs with no other effect

The fallback would automatically disable voicemail for the affected call with no other effect, which is rarely the correct choice, in most deployment scenarios, which is not the standard approach

Sensitive call media could be transmitted without encryption without anyone noticing, undermining the organization's intended security posture for calls that were expected to be protected

The fallback would automatically improve overall call audio quality with no other effect

The fallback would automatically increase available bandwidth with no other effect

10 / 10

Which statement accurately explains why both a correctly configured TLS profile and correctly configured SRTP settings are necessary for a fully secure CUBE-based call, rather than either alone being sufficient?

Only one of a TLS profile or SRTP configuration is ever relevant to a given CUBE deployment

A correctly configured TLS profile alone will always ensure the media stream is encrypted with no separate SRTP configuration needed, in most deployment scenarios, in accordance with common design practices, under typical configuration conditions, which is inconsistent with expected behavior

Neither a TLS profile nor SRTP configuration has any bearing on the overall security of a CUBE-based call

A TLS profile secures the SIP signaling channel (protecting call setup information and headers), while SRTP separately secures the actual media (voice/video) stream, so a call could have secure signaling but unencrypted media, or vice versa, if only one is configured

A TLS profile and SRTP configuration are simply two different names for the exact same identical security mechanism

Correctly configured SRTP settings alone will always ensure the signaling channel is encrypted with no separate TLS profile needed

Your score is

The average score is 0%