Pass Your Microsoft Power Platform PL-200 Exam Easy!

Microsoft PL-200 Microsoft Power Platform Functional Consultant exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Microsoft PL-200 Microsoft Power Platform Functional Consultant exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Microsoft Power Platform PL-200 certification exam dumps & Microsoft Power Platform PL-200 practice test questions in vce format.

Dataverse

20. Admin Center

We'll talk about the database admin centre in this lecture. So let us go to the application first from Power Apps. If you click on Settings and AdminCenter, it will take you to Admin. Admin center. The home screen of the Admin Center will show you all the environments that you have created, and you can create a new environment from here also. So this is our environment, on which we are working on.Then you can go to the Analytics tab, and it will show you all the analytics. It displays three active users, 2017 API calls, a 100% pass rate, and time-based operations. You can also change the filter to have it print date and time settings, and the numbers will update accordingly. So I've increased the time, the numbers have increased, and correspondingly the graph has increased. If you go to Resource Capacity tab,it will show you the capacity. So, for the database, ten of the twelve GB are being used, file 67% is available, and so on. If you go to Data Integration, this screen lets you integrate data into a database from other external sources, like SQL Server or any other database. So this is the screen, and you can set a new connection here. And if you click on "Data Policies" here, you can set data policies in which you can control how data flows in and out of the database. So these are the screens. Let us look at theory now. So this is a database overview. Till now we have been working on database creation—creating tables, columns, businesses, and things like that. So Security is used as your advertisement. It also uses multifactor authentication, and it supports authorization at the role level or field level logic.We can use rules related to duplicate detection, business rules, or workflows. We have already looked at business rules. We looked at duplicate detection in algebra lecture data and discovered models, validated them, and reported on the data storage. It stores the physical data on the Azure Cloud, and we can extend the storage up to four terabytes. And we have integration like we looked at data integration, just a nonlinear center, and we have APIs, Webbooks, Eventing, and Data Exports to give you flexibility to get data in and out. So we looked at the environments here, and environments are bound to a geographic collection like the United States. So let's go back, and if I go to Environment and create a new environment, I can tell which region this environment will be created in. So these are the available options for me. So each environment is created under Microsoft as your Active Directory tenant. And this is the URL, and this is the same URL it goes to when we click on Admin Center. So this is again a screenshot of what we clicked on—Admit Centers, Settings, Admin Center—and it lists all the instances of the database. Then we looked at data integration apps. This section lets you create or add predefined connections or monitor these connections between data warehouses and other data sources, like Salesforce or SQL Server. Then we have a tab for data policies. This section lets you set up policies to restrict which data connector can be used with a database to limit what data can flow into or out of database tables. We look into data policies in the in alater lecture, we looked at this analytics tab andwe looked at how we can change filters andset up different environment or date settings. We looked at this resource step, and that's all. These are all the various features available in the Admin Center. Thank you.

21. Environment Settings

We'll look at environmental settings in this lecture. So let us go back to power. Apps, settings. Admin center. This will take us to PlatformAdmin and a list of environments. Let's select our environment. It will show the environment's details, like access, resources, updates, and version. So let's go to the settings, and you will get the Environment Settings page. first look at relevance. Search Relevance. The search function is located under product features. Let's go to product features. You can enable relevance search here. So if you go down, this is a place to switch on and off relevant searches. Now, Relevance Search is an AI search where you can search for an entity. It's not an exact search, but it uses AI and finds you the best match. So these are the screenshots of what we just saw. Let us now navigate to the Privacy and Security settings. Return to the Privacy and Security settings. Now, these are all the privacy and security settings. You can show your own privacy statement by switching on and providing your URL. Then you have default actions when an error occurs. One is asking the user for permission to send an error report to Microsoft. Automatically send an error report to Microsoft without user interaction. Never send an error report to Microsoft. Then these are the listed exceptions that are blocked. Then you can configure a session expiration. You can specify the maximum session length and how long before a session expires a timeout warning is displayed. And then you can set an inactivity timeout. So these are all the privacy and security settings. Again, we have screenshots here for your reference. Then you can manage business units. When you click on business units, it's under user and permissions. You will get this screen. This shows you all the business units. Assume there is a hierarchy. You can have all your business unitsor departments in heracultical motion fashion here. So let's say we want to create a business unit for, let's say, Azure. We can do that. Azure is under PL 200 US, and Dynamics is under Azure. Now, an organisation is the top level of a Windows unit. An organisation name is derived from a domain name when the environment was provisioned. So organisation environment name is same asthe top level business unit here. Now, each business unit can have just one parent business unit. And each business unit can have multiple child business units. So it's like a tree structure that has just one parent but multiple children below it. This is the screen we just saw to create a child for a new business unit. Then next is team. You can create your own teams. So you have teams here under user and permissions. If you click, you'll be taken to this screen, where this team is automatically created, followed by the rest of the teams you can create. So, let us create a new team, say, and remember that it is under, and we can choose any business units. So let's say we test. Test for Dynamics 365 and let us create this new team. Once we create this new team, it will start showing up here. So you'll have to refresh the page, and it will show up here, maybe after some time. So this is the screenshot to create teams: These are all the screens, other devices, and environment settings that are relevant to our exam. Thank you.

22. Auditing & Duplicate Detection

In this lecture, we'll talk about auditing and duplicate detection. So let's go back to the application. So we click on the wheel and click on Advanced Settings. Under advanced settings, we go to settings for system and auditing. And under auditing, we click on Global Audit Settings. So when we click on this link, we'll get this screen, and on this screen we have to select Audit Settings. We can click on Start, Auditing Audit, User Access, Start, Read Auditing, and we can enable auditing in the following areas: common entities (sales), marketing, and customer service. Entities are related to Dynamics 365. So if you are using Dynamics 365, the corresponding entities can be enabled for auditing. Cancel this. Once we enable global auditing, we have to enable ordering at the entity level. So we have to go to Settings, Customizations, and Customize the System. Customizing the system is a very powerful tool, and you can make a lot of settings here. So go to entities, and we have to enable the auditing by entity or table. So let us go to the account entity. Let us see, and under the entity general settings, you will see that under Data Services you have an audit. So I got to click thatto enable auditing on this entity. So these are the screenshots for your reference. Go to advanced settings, auditing, and globalaudit settings, and enable auditing globally. Then go to Customizations, customise the system and the particular entity, and enable the auditing. This will start the auditing of those particular entities. Now, moving on to duplicate detection, let us close this. For duplicate detection, what you'll have to do is go to Tables and select the table on which you want to set the duplicate section. Let us pick PC manufacturers, and under Settings>More Settings collaboration, under Create and Update Things, you have a checkbox for duplicate detection. You have to enable this. Once you have done that, duplication is detected based on certain rules. To set those rules, go back to Advanced Settings, System Data Management, and then click on Duplicate detection rules on the screen. Duplicate Detection Rules: Here you can set how the system will identify whether the two records are duplicates or not. while it's loading up. Let us look at the screenshots. We have seen this under "Configure Table," where you have to select "Duplicate detection." And then we went to Advanced Settings, System Data Management, Duplicate Detection Rules, and this is a screen that should come up. So let us set a new duplicate detection rule here. We give it a name, saying that the "duplicate account-past record type" is the starting record type. That is account matching. Record type is the record to which it is matched. It will match, say, Account. Again. Case-sensitive refers to whether or not the matching is case-sensitive, and exclude inactive matching records refers to whether or not inactive records will be excluded from matching. If you select this, then we have to select the field on which it will match. Assume that the criteria for an account name can be an exact match: the same first or last character. So let us say "exact match." And here we can select "ignore blank values." In case we say same first characters,we can say how many characters. Similarly, if we say the same last character, we can say how many characters there are. And then we can add multiple rules here. And this is how you tell the system how to match duplicate records. coming back to the screen. This is the same screen for your reference. In the Base Record Type list, choose the type of record that this rule applies to. In the Matching Record Type box, choose the type of record to compare. Now, the matching record type can be the same or different. Generally, it is the same. If you want the rule to consider only active records while detecting duplicates, select Exclude in the Active Matching Records box. And if you want the rule to be case-sensitive, select the case-sensitive checkbox. Now for each new criteria, select the field column to select and then choose the field. Here we have selected an account name. Choose an operator. The operator will be an exact match, with the same first or last characters. In the case of the same first or last character, enter the number of characters, and you can select Ignore blank values. If you don't want the rule to consider blank fields, This is the classic administration centre or solution explorer, which we just saw. So this was all about auditing and duplicate detection. There are a few things that we should understand so that we are able to answer questions properly on the exam. So one is the Power Platform Admin Center. This is what we saw when we went to the Admin Center. From the advanced settings, it is basically beneficial for usage reporting, including how much data is consumed. This we saw in data usage, how much data is consumed by the database, by audit logs, what applications are being used, what entities are being used, and what is going on in each environment. And then you have power. platform admin portal. It is used to manage environments and users quickly. Then we have power apps and advanced customizations. This is where we are setting rules. We are going to customise the system or we are going to do data management. So this is that part. So this offers a quick way to add users and set permissions by using the Gear menu within Power Apps. And then we have a classic administration centre solution. Explorer: This is the place where we went to the Account entity and set duplicate detection rules. This is the original of all the administration portals and the portal with the most extensive administration options. This is your final stop and will have anything that you need. So now we have all the available options. The Power Apps, Admin Center, or Advanced Customizations within PowerApps mostly offer a subset of administrative options that are found within the classic Administration Center or Solution Explorer about auditing, duplicate detection, and various portals available within hours. Thank you.

Security

1. Welcome

Congratulations on completing the database section of the course. We now move on to the next section, security. from the Exam Outline perspective. Both database and security belong to Section One of the exam outline. Thank you.

2. Users & Roles

We will talk about users and roles in this lecture. So to go to users, you have to go to the admin portal, select the environment, select the settings, and then you will see the option for users. So let us go to the application, click on Start, and go to the Admin Center. Once you are in the Admin Center, you will see all the environments. Under the environment, select the environment for which you want to manage users, and under the environment, you will have an option for settings. Click on Settings, and under Settings you will see an option for users. So if you click here, you will see all the users. When you click on Users, you will be taken to this page, where you can see all of the users and add a new one. Now let's move on to roles. So this is related to Exam Objective: Create and its security roles. In the same option for users, you will have an option for security roles as well. If you click on Security Roles, it will show you all the security roles, and then you can add a new role. So these are all the security roles, and the main roles that you will have to look at are System, Administrator, Environment Maker, Support, User, System, Customizer, and Delegate. Let us go back. So once you have all the roles and you click on New Role, you will get this screen where you can create a new role. You can also click on a role and say, "Make a copy of that, edit it, and delete it." So give it a role name, and on the role level, you have these options noneselected at user level, at bu level, at parent-child level, at bu and organisation level, and all the entities are grouped into these categories: core records, marketing, sales, service, business management, service management, customization, missing entities, business process flows, and custom entities. In core records, we have things like "Accountand all," and for each entity, you can set the permissions for "Create, Read, Write, Delete, Append, Append to Assign, and Share." So an empty circle means none are selected. This includes the user, the child, the parent, and the organization. You can also change the settings for all these things by clicking here also.As a result, the user, bu, parenthetist, and organisation allow us to learn more about them. We'll talk about systems and status roles. So Environment has two built-in roles that provide access to permissions within an environment or system. The admin role can perform all administrative tasks, such as adding or removing users or groups from either environment, admin, or Environment Maker. Provisionmicrosoft Data was a database for the environment. It was used to review and manage all resources that are created within an environment and set data loss prevention policies. We'll talk about data loss prevention policies in our later lecture. So this is basically an admin role. Then the environment maker role is used to make any changes to the environment, like adding an entity, managing data updates, and things like that. So the environment maker role can create resources within an environment, such as app connections, custom connectors, gateways, apps that use our apps, and floors that use power automation, so they can distribute the apps that they built in an environment without automatically giving them access to the environment database. When you add a user to an environment, they are assigned two roles by default, which are database users and environment makers. The next role is system customizer. So for users who make apps that connect to databases and need to create or update entities and security rules, you need to assign the system customizer role. So this is to update entities and to create or update entities and security rules. This is necessary because the environment-maker role does not have privileges on environment data. Add the System Customizer role to the user if you want them to be able to create new entities. So once you go to a role screen, you have the option to create a new role. We just saw that, and if you click on the arrow, you can also have the option to copy, edit, or delete. You will use the copy options in case you want to make slight changes to an existing role. This is the screen we saw when you create a new role, and at the bottom you have a key, and we can set the permissions for each of the entities. Now, what this means is that records access is given to all the records within that business unit as well as all the records between that business unit and all the child business units and the complete organization, and then for each entity you have to create, read, write, delete, append, append to, assign, and share. So let us understand: What do they mean? "Create" means you are adding a record. "Read" means you can read the record. "Write" means you can update the record. Delete means you can permanently delete the record, assign means you can assign the record on a shift to some other user, and share means you can give access to the record that you own to some other user. Then we have these permissions for append and appendix, which are a little confusing, so for example, if you have an opportunity entity and you want to link notes to it, to do that you need to write an opportunity and append two rights on a note. So to append an associated record with the current record, for example, if a user has appended notes on an opportunity, the user can add a note to the opportunity and append to associate the current record with another record. For example, a note can be attached to an opportunityif the user has append two rights on the note. So to add a note to an opportunity, you need to append rights to the opportunity and append two rights to the note. This was all about users and roles, and you're creating a role to see what permissions you can set at the entity level. Thank you.

Go to testing centre with ease on our mind when you use Microsoft Power Platform PL-200 vce exam dumps, practice test questions and answers. Microsoft PL-200 Microsoft Power Platform Functional Consultant certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Microsoft Power Platform PL-200 exam dumps & practice test questions and answers vce from ExamCollection.