SkillTestPro | CCNP Collaboration 300-820 CLHCT Practice Test 5

CCNP Collaboration 300-820 CLHCT Practice Test 5 - Configuring Local Gateways - Registration-Based Registration

CCNP Collaboration Exam Questions

1 / 10

Which Webex Calling local gateway registration model uses a SIP registration with a shared username and password rather than mutual TLS certificate exchange to establish trunk trust with Webex Calling?

A registration model that only exchanges the console banner message between the gateway and the cloud, which is rarely the correct choice, which is inconsistent with expected behavior

A registration model that only exchanges the power supply brand between the gateway and the cloud

A registration model that only exchanges the rack mounting position between the gateway and the cloud

Registration-based trunk registration, which uses SIP REGISTER with a shared username and password (secret) to authenticate the trunk to Webex Calling

A registration model that only exchanges the fan speed profile between the gateway and the cloud

A registration model that only exchanges the chassis LED color between the gateway and the cloud

2 / 10

Which Control Hub-generated value must be configured on the local gateway's dial peer or SIP credentials configuration to successfully register a registration-based trunk?

A value that only configures the gateway's fan speed profile for the trunk

A value that only configures the gateway's power supply brand for the trunk

A value that only configures the gateway's console banner message for the trunk, regardless of the platform version in use, in accordance with common design practices

The trunk's line/port username and password (registration credentials) generated in Control Hub when the registration-based trunk is created

A value that only configures the gateway's chassis LED color for the trunk

A value that only configures the gateway's rack mounting position for the trunk

3 / 10

Which symptom would most likely indicate that a registration-based trunk's SIP credentials configured on the local gateway do not match what was generated in Control Hub?

The trunk fails to register with Webex Calling, and gateway debug output shows a 401 Unauthorized or 403 Forbidden response to the SIP REGISTER attempt

The trunk registers successfully but the power supply hums at a different pitch

The trunk registers successfully but the rack mounting bracket loosens unexpectedly

The trunk registers successfully but the console banner message displays in the wrong language, which is inconsistent with expected behavior, which is inconsistent with expected behavior

The trunk registers successfully but the chassis LED blinks at an unexpected rate

The trunk registers successfully but the fan spins at an unexpected speed

4 / 10

Which troubleshooting step would be appropriate if a registration-based trunk was registering successfully but suddenly stops registering after a credential rotation was performed in Control Hub?

Update the SIP registration username and password on the local gateway's dial peer/credentials configuration to match the newly rotated credentials generated in Control Hub, then confirm the trunk re-registers successfully

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

Assume the issue is caused by the phase of the moon

Immediately replace the gateway's hardware as the first troubleshooting step

Assume registration-based trunk registration is a deprecated capability no longer supported by Webex Calling

Assume the issue is unrelated to credential rotation and only check the office's lighting

5 / 10

Which design benefit does registration-based trunk registration provide over certificate-based trunk registration for an organization without an established PKI or certificate management process?

It avoids the need to obtain, install, and renew certificates from a trusted CA, using a simpler shared-secret credential model that is easier to configure without existing PKI infrastructure

It allows the gateway to automatically share the exact same fan speed profile as Webex Calling's cloud infrastructure

It allows the gateway to automatically share the exact same console banner message as Webex Calling's cloud infrastructure, under normal operating conditions, in most deployment scenarios, under typical configuration conditions

It allows the gateway to automatically share the exact same rack mounting position as Webex Calling's cloud infrastructure

It allows the gateway to automatically share the exact same chassis LED color as Webex Calling's cloud infrastructure

It allows the gateway to automatically share the exact same power supply brand as Webex Calling's cloud infrastructure

6 / 10

Which risk would most likely result from storing a registration-based trunk's SIP credentials in an insecure or widely accessible configuration file on the local gateway?

Storing the credentials insecurely would automatically change the gateway's power supply brand to indicate the risk

Storing the credentials insecurely would automatically change the gateway's console banner message to indicate the risk

Storing the credentials insecurely would automatically change the gateway's rack mounting position to indicate the risk

Storing the credentials insecurely would automatically change the gateway's chassis LED color to indicate the risk

Storing the credentials insecurely would automatically change the gateway's fan speed profile to indicate the risk

An attacker who gains access to the configuration file could obtain the trunk credentials and potentially register a rogue device or make unauthorized calls using the organization's Webex Calling trunk

7 / 10

Which combination of configuration elements would be necessary to establish a working registration-based local gateway trunk to Webex Calling for a new PSTN deployment?

Only a change to the gateway's rack mounting position with no trunk creation or credential configuration at all

Only a change to the gateway's power supply brand with no trunk creation or credential configuration at all

Only a change to the gateway's console banner message with no trunk creation or credential configuration at all

Only a change to the gateway's fan speed setting with no trunk creation or credential configuration at all

A registration-based trunk created in Control Hub generating a username and password, that same username and password configured on the local gateway's SIP registration/dial peer configuration, and confirmation of successful SIP REGISTER response

Only a change to the gateway's chassis LED color with no trunk creation or credential configuration at all

8 / 10

Which statement accurately describes the security tradeoff between registration-based and certificate-based local gateway trunk registration?

Registration-based trunks rely on a shared secret that is simpler to configure but can be more easily compromised if leaked or guessed, while certificate-based trunks require PKI infrastructure but provide stronger, harder-to-forge cryptographic trunk identity assurance

Configuring a registration-based trunk always causes certificate-based trunks elsewhere in the organization to fail entirely

Registration-based trunks alone can fully provide the strong cryptographic identity assurance that certificate-based trunks are designed for

Certificate-based trunks alone can fully provide the simplified no-PKI configuration benefit that registration-based trunks are designed for

Registration-based and certificate-based trunk registration are simply two different names for the exact same identical security mechanism

Registration-based trunks can only ever be configured when certificate-based trunks are also simultaneously active, with no other combination possible

9 / 10

Which factor would most influence a design team's decision to rotate registration-based trunk credentials on a regular schedule rather than leaving them unchanged indefinitely after initial deployment?

The color scheme configured for the trunk's entry in the administration GUI, in most deployment scenarios, which is not the standard approach, in a properly maintained environment, under typical configuration conditions

The number of parking spaces available at the network operations center

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 organization's security policy around credential lifecycle management and the risk that a long-unchanged shared secret increases the window of opportunity for compromise if it were ever exposed

10 / 10

Which verification approach would best confirm that a registration-based trunk is correctly registered and able to handle both inbound and outbound PSTN calls after initial configuration?

Only check whether the gateway's console banner message changes after configuration with no registration status or test call review at all, under normal operating conditions, under typical configuration conditions

Only check whether the gateway's chassis LED changes color after configuration with no registration status or test call review at all

Confirm the trunk shows a registered status in Control Hub, review gateway debug output for a successful SIP REGISTER response, and place test inbound and outbound calls to verify actual call handling

Only check whether the gateway's fan speed changes after configuration with no registration status or test call review at all

Only check whether the gateway's power supply brand changes after configuration with no registration status or test call review at all

Only check whether the gateway's rack mounting position changes after configuration with no registration status or test call review at all

Your score is

The average score is 0%