Free Microsoft PL-600 Practice Exam with Questions & Answers | Set: 4

Box 1: Omnichannel for Customer Service dashboard

Scenario: Workers must be able to communicate in near real-time with worker support agents.

The company has a team or worker support agents that respond to inquiries from current and prospective workers. Some of the worker support agents are multilingual.

If you choose to expand your customer service offering to provide chat and channels, the Customer Service workspace seamlessly adjusts to support managing conversations as well.

Note: As an agent with the Customer Service Representative security role, when you open Customer Service workspace, you start on the Customer Service Agent Dashboard unless your administrator has changed the default view. This dashboard shows you your active cases, cases you can work in queues you are assigned to, and your open activities. You can open existing cases and activities or begin working new cases from the queues you are assigned to and create activities.

Box 2: Dynamics 365 Customer Service

Scenario: First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.

Scenario: Information about each machine produced must be transferred to Dynamics 365 Field Service.

Use the Microsoft Dataverse connector when connecting to the Microsoft Dataverse used for Microsoft Dynamics 365 Sales, Microsoft Dynamics 365 Customer Service, Microsoft Dynamics 365 Field Service, Microsoft Dynamics 365 Marketing, and Microsoft Dynamics 365 Project Service Automation.

Need to store the image in the table.

Scenario: The company uses photos of employees to generate employee badges. Photos are uploaded into Microsoft 365 user profiles.

Business rule can create business recommendations based on business intelligence.

Scenario: Analytics and reporting

The solution must:

Provide metrics including existing and upcoming demand by inspection station, average time spent per user at a station, and average time a machine spends at each inspection point.

Provide metrics per inspector including number of inspections performed by month, and number of inspections per rating type (pass, fail).

Provide a printed quality certificate to be included with each machine.

Box 1: Schedule board

Note: The Dynamics 365 Field Service schedule board provides an overview of resource availability and bookings you can make.

When you’re looking at the schedule board for the current day, you’ll see a blue line that indicates the current time of day. You can also see a picture of all the resources listed on the schedule board. To quickly view contact information for a resource, hover over their name to view the contact card.

Box 2: Azure IoT Central connector

Azure IoT Central makes it easy to connect, monitor, and manage your IoT devices at scale. With the IoT Central V3 connector, you can trigger workflows when a rule has fired, and take actions by executing commands, updating properties, getting telemetry from devices, and more. Use this connector with your Azure IoT Central V3 application.

This connector is available in the following products and regions:

Box 1: Schedule board

The Dynamics 365 Field Service schedule board provides an overview of resource availability and bookings you can make.

Box 2: Azure IoT Central connector

Information about each machine produced must be transferred to Dynamics 365 Field Service.

The difference between IoT hub and IoT central is that IoT is an application platform that simplifies the creation of Internet of Things solutions. IoT central helps to reduce the challenges of implementing IoT development, operations, and management. IoT Central is a fully managed Software as a Service solution.

Note: There are three ways you can use to connect IoT-enabled devices into the Field Service solution:

Connected Field Service for Azure IoT Central

Connected Field Service for Azure IoT Hub

Connected Field Service for non-Azure IoT providers using the extensible IoT provider framework

Box 1: Create a lookup to Dynamics 365 Field Service

Scenario: Machines are assigned serial numbers and placed in stock until they are shipped to customers.

Entity lookup: Allows technicians to choose a Dynamics 365 record. In the inspection designer interface, admins must select an entity and a field to display. For a chosen entity, the Name field and mandatory fields are the entity attributes that can be displayed in the lookup.

Box 2: Create a one-to-many relationship and set the behavior to Parental

Scenario: Inspection orders must:

Allow entry of quality ratings of passed or failed for each quality metric identified for the machine being rated.

Be automatically marked as failed if one inspection step rating is marked as failed.

Each inspection order can have one or many inspection steps, and each inspection step has a rating.

Note: Each pair of tables that are eligible to have a 1:N relationship can have multiple 1:N relationships between them. Yet usually only one of those relationships can be considered a parental table relationship.

Scenario: Standardized checklists must be stored in the solution for use by inspectors. A copy must be created when a new inspection is initiated.

Dataverse for Teams – built on Microsoft Dataverse – provides relational data storage, rich data types, enterprise-grade governance, and one-click solution deployment to the Microsoft Teams app store.

Dataverse for teams table creation has all of the things that are great about Microsoft Lists, without the major downsides.