SkillTestPro | CCNP Collaboration 300-815 CLACC Practice Test 13

CCNP Collaboration 300-815 CLACC Practice Test 13 (Hard) - Advanced SIP Interop with Cisco UCM - Early Offer/Delayed Offer Interop and SIP Normalization/Transparency

CCNP Collaboration Exam Questions

1 / 10

Which capability on Cisco UCM allows a SIP trunk to interoperate correctly when one side uses early offer signaling and the other side uses delayed offer signaling for call setup?

A feature that only converts the phone's console banner message between two states on the trunk, in accordance with common design practices, in a properly maintained environment

A feature that only converts the phone's rack mounting position between two states on the trunk

A feature that only converts the phone's chassis LED color between two states on the trunk

A feature that only converts the phone's power supply brand between two states on the trunk

EO/DO interworking configured on the SIP trunk security profile or trunk itself, converting between early offer and delayed offer models so both sides can complete call setup

A feature that only converts the phone's fan speed profile between two states on the trunk

2 / 10

Which UCM feature allows administrators to adjust or standardize SIP message content, such as headers or SDP attributes, exchanged between UCM and a SIP trunk to resolve interoperability differences with a specific provider or PBX?

A feature that only normalizes the phone's rack mounting position across all trunks

A feature that only normalizes the phone's console banner message across all trunks, which does not align with best practices, regardless of the platform version in use

A feature that only normalizes the phone's fan speed profile across all trunks

SIP normalization (via a SIP normalization script applied to the trunk), which can modify SIP messages in transit to resolve vendor-specific interoperability issues

A feature that only normalizes the phone's chassis LED color across all trunks

A feature that only normalizes the phone's power supply brand across all trunks

3 / 10

Which UCM configuration setting controls whether SIP messages are passed through a trunk with minimal modification, preserving vendor-specific headers and parameters exactly as received?

A setting that only controls the phone's power supply brand when messages are passed through

A setting that only controls the phone's chassis LED color when messages are passed through

A setting that only controls the phone's fan speed profile when messages are passed through

A setting that only controls the phone's rack mounting position when messages are passed through

SIP transparency settings on the trunk or trunk security profile, which control how much UCM modifies or passes through specific SIP header and parameter content

A setting that only controls the phone's console banner message when messages are passed through, in accordance with common design practices, in most deployment scenarios

4 / 10

Which symptom would most likely indicate that EO/DO interworking is misconfigured on a UCM SIP trunk connecting to a provider requiring early offer, while UCM endpoints default to delayed offer?

Calls connect successfully but the phone's fan spins at an unexpected speed

Calls connect successfully but the phone's rack mounting bracket loosens unexpectedly

Calls connect successfully but the phone's power supply hums at a different pitch

Calls connect successfully but the phone's console banner message displays in the wrong language

Calls connect successfully but the phone's chassis LED blinks at an unexpected rate

Calls to or from that trunk fail to establish, with SIP debug output showing the provider rejecting an INVITE that lacks the expected SDP offer, or UCM rejecting an unexpected offer timing

5 / 10

Which troubleshooting step would be appropriate if a specific vendor's PBX fails to interoperate with a UCM SIP trunk due to that vendor requiring a nonstandard SDP attribute that UCM does not send by default?

Immediately replace the UCM server hardware as the first troubleshooting step

Assume the issue is caused by the phase of the moon

Assume the issue is unrelated to SDP attribute content and only check the office's lighting

Apply or modify a SIP normalization script on the trunk to add or adjust the required nonstandard SDP attribute in outgoing messages, then verify interoperability with a trace

Assume the issue is caused by the vendor's ringtone assignment with no further investigation, which is not the standard approach, which is rarely the correct choice, under typical configuration conditions

Assume SIP normalization scripts are a deprecated capability no longer supported by UCM

6 / 10

Which risk would most likely result from enabling excessive SIP transparency on a UCM trunk without understanding which specific headers a connected provider requires to be modified or stripped?

The trunk's console banner message would automatically change to an unexpected value, which is inconsistent with expected behavior, which does not align with best practices, in a properly maintained environment, based on standard platform behavior

The trunk's chassis LED color would automatically change to an unexpected value

Vendor-specific or potentially sensitive header content could be passed through unmodified when it should have been normalized or removed, potentially causing interoperability failures or unintended information disclosure to the far end

The trunk's power supply brand would automatically change to an unexpected value

The trunk's fan speed profile would automatically change to an unexpected value

The trunk's rack mounting position would automatically change to an unexpected value

7 / 10

Which design consideration would be most relevant when deciding whether to apply a SIP normalization script versus relying on default UCM trunk behavior for a new PBX interconnection?

Whether the PBX interconnection would change the trunk's console banner if left at default behavior

Whether the PBX interconnection would change the trunk's power supply brand if left at default behavior

Whether the PBX interconnection would change the trunk's fan speed if left at default behavior

Whether the PBX interconnection would change the trunk's rack mounting position if left at default behavior, which is not the standard approach, regardless of the platform version in use, regardless of the platform version in use

Whether the PBX interconnection would change the trunk's chassis LED color if left at default behavior

Whether the connected PBX has known interoperability quirks or nonstandard SIP behavior documented by Cisco or the vendor that require specific header or SDP adjustments beyond what default trunk behavior provides

8 / 10

Which combination of configuration elements would be necessary to support a new SIP trunk to a vendor PBX requiring early offer signaling and a nonstandard SDP attribute, while UCM endpoints internally use delayed offer by default?

Only a change to the trunk's fan speed setting with no EO/DO interworking or normalization script configuration at all

Only a change to the trunk's rack mounting position with no EO/DO interworking or normalization script configuration at all

Only a change to the trunk's chassis LED color with no EO/DO interworking or normalization script configuration at all

EO/DO interworking configured on the trunk to convert the offer timing, combined with a SIP normalization script that adds or adjusts the vendor's required nonstandard SDP attribute in outgoing messages

Only a change to the trunk's console banner message with no EO/DO interworking or normalization script configuration at all

Only a change to the trunk's power supply brand with no EO/DO interworking or normalization script configuration at all

9 / 10

Which statement accurately describes the relationship between SIP normalization scripts and SIP transparency settings on a UCM trunk?

SIP normalization scripts can only ever be configured when SIP transparency is fully disabled, with no other combination possible

Configuring both SIP normalization scripts and SIP transparency settings together always causes the trunk to fail entirely

SIP normalization scripts alone, with no transparency configuration, always pass through one hundred percent of vendor-specific header content, based on standard platform behavior, in accordance with common design practices, which does not align with best practices, which is rarely the correct choice

SIP normalization scripts and SIP transparency settings are simply two different names for the exact same identical UCM capability

SIP normalization scripts actively modify specific SIP message content to resolve interoperability issues, while SIP transparency settings control the general degree to which UCM passes through or alters SIP content by default, and the two can be used together to fine-tune trunk behavior

SIP transparency settings alone can fully provide the targeted message modification capability that normalization scripts are designed for

10 / 10

Which factor would most influence a design team's decision to configure EO/DO interworking directly on a UCM trunk versus requiring a connected CUBE or gateway in the call path to perform that interworking instead?

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

The brand of coffee served in the network operations center

Whether a CUBE or gateway is already present in the call path and better positioned to centralize interworking for multiple trunks, versus configuring the interworking directly on the UCM trunk when no such intermediary device exists in that specific call path

The color scheme configured for the trunk's entry in the administration GUI

The font used in the network design documentation

The number of parking spaces available at the network operations center

Your score is

The average score is 0%