1Y0-371 · Question #143
A Citrix Engineer must provide a group of non-administrator help-desk personnel with access to a set of features in the XenMobile Console. What should the engineer do to accomplish this task?
The correct answer is D. Configure Role-based Access Control (RBAC) and assign only the desired permissions to the. See the full explanation below for the reasoning.
Question
A Citrix Engineer must provide a group of non-administrator help-desk personnel with access to a set of features in the XenMobile Console. What should the engineer do to accomplish this task?
Options
- AConfigure AAA groups on the NetScaler Gateway. Allow only these groups to access the console
- BCreate a local group on the XenMobile Server. Allow only access for help-desk personnel.
- CConfigure a Delivery Group within the XenMobile Server and deploy the security policies only to
- DConfigure Role-based Access Control (RBAC) and assign only the desired permissions to the
How the community answered
(22 responses)- A5% (1)
- B18% (4)
- C5% (1)
- D73% (16)
Community Discussion
5The correct answer is D. XenMobile has a built-in RBAC system specifically designed for this scenario, where you create a role, check off the console features that role is allowed to use, and then assign that role to the help-desk users or their group. That granularity is the whole point, because you can hand someone access to device wipe or enrollment without giving them keys to the entire server configuration. The other options either control network-level authentication rather than console permissions, like A does with NetScaler Gateway AAA groups, or they deal with device and app delivery rather than console access, which is what C is doing with Delivery Groups. Option B gets you partway there by creating a local group, but a group alone does not scope what features those users can see or touch inside the console, so pairing group membership with RBAC role assignment is the complete solution.
Saw this exact scenario on my exam last month and I almost went with B because I was thinking about it like a Windows server thing, but then I remembered that RBAC in XenMobile is specifically built for delegating console access to help-desk roles without giving them full admin rights, so D is the one. Creating a local group on the XenMobile Server does not actually control what those users can do inside the console, which is the whole point of the question.
Luis nailed the core of it, though worth adding that the delegation in RBAC is scoped per role, so if your help-desk group ends up with more console permissions than intended, the role assignment is where you go to tighten it, not the local group.
RBAC is the only mechanism that scopes console permissions by role, not by network group (A) or enrollment group (C), so D.
Solid call, and worth flagging for test day: if the question stem uses the phrase "by role" or "role assignment," treat that as your direct pointer to RBAC and skip re-reading the group-based options because the wording alone rules them out.