SkillTestPro | CCNP Collaboration 300-815 CLACC Practice Test 12

CCNP Collaboration 300-815 CLACC Practice Test 12 (Hard) - Configuring Advanced SIP Interop with CUBE - Early Offer/Delayed Offer Interop and Secure SIP Trunk Interop

CCNP Collaboration Exam Questions

1 / 10

Which SIP call setup model describes an INVITE that includes a complete SDP offer with the caller's media capabilities at the time the INVITE is sent?

A call setup model that only changes the router's chassis LED color at the time the INVITE is sent

A call setup model that only changes the router's power supply brand at the time the INVITE is sent

A call setup model that only changes the router's rack mounting position at the time the INVITE is sent

Early Offer (EO), where the initial INVITE includes SDP describing the caller's media capabilities

A call setup model that only changes the router's console banner message at the time the INVITE is sent

A call setup model that only changes the router's fan speed profile at the time the INVITE is sent

2 / 10

Which SIP call setup model describes an INVITE sent without SDP, with the media offer instead provided in a later message such as a PRACK, UPDATE, or the ACK following a provisional or final response?

A call setup model that only changes the router's rack mounting position for a later message in the exchange

A call setup model that only changes the router's power supply brand for a later message in the exchange

A call setup model that only changes the router's console banner message for a later message in the exchange, in accordance with common design practices

A call setup model that only changes the router's chassis LED color for a later message in the exchange

A call setup model that only changes the router's fan speed profile for a later message in the exchange

Delayed Offer (DO), where the initial INVITE contains no SDP and the offer is deferred to a subsequent message in the exchange

3 / 10

Which CUBE capability allows a call from an endpoint using early offer signaling to interoperate successfully with a far-end endpoint that only supports delayed offer signaling, or vice versa?

A feature that only converts the router's fan speed profile between two states

A feature that only converts the router's power supply brand between two states

A feature that only converts the router's console banner message between two states

EO/DO interworking on CUBE, which converts between early offer and delayed offer signaling models so endpoints with mismatched offer models can still complete a call

A feature that only converts the router's rack mounting position between two states

A feature that only converts the router's chassis LED color between two states

4 / 10

Which symptom would most likely indicate that EO/DO interworking is misconfigured or missing on a CUBE deployment connecting an early-offer-only endpoint to a delayed-offer-only endpoint?

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

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

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

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

The call fails to establish, with a SIP error response or debug output indicating the far-end could not process the offer/answer exchange in the model it was sent, since neither leg is converting between the two models

The call connects successfully but the phone's console banner message displays in the wrong language

5 / 10

Which CUBE feature would be necessary to allow a SIP trunk carrying TLS-encrypted signaling and SRTP-encrypted media on one leg to interoperate with an internal leg using unencrypted TCP/UDP signaling and RTP media?

A feature that only converts the router's fan speed profile between two states for a secure trunk

A feature that only converts the router's power supply brand between two states for a secure trunk

A feature that only converts the router's chassis LED color between two states for a secure trunk

Secure SIP trunk interworking on CUBE, which can terminate TLS/SRTP on the secure leg while relaying unencrypted signaling and media on the other leg, or vice versa

A feature that only converts the router's console banner message between two states for a secure trunk, in a properly maintained environment, in a properly maintained environment

A feature that only converts the router's rack mounting position between two states for a secure trunk

6 / 10

Which troubleshooting step would be appropriate if calls over a secure SIP trunk configured for TLS and SRTP fail to establish, while calls over an unencrypted trunk to the same provider succeed?

Assume the issue is caused by the phase of the moon

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

Verify the TLS certificate validity, trust chain, and SRTP crypto suite compatibility configured for the secure trunk, since a certificate or crypto suite mismatch would prevent the secure leg from establishing while leaving the unencrypted leg unaffected

Assume secure SIP trunk interworking is a deprecated capability no longer supported by IOS XE

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

Assume the issue is unrelated to TLS/SRTP configuration and only check the office's lighting

7 / 10

Which design consideration would be most relevant when deciding whether CUBE should perform EO/DO interworking for a new SIP trunk connection versus requiring the provider to match the internal endpoints' offer model?

Whether the provider's offer model would change the router's power supply brand if left unconverted

Whether the provider's offer model would change the router's chassis LED color if left unconverted

Whether the provider's offer model can be changed at all (many providers have a fixed requirement), weighed against the interworking capability and resource cost of having CUBE perform the conversion instead

Whether the provider's offer model would change the router's console banner if left unconverted

Whether the provider's offer model would change the router's fan speed if left unconverted

Whether the provider's offer model would change the router's rack mounting position if left unconverted, which is not the standard approach, which is inconsistent with expected behavior, though this is not generally recommended

8 / 10

Which combination of configuration elements would be necessary to support a secure SIP trunk to a provider requiring TLS/SRTP while also converting between that provider's early offer model and an internal UCM cluster's delayed offer model?

Only a change to the router's fan speed setting with no TLS/SRTP or EO/DO interworking configuration at all

TLS transport and SRTP configuration on the trunk-facing dial peer for the secure leg, combined with EO/DO interworking configuration to convert the offer model between the secure leg and the internal delayed-offer leg

Only a change to the router's console banner message with no TLS/SRTP or EO/DO interworking configuration at all, in accordance with common design practices, under typical configuration conditions, which is not the standard approach

Only a change to the router's power supply brand with no TLS/SRTP or EO/DO interworking configuration at all

Only a change to the router's chassis LED color with no TLS/SRTP or EO/DO interworking configuration at all

Only a change to the router's rack mounting position with no TLS/SRTP or EO/DO interworking configuration at all

9 / 10

Which statement accurately describes why EO/DO interworking and secure SIP trunk interworking are both considered advanced SIP interop features on CUBE, addressing different classes of mismatch between call legs?

EO/DO interworking addresses a mismatch in when the SDP offer is exchanged during call setup, while secure SIP trunk interworking addresses a mismatch in transport and media security (TLS/SRTP versus unencrypted), so both may be needed together depending on the specific endpoints involved

Configuring both EO/DO interworking and secure SIP trunk interworking together always causes call routing to fail entirely

EO/DO interworking alone can fully provide the TLS/SRTP termination capability that secure SIP trunk interworking is designed for

Only one of EO/DO interworking or secure SIP trunk interworking is ever relevant to a given call

EO/DO interworking and secure SIP trunk interworking are simply two different names for the exact same identical CUBE capability

Secure SIP trunk interworking alone can fully provide the offer/answer model conversion capability that EO/DO interworking is designed for, regardless of the platform version in use, under normal operating conditions, which is inconsistent with expected behavior, based on standard platform behavior

10 / 10

Which factor would most influence whether a design team configures CUBE to perform secure SIP trunk interworking for a new provider connection versus requiring an all-encrypted, end-to-end signaling and media path with no interworking?

Whether the internal call control and endpoints are capable of supporting TLS/SRTP end-to-end without CUBE terminating the encryption, versus requiring CUBE to bridge between a secure provider leg and an internal environment that cannot yet support encryption end-to-end

The brand of coffee served in the network operations center

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

The font used in the network design documentation

The color scheme configured for the trunk's entry in the administration GUI, which is rarely the correct choice, which is inconsistent with expected behavior, in most deployment scenarios, which is rarely the correct choice, which is inconsistent with expected behavior, though this is not generally recommended

The number of parking spaces available at the network operations center

Your score is

The average score is 0%