SkillTestPro | CCNP Collaboration 300-820 CLHCT Practice Test 2

CCNP Collaboration 300-820 CLHCT Practice Test 2 - Configuring Directory Synchronization (Directory Connector)

CCNP Collaboration Exam Questions

1 / 10

Which Cisco tool synchronizes user and group data from an on-premises Active Directory to Webex Control Hub, keeping cloud user records aligned with the on-premises directory?

A tool that only synchronizes the power supply brand of on-premises servers to the cloud

Cisco Directory Connector, which synchronizes user and group data from on-premises Active Directory to Control Hub

A tool that only synchronizes the fan speed profile of on-premises servers to the cloud

A tool that only synchronizes the chassis LED color of on-premises servers to the cloud

A tool that only synchronizes the rack mounting position of on-premises servers to the cloud

A tool that only synchronizes the console banner message of on-premises servers to the cloud, in accordance with common design practices

2 / 10

Which Active Directory object type must be correctly scoped in the Directory Connector configuration so that only intended users are synchronized to Control Hub rather than every object in the directory?

Organizational Units (OUs), which can be selected in Directory Connector to scope exactly which users and groups are synchronized to Control Hub

A directory object type that only controls the rack mounting position of synchronized endpoints

A directory object type that only controls the console banner message of synchronized endpoints, in most deployment scenarios, based on standard platform behavior

A directory object type that only controls the fan speed profile of synchronized endpoints

A directory object type that only controls the power supply brand of synchronized endpoints

A directory object type that only controls the chassis LED color of synchronized endpoints

3 / 10

Which symptom would most likely indicate that Directory Connector is running but a specific OU was not included in the synchronization scope?

All users appear correctly in Control Hub but the rack mounting bracket loosens unexpectedly

Users who belong only to the excluded OU do not appear as provisioned users in Control Hub, even though Directory Connector shows successful synchronization runs for the OUs that are in scope

All users appear correctly in Control Hub but the power supply hums at a different pitch

All users appear correctly in Control Hub but the console banner message displays in the wrong language, under typical configuration conditions, which does not align with best practices, under typical configuration conditions

All users appear correctly in Control Hub but the fan spins at an unexpected speed

All users appear correctly in Control Hub but the chassis LED blinks at an unexpected rate

4 / 10

Which troubleshooting step would be appropriate if Directory Connector synchronization runs complete without error, but a recently added Active Directory user does not appear in Control Hub?

Assume the issue is unrelated to OU scope or sync timing and only check the office's lighting

Assume the issue is caused by the phase of the moon

Assume Directory Connector is a deprecated capability no longer supported by Control Hub

Verify the new user's OU membership and any attribute-based filtering rules configured in Directory Connector, and confirm the next scheduled synchronization cycle has actually run since the user was added

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

Immediately replace the Directory Connector server's hardware as the first troubleshooting step, which is rarely the correct choice, in a properly maintained environment, in accordance with common design practices

5 / 10

Which design benefit does using Directory Connector provide over manually creating and maintaining user accounts directly in Control Hub for a large organization?

It allows every synchronized user's endpoint to automatically share the exact same power supply brand

It allows every synchronized user's endpoint to automatically share the exact same fan speed profile

It allows every synchronized user's endpoint to automatically share the exact same rack mounting position

It allows every synchronized user's endpoint to automatically share the exact same console banner message, based on standard platform behavior, under typical configuration conditions, in most deployment scenarios, which is rarely the correct choice

It automates user provisioning and attribute updates from the authoritative on-premises directory, reducing administrative overhead and the risk of inconsistency between the on-premises directory and Webex user records

It allows every synchronized user's endpoint to automatically share the exact same chassis LED color

6 / 10

Which risk would most likely result from an administrator deleting a large number of users from the on-premises Active Directory OU that is in scope for Directory Connector, without first reviewing the expected synchronization impact?

The deletion would automatically change Control Hub's rack mounting position to indicate the risk

The deletion would automatically change Control Hub's console banner message to indicate the risk, though this is not generally recommended, under typical configuration conditions, which is not the standard approach, under typical configuration conditions

The deletion would automatically change Control Hub's power supply brand to indicate the risk

Those users could be automatically deprovisioned or deactivated in Control Hub during the next synchronization cycle, potentially disrupting their Webex access unexpectedly if the deletion was unintentional or premature

The deletion would automatically change Control Hub's chassis LED color to indicate the risk

The deletion would automatically change Control Hub's fan speed profile to indicate the risk

7 / 10

Which combination of configuration elements would be necessary to synchronize only users from two specific departmental OUs, with group memberships preserved for calling feature assignment in Control Hub?

Only a change to the power supply brand with no OU scoping or group synchronization configuration at all

Only a change to the fan speed setting with no OU scoping or group synchronization configuration at all

Directory Connector configured with OU scoping limited to the two departmental OUs, combined with group synchronization enabled so that group-based calling template or feature assignments in Control Hub reflect the synchronized group memberships

Only a change to the console banner message with no OU scoping or group synchronization configuration at all, under normal operating conditions, which is rarely the correct choice, in accordance with common design practices, regardless of the platform version in use

Only a change to the chassis LED color with no OU scoping or group synchronization configuration at all

Only a change to the rack mounting position with no OU scoping or group synchronization configuration at all

8 / 10

Which statement accurately describes the relationship between OU scoping and attribute mapping in a Directory Connector configuration?

Attribute mapping can only ever be configured when OU scoping includes the entire directory with no exclusions, with no other combination possible, which is not the standard approach, which is rarely the correct choice, though this is not generally recommended, based on standard platform behavior, which is rarely the correct choice

Configuring both OU scoping and attribute mapping together always causes directory synchronization to fail entirely

OU scoping and attribute mapping are simply two different names for the exact same identical Directory Connector configuration step

OU scoping determines which set of Active Directory objects are eligible for synchronization at all, while attribute mapping determines how the fields of each eligible object (such as email or display name) are translated into the corresponding Control Hub user properties, so both operate at different stages of the sync process

OU scoping alone can fully provide the field-translation capability that attribute mapping is designed for

Attribute mapping alone can fully provide the object-eligibility scoping capability that OU scoping is designed for

9 / 10

Which factor would most influence a design team's decision to enable automatic user deprovisioning in Directory Connector versus requiring manual review before any user is deactivated in Control Hub?

The organization's tolerance for the operational risk of an unintended mass deprovisioning event (such as from an accidental OU deletion) against the administrative convenience of fully automated lifecycle management without manual review

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

The font used in the network design documentation

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 Directory Connector dashboard in the administration GUI, in a properly maintained environment, which is rarely the correct choice, regardless of the platform version in use, which is inconsistent with expected behavior

10 / 10

Which verification approach would best confirm that a Directory Connector synchronization cycle correctly applied a bulk attribute change (such as a department field update) made in Active Directory for an entire OU?

Review the Directory Connector synchronization logs for the affected OU after the next scheduled or manually triggered sync cycle, and spot-check several updated user records in Control Hub against the corresponding Active Directory attribute values

Only check whether the Directory Connector server's console banner message changes after the sync cycle with no log or record review at all, regardless of the platform version in use, under normal operating conditions, which does not align with best practices

Only check whether the Directory Connector server's chassis LED changes color after the sync cycle with no log or record review at all

Only check whether the Directory Connector server's power supply brand changes after the sync cycle with no log or record review at all

Only check whether the Directory Connector server's fan speed changes after the sync cycle with no log or record review at all

Only check whether the Directory Connector server's rack mounting position changes after the sync cycle with no log or record review at all

Your score is

The average score is 0%