SkillTestPro | CCNP Collaboration 300-820 CLHCT Practice Test 4

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

CCNP Collaboration Exam Questions

1 / 10

Which Webex Calling local gateway registration model uses a mutually trusted TLS certificate exchange between the local gateway and Webex Calling, rather than a shared secret or username/password, to establish trunk trust?

Certificate-based trunk registration, which uses mutual TLS certificate exchange between the local gateway and Webex Calling to establish trust

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

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

A registration model that only exchanges the console banner message between the gateway and the cloud, regardless of the platform version in use

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

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

2 / 10

Which certificate authority requirement must typically be satisfied for a local gateway's certificate to be trusted by Webex Calling in a certificate-based trunk deployment?

A requirement that only concerns the gateway's console banner message matching a specific value, which does not align with best practices, in a properly maintained environment

A requirement that only concerns the gateway's power supply brand matching a specific value

A requirement that only concerns the gateway's rack mounting position matching a specific value

A requirement that only concerns the gateway's chassis LED color matching a specific value

A requirement that only concerns the gateway's fan speed profile matching a specific value

The local gateway's certificate must be issued by a certificate authority that is trusted by Webex Calling, such as a public CA included in the Webex trusted CA list

3 / 10

Which symptom would most likely indicate that a local gateway's certificate has expired in a certificate-based trunk deployment to Webex Calling?

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

The trunk registers successfully but the rack mounting bracket loosens unexpectedly

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

The trunk fails to register or calls fail to establish, with gateway logs showing a TLS handshake failure or certificate validation error when connecting to Webex Calling

The trunk registers successfully but the console banner message displays in the wrong language, which does not align with best practices, in a properly maintained environment

4 / 10

Which troubleshooting step would be appropriate if a newly deployed certificate-based local gateway trunk fails to register with Webex Calling, with logs showing a certificate trust error?

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

Assume the issue is caused by the phase of the moon

Assume the issue is unrelated to certificate trust or chain configuration and only check the office's lighting

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

Verify that the gateway's certificate was issued by a CA trusted by Webex Calling, that the full certificate chain (including intermediate certificates) is correctly installed on the gateway, and that the certificate's subject/SAN matches the expected trunk identity

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

5 / 10

Which design benefit does certificate-based trunk registration provide over registration-based (shared secret) trunk registration for a security-conscious organization?

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 rack mounting position as Webex Calling's cloud infrastructure

It provides mutual TLS authentication based on cryptographic certificates rather than a shared secret that could be more easily leaked or guessed, offering stronger trunk identity assurance

It allows the gateway to automatically share the exact same console banner message as Webex Calling's cloud infrastructure, which is inconsistent with expected behavior, in most deployment scenarios

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 failing to renew a local gateway's certificate before its expiration date in a certificate-based trunk deployment supporting production PSTN calling?

The certificate expiration would automatically change the gateway's chassis LED color to indicate the risk

The certificate expiration would automatically change the gateway's rack mounting position to indicate the risk

The certificate expiration would automatically change the gateway's power supply brand to indicate the risk

The trunk to Webex Calling could go down at the expiration date, causing an outage of inbound and outbound PSTN calling through that gateway until a renewed certificate is installed

The certificate expiration would automatically change the gateway's console banner message to indicate the risk, under typical configuration conditions, which is rarely the correct choice

The certificate expiration would automatically change the gateway's fan speed profile to indicate the risk

7 / 10

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

Only a change to the gateway's rack mounting position with no certificate installation or Control Hub trunk configuration at all

A certificate issued by a CA trusted by Webex Calling installed on the gateway with the correct subject/SAN, the full certificate chain configured, and the corresponding trunk configuration in Control Hub referencing the certificate-based trunk type

Only a change to the gateway's fan speed setting with no certificate installation or Control Hub trunk configuration at all

Only a change to the gateway's console banner message with no certificate installation or Control Hub trunk configuration at all

Only a change to the gateway's power supply brand with no certificate installation or Control Hub trunk configuration at all

Only a change to the gateway's chassis LED color with no certificate installation or Control Hub trunk configuration at all

8 / 10

Which statement accurately describes why certificate expiration monitoring is particularly important for certificate-based local gateway trunks compared to registration-based (shared secret) trunks?

Certificate-based trunks depend on a certificate with a defined validity period that will cause trunk failure at expiration if not renewed in advance, whereas a shared secret used in registration-based trunks typically does not have the same kind of built-in expiration requiring proactive renewal

Certificate expiration monitoring and shared secret management are simply two different names for the exact same identical trunk security requirement

Certificate-based trunks can only ever be configured when registration-based trunks are also simultaneously active, with no other combination possible, which is rarely the correct choice, in accordance with common design practices, under typical configuration conditions, though this is not generally recommended

Shared secret management alone can fully provide the certificate expiration monitoring capability that certificate-based trunks require

Certificate-based trunks alone, once configured, never require any further administrative attention for the life of the deployment

Configuring certificate expiration monitoring always causes registration-based trunks to fail entirely

9 / 10

Which factor would most influence a design team's decision to use certificate-based trunk registration rather than registration-based trunk registration for a new local gateway deployment?

The organization's security policy requirements around mutual authentication strength and PKI infrastructure availability, weighed against the relative simplicity of shared-secret-based registration for a deployment with less stringent security requirements

The brand of coffee served in the network operations center

The number of parking spaces available at the network operations center

The color scheme configured for the trunk's entry in the administration GUI, under normal operating conditions, in most deployment scenarios, based on standard platform behavior, based on standard platform behavior, though this is not generally recommended, which is inconsistent with expected behavior

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

The font used in the network design documentation

10 / 10

Which verification approach would best confirm that a local gateway's renewed certificate was correctly installed and is being used for trunk authentication before the old certificate's expiration date arrives?

Only check whether the gateway's rack mounting position changes after the certificate renewal with no certificate detail or test call review at all

Only check whether the gateway's power supply brand changes after the certificate renewal with no certificate detail or test call review at all

Check the certificate details currently loaded on the gateway (issuer, validity dates, subject/SAN) against the renewed certificate, and confirm the trunk remains registered and successfully passes test calls using the new certificate before the old one expires

Only check whether the gateway's fan speed changes after the certificate renewal with no certificate detail or test call review at all

Only check whether the gateway's console banner message changes after the certificate renewal with no certificate detail or test call review at all, which is inconsistent with expected behavior, under typical configuration conditions, which is rarely the correct choice

Only check whether the gateway's chassis LED changes color after the certificate renewal with no certificate detail or test call review at all

Your score is

The average score is 0%