Pass Your Microsoft Certified: Dynamics 365 Customer Service Functional Consultant Associate Certification Easy!

Prepare with top-notch Microsoft Certified: Dynamics 365 Customer Service Functional Consultant Associate certification practice test questions and answers, vce exam dumps, study guide, video training course from ExamCollection. All Microsoft Certified: Dynamics 365 Customer Service Functional Consultant Associate certification exam dumps & practice test questions and answers are uploaded by users who have passed the exam themselves and formatted them into vce file format.

Security

3. Field Level, Hierarchical & Conditional Access

In this lecture we'll talk about feedlevel security, hierarchical security, and conditional access. So, first is field-level security. Let's get to the application. So, I created the four-column PC type for table PC manufacturers. Under advanced options, I have enabled column security. So once I have enabled column security, what I can do is go to advanced settings, settings for system security, and go to hierarchy security. No, not hierarchical security. We'll move on to field security profiles now. What we can do is allow new teams and users to have access. And you will see under field permissions that we have PC type because we have set column security here. So these are the screenshots for your reference. name column security at column level and then go to advanced settings, system security, field security profiles, and you can add teams, users, and field permissions. This is related to the exam objective of creating and managing column security profiles. So, moving on to her key security, let's look at her key security. So we'll head over to her key security. Once we go to Haircut security, we have to enable it, and then we can select the model. It can be a manager's hierarchy or a position's hierarchy. So manager hierarchy is like this: your team reports to you, and you report to somebody above you. And the CEO position is at the top of the position hierarchy. And under CEO position you have VP. And under the VP, you have senior managers. And like that, you can configure the depth and how many lower levels a person has access to. And then you can select entities for which access is available, any available entities, and excluded entities. You can also configure position hierarchy in the settings, system security settings. You can also set the position here. So I've already defined some positions here. Key, you have CU at the top. Under Co. You have VPs of Sales and VPs of Service. Under the VP of Sales, you have sales managers, and under the VP of Service, you have service managers. So let's say we'll create one more position. We'll create a sales position, which will report to sales managers, and then that will get reflected here. And then we can select the parent. Parent is a sales manager, and you see sales staff reporting to sales managers. So manager hierarchy, the managers are able to accessthe data that their reports have access to. and position hierarchy. Users at higher positions in the hierarchy have access to more data than users at lower positions. So we saw it was disabled by default, and we have to enable it. The major difference between position and manager hierarchy is that with manager hierarchy, the manager must be in the same business unit or in the parent business unit. But position hierarchy allows you to extrapolate across business units. So this is a screenshot for reference. Go to System Security, Hierarchy Security, and the Hierarchy Security menu. You enable hierarchical modelling and select the hierarchy model, whether it's manager or position, and then you select the depth, or how much depth the access will be there.And you can manage users and positions here. So if you click on position, you can create a new position and select the parent position. So that was about hierarchy. Now let us move to conditional access. With conditional access, policy administrators can make use of signals from conditions like risk, device platform, or location to enhance their policy decisions. So here, access is based on certain conditions and certain risks. For example, a sign in risk So there's a probability that a given authentication request isn't authorised by the identity owner or user. Risk represents the probability that a givenentity account is compromised or device platform. As previously stated, conditional access supports the following device platforms (Android, iOS, Windows Phone, and Mac OS), location, and some organisations may choose not to require multifactor authentication if the user views from trusted networking locations such as their physical headquarters. But if they are not in the physical location, then they might need multi-factor authentication. So that is a concept of "conditional access" for client apps. By default, all newly created conditional access policies will apply to all client types, even if the client type condition is not configured. So that is about conditional access. Thank you.

4. Data Loss Prevention Policy & Starters Kit

In this lecture, we'll talk about data loss prevention, policy starter kits, and some other topics. So here is a link to YouTube on security. It's a half-hour video, and it's a nice one. I recommend that you get it. And these are all the licencing plans available. One is Microsoft 6365. It includes Word, Excel, SharePoint, and Office assets. Then we have Dynamics 365. It includes Dynamics 365 sales, customer service, feed service marketing, and product service automation. Then we have the Power Apps plan. It includes all the Power apps and makes enterprise connections and databases accessible for users to use robust business logic across application types and demonstration capabilities. The PowerApps Community is the one we use. It allows a user to use PowerApps, an automated database, and customer connectors in a single instance for individual use. Then we have Power Automate Free, which allows users to create unlimited flows and do 750 runs. And then we have power. Automate paid. So here is the security model. So it's a high-level view of the security model implemented in database servers that are authenticated using Azure Active Directory. And we have Environment, which is a container for all the resources used by Power as an automated database. So, in our course, we've created a PL 200 US environment. All previous plants are accumulated with the greatest amount of access prevailing, and the database supports two types of required ownership: organisation owned and user owned. This is a choice that happens at the time the table is created and can't be changed. So we have looked at it; let's look at it again. If we go to database tables and create a table, you will see these two options. So under more settings under table type ownership, it can be user, team, or organization. Now let's talk about the environment. When you create environments, you can create any one of these three types: sandbox, production, and trial. Sandbox environments are used for building proof-of-concept applications and flows that might need to be reset without recreating the entire environment. Production environments are suited for stable workloads, and trial environments expire after 30 days. So these environments are the best to evaluate technologies. Now let's talk about data loss prevention policy. Once you go to Admin centre youhave an option of data policies. So let's create one. When you create a policy, let's say "test policy," this policy has all the connectors, and these connectors are split into three groups: business, nonbusiness, and blocked, and connectors in one group cannot talk to connectors in other groups. So, if I move this connector to business, I'll have one character in business and everything else in non-business. You can then choose which group is the default: business, non-business, or block. We'll leave it alone and move on to the next one. You tell which environment it is applicable to, and then you review it and create a policy. Once a policy is created for an environment So this is your policy. Once your policy is created for an environment, the data connectors in one group will not be able to talk to another. So here are the screenshots. Once you create a policy, they can be grouped into these three. And the meaning of "default group" is that whenever a new connector is introduced by Microsoft, it will go under the default group. So data loss permission policies allow organisations to construct rules that permit and prevent connectors from communicating with each other within the same flow. And there are two databases: business data only and no business data allowed. So grouping connectors means that they can communicate with each other in the same data group but are not able to communicate across data groups. Here we are setting the default data group. So the default data group becomes the data group that all new connectors are added to. So, for example, Microsoft deploys a new connector to the Power Automate service, so that connector will be added to the default database. So environments can have multiple data loss prevention policies applied; however, the most restrictive policy is applied. So let's move now to this being all about data loss duration policy. Let's move to the Center of Excellence starter kit. So it's a huge task to set up your environment. So there is a starter kit provided, which gives you some guidance. As a result, the Power Platform Center for Excellence starter kit is a collection of apps, floors, custom connectors, and a PowerBI dashboard that enables automation on their power platform environment. So this tool is available for free on GitHub, and it gives you a Power BI dashboard that gives you an overview of the entire environment. So this is the URL for the COE Starter Kit, and once you set it up, the Power Bi report will be visible. So these are the various reports available. Let's look at the report. You see on the left hand side, you have all the applications, like total applications, how many were created this month, and how many application makers there are. On the right hand side, you have flows, total flows created this month, and flow makers. Then you have these applications by place and application maker. You have flows by city and flow metres as well. And in the middle you have total environments—how many were created in the last 30 days? Environment creators and custom connectors And then you have top environments, and you have floors and applications against them. You have information and environments in the middle. Now, these are the reports available. So an overview includes the total number of apps and flows. Environment highlights the number of environments that have been created. Apps provide insights into the usage of those apps. App TTS examines the specifics of the appflows and displays a total creation trend that will break down when flows are created. A custom connector is any custom connector found within a tenant. Makers locate all other makers in the environment. Connections display the number of connections that have been established by a connector. Let's move on to app order. So, the main purpose of the sample app order process is to demonstrate how an admin can identify overused or often-used resources and gather further information like business justification and business impact. These situations might also occur when people create temporary applications for proof of concept, and these applications can clutter the environment if they are not clean them.So the app catalogue acts as a catalogue that helps the discoverability of apps, and you can remove the apps that are not being used. So there are four types of configurations available by default. The first is a single centralised region or organization, followed by a single decentralised reason, followed by multiple centralised and multiple decentralised reasons. The first is single-region centralized. So, on the right, we have a centralised single reason. As a result, this environment will also be influenced by one factor. And you have environments for personal productivity, development, testing, and production. So here environments are centrally managedand include isolation for production, personalproductivity, development, testing and production purposes. The Central Team manages the environment to provide access. Then you have a centralised one where you have environments for each department like HR, Finance, and Operations. Individual business units have also been assigned invested responsibilities. They are not centralized, they are assigned to the individual business units. The organisation operates within a single region, and the default environment has been renamed to personal productivity. Additional environments have been created for respected regions and units like Agile Finance, Operations, and IT. Then we have centralised multiple regions. Here you have a different environment for each region like Asia, North America, and Europe, and then you have employment for personal productivity, development, testing, and production. Now, because the organisation operates in multiple regions throughout the world, an environment must be created within each region where it operates. So in all the regions where the organisation operates, an environment is created, and it is managed centrally. Finally, you have multiple decentralised regions. There are environments created for each region, as well as ones for each department, such as HR Finance Operations. So the organisation operates in multiple regions, and the default environment has been renamed to personal productivity here and resides within the same region as Ten in North America. So this is all about data protection, policies, centres of excellence, and a few other topics. Thank you

5. Solutions & Analytics

In this lecture, we'll talk about solutions and analytics Let's take a look at solutions. In the Power Apps app, at the bottom, there's a tab for solutions, and here we can create a new solution, so let's give it a name, and publisher will be the default publisher, then more options. And we have two types of solutions: managed and unmanaged, so by default it is unmanaged. Once you create a solution, it will allow you to add various components to it, so once you have a solution, you can add various components to it like applications. Dashboard workflows. Cloud workflows. desktop workflows, so let us add our table so we have a cruise table. We have added cruise table then let us add asignature table and then we'll add PC manufacturers so weare not adding any application or workflow in this testsolution so once you have added components to a solutionyou can export it and you can publish your changesand then check for any issues then you can exportas a managed or unmanaged solution so the difference betweenmanaged and unmanaged is managed solution cannot be changed. They are installed and uninstalled as a single unit. While unmanaged solutions are being uninstalled, the corresponding corporations are not being uninstalled automatically and must be done manually, so let's say unmanaged once we create an export it exports, so let's go take a look at it. You will see that in the solutions, there is a formula for the change count, where we counted the number of passengers on the cruise. So now it has exported a solution and is saving it to my laptop, so solutions allow you to package components to transport them from one environment to another; only metadata is transported and business data is not transported. No business data is transported, and solutions can be managed or unmanaged; you cannot export a managed solution, which also applies when a managed solution is deleted. All included customizations and extensions are removed, so this is a screenshot. Just go to the Solutions tab. Create a new solution and fill in all these details. This shows up like this, and then here we are adding various components to a solution, which then we publish. Check for issues and export it as a managed or unmanaged solution, so this is an overview of the difference between a managed and unmanaged solution. unmanaged solution you can change any of thecomponents of the solution deleting the unmanaged solutiononly deletes the reference to the solution. Not the customization components this we talked aboutearlier manage solution is a finalised solution thatcan be distributed and installed deleting a managedsolution will remove all its customizations as wellas data unto all that removing a managesolution after deploying to production is simple andonce your deploy is managed in production. You cannot change back to unmanaged, so this is all about solutions now moving to analytics. So if you go to Admin Center, it providesyou analytics for Database, power, Automate and PowerApps. So if you click on Database, you have reports for Home Active Users, Mode of Access, Entity Usage, System Jobs Plugins, API Calls at Mailbox Usage, etc. You need not memorise everything; this is just for your awareness, and you can change filters where you can set the environment and date. Similarly, if you go to Power Automate, you have reports for runs, usage created, error shared, and connected, and again, it has data for the last 28 days, and you can change it to a shorter time. Similarly, if you go to Power Apps, it has reports for usage, location, toast errors, service performance, and connectors, and you can change the duration and environment. The duration can be 28 days or less. So Power Automate reports have reports on runs, usage created, errors shared, and connectors. Status can select the filter icon on the upper right corner to select the environment and time period. So this is the screenshot we just saw from PowerPlatform admins' internal storage of analytics for up to 28 days, and then Status can expect up to a three-hour delay before the latest analytics are published. So these are all the reports for Power Automate with runs. The administrator will be able to determine the number of flaws run each day, week, or month. The usage report outlines the types of flaws used, including whether the flow is scheduled, button-clicked, system-event driven, or not created. Flow reports will be broken upon my scheduled button click The System Events error report will be organised by error count and last occurred timestamp, while the flow creator email information shared report will identify the types of flows shared, including system events button clicked and scheduled. Connectors is the most important report to consider. When you are ready, there will be changes that will tell you all about connectors, which form a key input to creating a DLP policy. Now again, you do not need to memorise everything; you just have a look at it and understand it for your awareness. So this is a screenshot of database analytics and PowerApps analytics. So that is all we talked about: DLP and analytics. Thank you.

6. ALM - Application Lifecycle Management

In this lecture, we talk about ALM or application. Lifecycle management. So there are some tools available that help us manage application lifecycles. So what is "application"? Lifecycle. Application Lifecycle refers to the people, tools, and processes that manage an application's lifecycle from conception to end of life. This includes doing requirements, then putting it into a test environment, a development environment, a production environment, making regular updates to it, and finally retiring. So we'll talk about four things. A deployer tool and a solution packager tool are included in the solution configuration migration tool package. Each of these tools helps us in different ways. The solutions are used to transport applications and components from one environment to another. They apply a set of customizations to existing application solutions that you cannot use to transport data. They will only transport applications, components, and customizations. So if you go to your power apps, you see solutions at the bottom, and you see all your solutions. So you can create a new solution and add various components to it. It will export the solution, and then you can import the solution into another environment. Next is the configuration migration tool. Now, this Configuration Migration Tool will help you transport configuration and test data from one environment to another. So this will complement your solution. Then you have a package deployment tool. Now package it so it deploys packages or a Microsoft Database instance, and it includes one or more solution files, data files such as Slack files, or export configuration data. You can also include custom code, which can run before, during, and after the package is deployed. It can run; you can configure it to run before the package is deployed, while the package is deploying, and after the package is deployed, and it can also contain HTML content specific to the package. Lastly, we have a solution-packaged tool. Now, Solution Packaged Tool will basically decompose a solution file into multiple XML files and other files so that you can put all these files into a source control system, and that is how you can manage version control of your solution. So that's about it. This lecture will talk about four tools. Thank you.

ExamCollection provides the complete prep materials in vce files format which include Microsoft Certified: Dynamics 365 Customer Service Functional Consultant Associate certification exam dumps, practice test questions and answers, video training course and study guide which help the exam candidates to pass the exams quickly. Fast updates to Microsoft Certified: Dynamics 365 Customer Service Functional Consultant Associate certification exam dumps, practice test questions and accurate answers vce verified by industry experts are taken from the latest pool of questions.