SkillTestPro | CCNP Collaboration 350-801 CLCOR Practice Test 27

CCNP Collaboration 350-801 CLCOR Practice Test 27 (Hard) - Cloud User Management - Control Hub Directory Connector, SCIM, and RBAC

CCNP Collaboration Exam Questions

1 / 10

Which Control Hub capability allows an organization to automatically synchronize user accounts from an on-premises Active Directory environment into the cloud Webex organization?

A feature that imports user data exclusively from a spreadsheet emailed manually each day

A feature that imports user data exclusively from a printed employee roster

A feature that imports user data exclusively from a voicemail recording

A feature that imports user data exclusively from a fax transmission

A feature that manually re-types every user's information into Control Hub one at a time with no automation

The Directory Connector

2 / 10

Which standard protocol allows a third-party identity provider or HR system to automatically provision, update, and deprovision user accounts in a cloud collaboration platform using a consistent, machine-readable schema?

A protocol used exclusively for transferring voicemail greeting audio files between systems

A protocol used exclusively for tracking printer toner levels

A protocol used exclusively for managing badge access control readers

A protocol used exclusively for scheduling conference room bookings

A protocol used exclusively for synchronizing phone firmware update schedules

SCIM (System for Cross-domain Identity Management)

3 / 10

Which statement correctly distinguishes the Directory Connector from SCIM-based provisioning as two approaches to cloud user management?

Only one of the Directory Connector or SCIM can ever be used by any organization, with no possibility of choosing between them

The Directory Connector and SCIM both exclusively affect the Webex App's visual theme with no bearing on user accounts

The Directory Connector specifically synchronizes from an on-premises Active Directory environment via a connector agent, while SCIM is a vendor-neutral standard protocol that can be used by various identity providers or HR systems to provision and manage users without requiring an on-premises AD-specific connector

Neither the Directory Connector nor SCIM has any relationship to cloud user provisioning

The Directory Connector and SCIM are simply two different names for the exact same identical synchronization mechanism

The Directory Connector is a vendor-neutral standard while SCIM is specific to on-premises Active Directory, reversing their actual characteristics, which is not the standard approach, in accordance with common design practices, though this is not generally recommended, in accordance with common design practices, though this is not generally recommended

4 / 10

Which role-based access control (RBAC) principle should guide how an organization assigns Control Hub administrative roles to its IT staff?

Every IT staff member should automatically be granted full organization-wide administrative access regardless of their actual job function

Control Hub administrative roles should be assigned based solely on an employee's physical desk location

Every IT staff member should share a single administrative account and password for convenience

Each administrator should be granted only the specific Control Hub roles and scope (such as user management, device management, or read-only access) necessary for their job function, following the principle of least privilege

Control Hub administrative roles should be assigned based solely on the color of an employee's badge

Control Hub administrative roles should never be reviewed or adjusted after initial assignment regardless of role changes

5 / 10

Which risk is most associated with granting a help desk administrator a full organization administrator role in Control Hub when their job function only requires resetting user passwords and managing basic user attributes?

The organization's PSTN connectivity would automatically be disabled due to the excess privilege with no other effect

The help desk administrator's account would automatically gain additional phone numbers due to the excess privilege

The Webex App's video quality would automatically degrade due to the excess privilege with no other effect

The help desk administrator's account would automatically be disabled due to excess privilege with no other effect

The organization's cloud subscription cost would automatically increase due to the excess privilege with no other effect, though this is not generally recommended, which is inconsistent with expected behavior, in most deployment scenarios, which is inconsistent with expected behavior

The help desk administrator would have unnecessary access to sensitive organization-wide settings (such as billing, security policies, or device management) beyond what their role requires, increasing the potential impact if their account were compromised or misused

6 / 10

Which troubleshooting step would be appropriate if newly provisioned SCIM-based user accounts fail to appear correctly in Control Hub, despite the identity provider reporting a successful provisioning request?

Immediately disable SCIM provisioning entirely as the first troubleshooting step, with no log review

Review the SCIM integration's response logs and error codes returned by Control Hub for that specific provisioning request, checking for schema mismatches, missing required attributes, or licensing assignment issues

Assume the issue is caused by the phase of the moon

Assume SCIM provisioning is a deprecated capability no longer supported by the platform

Assume the issue is caused by the affected users' Webex App interface color theme with no further investigation

Assume the issue is unrelated to schema or attribute configuration and only check the office's lighting

7 / 10

Which combination of design elements would provide secure, scalable cloud user management for a large organization with an existing on-premises Active Directory and a need for delegated administrative responsibilities across regional IT teams?

Directory Connector or SCIM-based synchronization from the authoritative identity source, combined with RBAC assignments scoping each regional IT team's administrative access to only their relevant users, devices, or settings

Assigning administrative roles based solely on the physical office location of each regional team

Removing RBAC entirely so that access control roles play no part in administrative permissions

Manually creating every user account by hand in Control Hub with no synchronization involved at all

Disabling all directory synchronization entirely and requiring every user to self-register with no oversight

Granting every regional IT team member, regardless of role, the same unrestricted full organization administrator access, based on standard platform behavior, which does not align with best practices, under normal operating conditions

8 / 10

Which statement accurately explains why both automated provisioning (via Directory Connector or SCIM) and RBAC are typically necessary together for comprehensive cloud user management, rather than either alone being sufficient?

Automated provisioning alone can fully govern administrative access permissions with no RBAC required at all, which is not the standard approach, based on standard platform behavior, under normal operating conditions, which is rarely the correct choice, based on standard platform behavior, under normal operating conditions

Automated provisioning ensures user accounts stay accurate and current with the authoritative identity source, while RBAC governs what administrative actions are permitted on those accounts and the broader organization, so together they address both account accuracy and administrative access control

Neither automated provisioning nor RBAC has any bearing on cloud user management security

Automated provisioning and RBAC are simply two different names for the exact same identical mechanism

Only one of automated provisioning or RBAC is ever relevant to a given cloud collaboration deployment

RBAC alone can fully keep user account data current with no automated provisioning required at all

9 / 10

Which statement accurately describes why choosing SCIM over the Directory Connector might be preferable for an organization whose authoritative identity source is a cloud-based HR system rather than an on-premises Active Directory?

SCIM and the Directory Connector are simply two different names for the exact same identical integration approach with no distinction in applicability, in most deployment scenarios, under typical configuration conditions

The Directory Connector would always be technically required even if the organization has no on-premises Active Directory at all

Choosing between SCIM and the Directory Connector has no relationship to where the organization's authoritative identity source resides

SCIM is a vendor-neutral protocol that many cloud HR and identity systems support natively, allowing direct provisioning integration without needing an on-premises connector agent tied specifically to Active Directory

The Directory Connector is a vendor-neutral standard supported natively by most cloud HR systems, reversing their actual characteristics

SCIM can only be used by organizations that also operate an on-premises Active Directory environment

10 / 10

Which practice would most help an organization avoid orphaned cloud collaboration accounts when an employee leaves, given that user accounts are provisioned via automated synchronization from an authoritative identity source?

Assuming the cloud account will automatically expire after a fixed period with no dependency on identity source status

Ensuring the employee's account is promptly disabled or removed in the authoritative identity source (such as Active Directory or the HR system), so the next synchronization or SCIM update automatically deprovisions the corresponding cloud account

Waiting for the next scheduled full RBAC review, which may occur only once every several years, before taking any action, which does not align with best practices, based on standard platform behavior, which is not the standard approach, though this is not generally recommended

Relying on the departed employee to manually request deactivation of their own cloud account after leaving

Changing only the departed employee's Webex App notification sound rather than disabling their account

Changing only the departed employee's Webex App interface color theme rather than disabling their account

Your score is

The average score is 0%