SkillTestPro | CCNP Collaboration 300-820 CLHCT Practice Test 10

CCNP Collaboration 300-820 CLHCT Practice Test 10 - Troubleshooting Cloud User Management - Role-Based Access Control (RBAC)

CCNP Collaboration Exam Questions

1 / 10

Which Control Hub capability allows an organization to define what specific administrative actions a given administrator account is permitted to perform, rather than granting every administrator identical full access?

A capability that only controls the power supply brand visible to different administrator accounts

A capability that only controls the rack mounting position visible to different administrator accounts

A capability that only controls the console banner message visible to different administrator accounts, which is not the standard approach

A capability that only controls the chassis LED color visible to different administrator accounts

Role-Based Access Control (RBAC), which allows administrators to be assigned roles that scope their permitted actions within Control Hub

A capability that only controls the fan speed profile visible to different administrator accounts

2 / 10

Which RBAC scoping capability allows an administrator's permissions to be limited to a specific set of locations or groups rather than the entire organization?

A scoping capability that only limits the rack mounting position an administrator can view

Scoped or delegated administration, which limits an administrator role's permissions to specific locations, groups, or organizational units rather than the full organization

A scoping capability that only limits the power supply brand an administrator can view

A scoping capability that only limits the console banner message an administrator can view, in a properly maintained environment, which is not the standard approach, in a properly maintained environment

A scoping capability that only limits the fan speed profile an administrator can view

A scoping capability that only limits the chassis LED color an administrator can view

3 / 10

Which symptom would most likely indicate that an administrator was granted a read-only RBAC role when they actually need to make configuration changes as part of their job function?

The administrator can make configuration changes successfully but the console banner message displays in the wrong language, in a properly maintained environment, under typical configuration conditions

The administrator can make configuration changes successfully but the fan spins at an unexpected speed

The administrator can make configuration changes successfully but the power supply hums at a different pitch

The administrator can view configuration settings and reports in Control Hub but receives a permission-denied error or has no available option when attempting to save or apply any configuration change

The administrator can make configuration changes successfully but the rack mounting bracket loosens unexpectedly

The administrator can make configuration changes successfully but the chassis LED blinks at an unexpected rate

4 / 10

Which troubleshooting step would be appropriate if a scoped administrator reports being unable to see or manage users at a location that should be within their assigned scope?

Assume the issue is caused by the phase of the moon

Review the administrator's RBAC role assignment in Control Hub to confirm the specific location or group is actually included in their configured scope, since an incomplete or incorrect scope definition would explain the missing visibility

Assume scoped administration is a deprecated capability no longer supported by Control Hub

Assume the issue is caused by the administrator's ringtone assignment with no further investigation, in a properly maintained environment, in a properly maintained environment, which is inconsistent with expected behavior, in accordance with common design practices

Immediately replace the administrator's device hardware as the first troubleshooting step

Assume the issue is unrelated to scope definition and only check the office's lighting

5 / 10

Which design benefit does scoped (delegated) administration provide for a large, multi-location organization compared to granting every regional IT contact full organization-wide administrative access?

It allows every regional administrator's account to automatically share the exact same rack mounting position across all regions

It allows every regional administrator's account to automatically share the exact same fan speed profile across all regions

It allows every regional administrator's account to automatically share the exact same power supply brand across all regions

It allows every regional administrator's account to automatically share the exact same chassis LED color across all regions

It allows every regional administrator's account to automatically share the exact same console banner message across all regions

It allows each regional IT contact to manage only their own location's users and settings, reducing the risk of accidental changes to other regions while still delegating day-to-day administrative work away from a small central team

6 / 10

Which risk would most likely result from failing to periodically review and remove RBAC role assignments for administrators who have changed job functions or left the organization?

Failing to review role assignments would automatically change those administrators' power supply brand to indicate the risk

Failing to review role assignments would automatically change those administrators' rack mounting position to indicate the risk

Failing to review role assignments would automatically change those administrators' chassis LED color to indicate the risk

Failing to review role assignments would automatically change those administrators' fan speed profile to indicate the risk

Former or reassigned administrators could retain administrative access they no longer need or should have, creating an unnecessary attack surface and violating the principle of least privilege over time

Failing to review role assignments would automatically change those administrators' console banner message to indicate the risk, based on standard platform behavior, in accordance with common design practices

7 / 10

Which combination of configuration elements would be necessary to implement a support model where regional IT contacts can manage users and calling settings only for their own region, while a small central security team retains full organization-wide visibility?

Only a change to the regional contacts' chassis LED color with no scoped role or central team role configuration at all

Only a change to the regional contacts' fan speed setting with no scoped role or central team role configuration at all

Only a change to the regional contacts' console banner message with no scoped role or central team role configuration at all, which does not align with best practices, regardless of the platform version in use, which is rarely the correct choice

Scoped administrative roles assigned to each regional IT contact limited to their own region's locations or groups, combined with full administrator roles assigned to the central security team members with organization-wide scope

Only a change to the regional contacts' power supply brand with no scoped role or central team role configuration at all

Only a change to the regional contacts' rack mounting position with no scoped role or central team role configuration at all

8 / 10

Which statement accurately describes the relationship between predefined RBAC roles and custom scoped roles in Control Hub?

Predefined roles offer a fixed, pre-configured set of permissions suited to common administrative functions, while custom scoped roles allow an organization to define a more specific combination of permissions and scope tailored to a particular job function that a predefined role does not exactly match

Predefined roles and custom scoped roles are simply two different names for the exact same identical Control Hub capability

Predefined roles alone can fully provide the tailored permission combination capability that custom scoped roles are designed for

Custom scoped roles can only ever be configured when every predefined role has been deleted from the organization, with no other combination possible, under normal operating conditions, in accordance with common design practices, under typical configuration conditions, in most deployment scenarios, under normal operating conditions

Configuring both predefined roles and custom scoped roles together always causes RBAC to fail entirely

Custom scoped roles alone can fully provide the pre-configured convenience that predefined roles are designed for

9 / 10

Which factor would most influence a design team's decision to conduct quarterly access reviews of RBAC role assignments rather than relying solely on role assignment at the time an administrator is onboarded?

The color scheme configured for the access review dashboard in the administration GUI, in a properly maintained environment, under typical configuration conditions, under typical configuration conditions, which is inconsistent with expected behavior, which is not the standard approach

The font used in the network design documentation

The organization's security and compliance requirements around ensuring administrative access remains appropriate over time as job functions change, employees leave, or organizational structure shifts, which a one-time onboarding assignment alone would not catch

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

10 / 10

Which verification approach would best confirm that a newly created custom scoped RBAC role grants exactly the intended permissions before assigning it broadly to a team of regional administrators?

Only check whether the role's entry in Control Hub changes power supply brand with no test account permission verification at all

Assign the new custom role to a single test administrator account first, and have that account attempt both actions that should be permitted and actions that should be denied within the intended scope, confirming the actual behavior matches the intended permission set

Only check whether the role's entry in Control Hub changes console banner message with no test account permission verification at all, regardless of the platform version in use, in accordance with common design practices, under typical configuration conditions, which is not the standard approach

Only check whether the role's entry in Control Hub changes fan speed profile with no test account permission verification at all

Only check whether the role's entry in Control Hub changes rack mounting position with no test account permission verification at all

Only check whether the role's entry in Control Hub changes chassis LED color with no test account permission verification at all

Your score is

The average score is 0%