Assignable Security Roles

Correct Answers: B and D

When you create a Dataverse environment without a database, you have only two security role choices: Environment Maker and Environment Admin.

Environment Maker can create new resources, like apps, flows, connections, gateways; share the apps with the users in an organization.

But this role does not have privileges to access the environment's data.

Environment Admin can perform all administrative tasks in the environment, like add and remove users from Environment Maker or Admin roles; provision Dataverse database, and view and manage the environment's resources.

Option A is incorrect because System Customizer is a Dataverse security role for the environments with the Dataverse database.

Option C is incorrect because System Administrator is a Dataverse security role for the environments with the Dataverse database.

Option E is incorrect because Basic user (previously Common Data Service User) is a Dataverse security role for the environments with the Dataverse database.

For more information about Dataverse security roles, please visit the below URL:

The statement in the question "You create a Dataverse environment without a database" is a bit confusing since the Dataverse (formerly known as Common Data Service) is essentially a database that allows you to store and manage data used by Power Apps, Power Automate, and Power BI. However, it's possible to create an environment in Dataverse without any tables or data, which might be what the question is referring to.

With that in mind, let's review the security roles that can be assigned to users in Dataverse environments:

A. System Customizer: This role allows a user to customize the system and entities within it, including creating, modifying, and deleting fields, forms, views, and dashboards. This role is typically assigned to business analysts or power users who are responsible for configuring and customizing the Dataverse environment to meet the needs of the organization.

B. Environment Maker: This role allows a user to create and manage environments in Dataverse. They can create new environments, manage environment settings, and manage environment security roles. This role is typically assigned to IT administrators or technical users who are responsible for managing the overall Dataverse environment.

C. System Administrator: This role has full access to all aspects of the Dataverse environment, including managing security roles, configuring system settings, and managing solutions. This role is typically assigned to IT administrators who are responsible for managing the overall IT infrastructure, including the Dataverse environment.

D. Environment Admin: This role allows a user to manage the security and settings for a specific environment in Dataverse. They can manage security roles, create and manage users and teams, and manage the data policies for the environment. This role is typically assigned to business analysts or power users who are responsible for managing a specific project or application within the Dataverse environment.

E. Basic User: This role allows a user to read and edit records in Dataverse, but they cannot customize the system or manage security roles. This role is typically assigned to end-users who need to access and interact with data within the Dataverse environment.

So, based on the options given in the question, the security roles that can be assigned to users in a Dataverse environment without a database are:

• System Customizer
• Environment Maker
• System Administrator
• Environment Admin

The Basic User role is not applicable in this scenario since there is no data to access or interact with.