DRAG DROP
A company uses System Center 2012 R2 Virtual Machine Manager (VMM) to manage their Hyper-V
environment. The VMM environment has two host groups named Dev and Prod.
The Hyper-V environment has the following requirements:
Administrators of the Prod host group must be able to manage virtual machines (VMs) and perform all VMM
administrative tasks only within the Prod host group. Administrators of the Dev host group must be able to
manage VMs and perform all VMM administrative tasksonly within the Dev host group. Administrators of the
Dev host group must be able to provision new Hyper-V host servers from physical computers for the Dev host
group. The security administrators must be able to add user objects to the Administrator role in VMM.
All delegation must adhere to the principle of least privilege.
You need to configure the user role profiles for each host group.
Which user role profiles should you assign? To answer, drag the appropriate user role profile to the correct user
group. Each user role profile may be used once, more than once, or not at all. You may need to drag the split
bar between panes or scroll to view content.
Answer:
Explanation:
Is this really correct?
Seems correct to me.
http://technet.microsoft.com/en-us/library/gg696971.aspx
Wont Tenant Admin suffice for Prod?
I believe so, “giggidy”. I believe that the correct answer is:
Prod administrators = Tenant Administrator
Dev administrators = Fabric Administrator
Security administrators = Administrator
Fabric admins can perform “Administrative tasks” (whatever that may be) and Tenant Admins can not. This is needed by the Prod Admins.
See https://technet.microsoft.com/en-us/library/gg696971.aspx
So original answer looks okay to me.
It would seem that Prod Admins would be able work as Tenant administrators since they don’t need to deploy hyper-V hosts.
Tenant Administrator
As of VMM in System Center 2012 Service Pack 1 (SP1), you can create Tenant Administrator user roles.
Members of the Tenant Administrator user role can manage self-service users and VM networks. Tenant administrators can create, deploy, and manage their own virtual machines and services by using the VMM console or a web portal. Tenant administrators can also specify which tasks the self-service users can perform on their virtual machines and services. Tenant administrators can place quotas on computing resources and virtual machines.
Its not Tenant Administrator.
The question refers to Host Groups.
You cannot assign Tenant Administrator to a scope of Host Groups, only private clouds.
It has to be:
Fabric Administrator
Fabric Administrator
Administrator