You need to ensure that only three users named Admin1, Admin2, and Admin3 can access the service offering

Your company has a datacenter in Los Angeles.
The datacenter contains a private cloud that is managed by using a System Center 2012
infrastructure.
The infrastructure has the System Center 2012 Service Manager Self-Service Portal installed.
You create a new service offering.
You need to ensure that only three users named Admin1, Admin2, and Admin3 can access the
service offering.
What should you do?

A.
Add the service offering and the request offering to a Service Manager group, and then create a
Run As Account.

B.
Add the Admin1, Admin2, and Admin3 configuration items to a Service Manager group, and then
create a Run As Account.

C.
Add the service offering and the request offering to a Service Manager group, and then create a
User Role.

D.
Add the Admin1, Admin2, and Admin3 configuration items to a Service Manager group, and then
create a User Role.

Explanation:

With Role based security scoping in SCSM there is the possibility to configure a controlled
environment for different service roles.
A SCSM role profile is a configuration set to define access to objects, views in the console, operations
they can perform and members of the role (AD User/Group).
SCSM components of a User role are:
The security scope: Is the security boundary in SCSM.
Boundaries can be set on Group/queue, Class, Property & relationships.
UI filter scope: This filter is for defining what an operator can see in the SCSM console.
Limiting the options visible in the console improves the usability.
UI filters can be set on console tasks, templates and views.
User role profile: SCSM includes some predefined user profiles who include a set of allowed
operations with a class/property/relationship scope over objects.
User Assignment: The members of the user role in SCSM.
This can be set for users or groups.
(Always recommended to use groups)
http://scug.be/scsm/2010/03/21/service-manager-role-based-security-scoping