Top-Level Classifications for Role Assignment in Azure RBAC

Correct Answers: A, E, F and G

RBAC is the authorization technique that is used for managing access to Azure resources.

To grant access, roles can be assigned to groups, service principals, users, or managed identities at a particular scope.

Option A is correct.

A Role can be assigned to Managed Identities.

Option B is incorrect.

Role can't be assigned to Assets.

Option C is incorrect.

Role can't be assigned to devices.

Option D is incorrect.

Role can't be assigned to Attributes.

Option E is correct.

To grant access, roles can be assigned to groups, service principals, users, or managed identities at a particular scope.

Option F is correct.

To grant access, roles can be assigned to groups, service principals, users, or managed identities at a particular scope.

Option G is correct.

A role can be assigned to Service Principals.

Option H is incorrect.

Role can't be assigned to workflows.

Option I is incorrect.

Role can't be assigned to Orchestrations.

To know more about Identity and Access Management, please visit the below-given link:

Azure role-based access control (RBAC) is an authorization technique that enables administrators to manage access to Azure resources based on the roles assigned to users, groups, and service principals. RBAC allows granular control over access to resources by defining permissions at different levels of the Azure resource hierarchy.

The top-level classifications to which you can assign roles to grant access are as follows:

A. Managed Identities: Managed identities are Azure Active Directory (Azure AD) objects that provide an identity for Azure services to authenticate against Azure AD. You can assign roles to managed identities to grant access to Azure resources.

B. Assets: Assets are the resources in Azure that are being protected by Azure RBAC. This includes virtual machines, storage accounts, web apps, and other Azure resources.

C. Devices: Devices are physical devices that are managed and enrolled in Azure AD. You can assign roles to devices to grant access to Azure resources.

D. Attributes: Attributes are the properties of a resource that can be used to control access to the resource. For example, you can use resource tags to assign roles to resources.

E. Users: Users are individuals who have been granted access to Azure resources. You can assign roles to users to grant access to Azure resources.

F. Groups: Groups are collections of users that can be used to manage access to Azure resources. You can assign roles to groups to grant access to Azure resources.

G. Service Principals: Service principals are security principals that are used to represent applications, services, or other entities that need to authenticate and access Azure resources. You can assign roles to service principals to grant access to Azure resources.

H. Workflows: Workflows are automated processes that are used to manage and orchestrate tasks in Azure. You can assign roles to workflows to grant access to Azure resources.

I. Orchestrations: Orchestrations are the processes used to automate and manage complex workflows in Azure. You can assign roles to orchestrations to grant access to Azure resources.

In summary, RBAC in Azure allows you to assign roles to different types of objects such as managed identities, assets, devices, attributes, users, groups, service principals, workflows, and orchestrations to grant access to Azure resources. This provides granular control over access to resources and enables administrators to manage access to Azure resources more efficiently.