Microsoft Certified Power Platform Functional Consultant Associate · Free Practice Question Medium
Question 40
Scenario: Queen Consolidated was overtaken by Raymond Carson Palmer and rebranded as Palmer Technologies. Now that Ray is overseeing the operations at Palmer, Ray has decided to implement better applications.
You are working as a consultant with Palmer and in a meeting with Ray and his IT team discussing Microsoft Power Apps. Because Palmer is a large organization, Ray wants each department employee to see only apps and company data that are appropriate to their needs.
Which is the proper way to ensure this happens?
-
A
Create a separate environment for each department.
-
B
Use RBAC to provide the appropriate access to users.
-
C
Use AD to provide the appropriate access to users.
-
D
Create regional segregations based on IP addresses to indicate which departments have access to the data.
Reveal correct answer
Correct answer: A
Explanation
Understand environments in Power Apps
An environment is a container for apps and other resources, such as data connections and flows from Power Automate. It's a way to group items based on business requirements.
In the upper-right corner of the home page, you can view your current environment.
If a drop-down menu is visible next to the environment name, this indicates that other environments are available.
Reasons to use environments
Reasons to create environments beyond the default one include:
Separate app development by department - In a large organization, each department can work in a different environment. That way, department employees see only apps and company data that are appropriate to their needs.
Support application lifecycle management (ALM) - Separate environments let you separate apps that are in development stages from those that have already been shared. Alternatively, you might want to use a trial environment so that you can receive feedback from employees before publishing the final app. For some organizations, showing apps before they're completely developed and published can present security concerns.
Manage data access - Each environment can have its own source of business data, called a database for Microsoft Dataverse. Other data connections are specific to an environment and can't be shared across environments.
Note: Keep in mind that environments are relevant only to app creators and Power Apps admins. When you share an app with users, those users simply run the app, providing they have the correct permissions. In other words, they don't have to worry about what environment the app came from.
Create an environment
Only an admin can create environments. If you aren't an admin, this information can still be helpful when you talk to your admin about setting up environments.
On the make.powerapps.com home page, select the gear icon near the upper-right corner and then select Admin Centre.
You can also go directly to https://admin.powerplatform.microsoft.com/
In the Power Platform Admin Centre, select + New.
In the New environment dialog box, enter a name for the environment and then select a region and an environment type.
To the left of Create a database for this environment, select the toggle to Yes.
Select Next.
Select the currency and language for the data that is stored in the database. You cannot change the currency or language after the database is created.
Select Save.
It might take several minutes to create the database on Dataverse. After the database is created, the new environment appears in the list of environments on the Environments page.
You now have a new environment to work in. If you go back to make.powerapps.com, you will see it in the environments list.
Manage access to an environment
By default, you can access an environment in one of two ways:
System admin - A system admin has full permissions to create and manage environments.
Environment maker - An environment maker can view all apps in that environment, create apps, and work with Dataverse (other permissions apply).
Environment admins can create other security roles as needed. They can also add and assign users to these roles.
Start by going to https://admin.powerplatform.microsoft.com
On the left pane, Environments should be selected by default, if it is not, select Environments.
Select the test environment that you just created, and then select Settings at the top.
Select the Users + permissions dropdown and select Users.
Select Add user at the top and add the user by entering the email address of the user in your organization and then selecting Add. Wait a few minutes for the user to be added.
To manage the roles and information of a user, select the user’s Name. This will open a new tab with the Dynamics 365 view of that user.
Select Manage Roles on the top bar.
In the Manage User Roles box, select the role(s) for the user. In this example, assign the user to the Environment Maker role.
Select OK.
The changes are then saved, so you can close the Dynamics 365 tab in your browser when done.
A. Creating a separate environment for each department is the proper way to ensure that each department employee only sees apps and company data that are appropriate to their needs. By segregating the environments, you can control access and visibility based on department-specific requirements.
B. Using Role-Based Access Control (RBAC) to provide the appropriate access to users is a valid approach, but it may not be as effective in ensuring that each department employee sees only relevant apps and data. RBAC focuses on defining roles and permissions within the same environment, rather than segregating environments for different departments.
C. Using Active Directory (AD) to provide the appropriate access to users is a valid method for managing user authentication and access control, but it may not be sufficient to ensure that each department employee sees only relevant apps and data. AD primarily deals with user authentication and identity management, rather than environment segregation.
D. Creating regional segregations based on IP addresses to indicate which departments have access to the data is not the proper way to ensure that each department employee sees only relevant apps and data. IP-based restrictions may not be granular enough to control access at the level of individual departments, and they may not provide the necessary flexibility for managing access based on department-specific requirements.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
