Free Microsoft PL-200 Practice Test Questions MCQs

Explanation
This question tests your understanding of entity relationships in Microsoft Dataverse. Based on the business requirements, you need to establish the correct cardinality between the Loan Applicant, Loan, and Property entities. The key is to analyze how records from different tables relate to each other in real-world scenarios. Understanding one-to-many (1:N) and many-to-one (N:1) relationships is crucial for proper data modeling in Power Apps.

Correct Options:

Requirement 1: "The email attribute must provide a look-up to the contact name"

Relationship Type: N:1
The requirement states that the Email attribute should provide a look-up to the contact name. In Dataverse, when you want an attribute (like Email) to look up values from another entity (likely a Contact entity not shown in the table), you are creating a Many-to-One relationship from the Loan Applicant to the Contact entity. This means many Loan Applicants can be associated with one Contact record.

Requirement 2: "Loan applicants can apply for one type of loan per application. Applicants can have more than one application"

Relationship Type: 1:N
This requirement describes a classic one-to-many relationship between the Loan Applicant entity and the Loan entity. The statement explicitly says "Applicants can have more than one application," which means one Loan Applicant record can be related to many Loan records. This is a 1:N relationship with Loan Applicant as the primary (one) table and Loan as the related (many) table.

Requirement 3: "Loans must be applied for for a single property"

Relationship Type: N:1
This requirement indicates that each Loan is associated with only one Property. Therefore, from the Loan entity's perspective, many Loan records can be associated with a single Property record. This creates a Many-to-One (N:1) relationship where the lookup field for Property resides on the Loan entity.

Incorrect Options:
N:N (Many-to-Many): This relationship type is not required in any of these scenarios. A many-to-many relationship would be needed if, for example, one Loan could have multiple Properties (which contradicts the requirement) or if multiple Loan Applicants could share the same Loan (which contradicts the requirement that applicants apply individually). The business rules specify clear "one" side constraints that make N:N relationships unnecessary.

Reference

Microsoft Learn: Create and edit entity relationships in Dataverse

Microsoft Learn: Types of entity relationships

Explanation
This question focuses on the process of creating and using a prediction model in AI Builder for sales forecasting. When building a prediction model, you need to follow a specific workflow: first prepare your data, then train the model, and finally make it available for use. The scenario mentions that you have already selected the fields for prediction, so the next steps follow the standard AI Builder prediction model lifecycle.

Correct Sequence:

Step 1: Train the prediction AI model by using Common Data Service data
The first step after selecting fields is to train your prediction model. Since your data resides in Dataverse (Common Data Service), you train the model directly using this data. AI Builder prediction models learn from historical data to predict future outcomes. In this sales forecasting scenario, the model would analyze past sales data to identify patterns and predict future revenue trends.

Step 2: Publish the AI model
Once the model is trained and you're satisfied with its performance score, you need to publish it. Publishing makes the model available for use in Power Apps, Power Automate, or directly in Dataverse. This step essentially deploys the model from the training environment to a production-ready state where it can process new data and generate predictions.

Step 3: Use the model with Power Apps
After publishing, the final step is to consume the model within Power Apps. You can embed the AI prediction directly into your sales forecasting app, allowing sales managers and executives to view predicted revenue based on current pipeline data. The model can provide predictions on opportunities that are likely to close, helping the company improve their sales forecasting accuracy.

Incorrect Actions:
Export data to Excel/Import analysis to Dataverse: These actions are not required in this sequence. While you could export data for training, the scenario specifies using Common Data Service data directly. The import step would come after using the model if you wanted to store predictions, but it's not part of the core three steps.

Train category classification model: This is for a different type of AI model (text classification) not relevant to sales forecasting predictions.

Train model using exported Excel data: Since the scenario specifies using Common Data Service data directly, this extra step is unnecessary and would add complexity.

Reference

Microsoft Learn: Get started with AI Builder prediction

Microsoft Learn: Train and publish a prediction model in AI Builder

Explanation
Business rules in Power Apps (model-driven and canvas apps) provide a no-code way to apply logic and validation. However, there are specific limitations on what business rules can do in canvas apps versus model-driven apps. Understanding these limitations is crucial for the PL-200 exam, as Microsoft tests your knowledge of where business rules can be applied and what actions they support.

Correct Options:

A. Validate data and show error messages
Correct: Business rules can validate data and display error messages to users. For example, you can create a rule that checks if a discount percentage exceeds a certain threshold and shows an error message when invalid data is entered. This is one of the primary uses of business rules across both app types.

C. Set field requirement levels
Correct: Business rules can set field requirement levels (Business required, Business recommended, or Not required). This allows you to dynamically change whether a field must be filled based on conditions. For instance, if a customer type is "Business," you might make the Company Name field required.

D. Set field values
Correct: Business rules can automatically set field values based on conditions. For example, when a user selects "United States" from a country dropdown, you can automatically set the currency field to USD. This helps automate data entry and ensure consistency.

Incorrect Options:

B. Enable or disable fields
Incorrect: While this action is available in business rules for model-driven apps, it is NOT supported for canvas apps. In canvas apps, you would need to use formulas or variables to control field enablement. This distinction is important because the question specifically asks about canvas apps, making this option invalid.

E. Show or hide fields
Incorrect: Similar to enable/disable, showing or hiding fields is supported in model-driven apps but NOT in canvas apps through business rules. Canvas apps require conditional formatting using the Visible property of controls. This limitation is clearly documented by Microsoft.

Reference

Microsoft Learn: Create a business rule for a canvas app

Microsoft Learn: Business rules and recommendations in Dataverse

Microsoft Learn: Differences between business rules for canvas and model-driven apps

Explanation
Regression testing requires automating test execution to verify that application updates haven't broken existing functionality. For testing Power Apps and business applications, Microsoft recommends using Power Automate desktop flows (RPA) and Windows Recorder (V1) specifically for UI testing scenarios. Windows Steps Recorder is a manual documentation tool, not an automated testing solution.

Correct Options:

B. Windows recorder (V1)
Correct: Windows Recorder (V1) is a legitimate tool for recording UI interactions that can be used for basic regression testing scenarios. It captures mouse clicks and keyboard inputs that can be replayed, making it useful for simple test automation of desktop applications and some web interfaces.

C. Power Automate desktop flow
Correct: Power Automate desktop flows provide robust RPA (Robotic Process Automation) capabilities specifically designed for UI automation and testing. They can record and replay test scenarios across applications, handle dynamic data, and include conditional logic - making them ideal for comprehensive regression testing of the three business apps.

Incorrect Options:

A. Power Automate automated flow
Incorrect: Automated flows (cloud flows) work with APIs and connectors, not UI automation. They cannot interact with application user interfaces directly, which is essential for regression testing of applications. They require pre-built connectors or APIs, which may not exist for custom business apps.

D. Windows Steps Recorder
Incorrect: Steps Recorder (Problem Steps Recorder) is a manual documentation tool that captures screenshots and steps as images and text for bug reporting or training documentation. It does NOT automate testing - it simply records what a user did for manual review later. It cannot replay or validate test results automatically.

Reference
Microsoft Learn: Automate regression testing with Power Automate desktop flows

Microsoft Learn: Windows Recorder (V1) for UI automation

Microsoft Learn: Differences between desktop flows and cloud flows

Explanation
When creating Power Apps apps specifically for Microsoft Teams, Microsoft provides a specialized environment type called Dataverse for Teams. This environment is automatically provisioned when you create or install an app in Teams, and it comes with built-in storage and capabilities designed specifically for Teams integration. Understanding this automatic provisioning process is essential for the PL-200 exam, as it differs from standard Dataverse environments that require manual creation.

Correct Option:

D. A Dataverse for Teams environment that is automatically created for the team.
Correct: This option accurately describes what happens when you create a Power Apps app for Microsoft Teams. Dataverse for Teams environments are automatically created the first time you add a Dataverse for Teams app to a team or create a Power Apps app within Teams. Each team gets its own environment, which includes relational data storage, logic, and integration with Teams members and security. This environment is lightweight and designed specifically for in-context app development within Teams.

Incorrect Options:

A. An existing Dataverse environment that you select.
Incorrect: While standard Dataverse environments can be used with Teams through the "Add to Teams" feature for existing apps, when you create a new Power Apps app within Teams, the default and recommended approach is to use the automatically provisioned Dataverse for Teams environment. The question specifically asks about the environment that will be used, implying the default creation behavior.

B. An existing Dataverse for Teams environment that you select.
Incorrect: You cannot select an existing Dataverse for Teams environment when creating a new app in Teams. These environments are tied to specific teams and are automatically created and managed. Each team typically gets its own environment, and you cannot choose a different team's environment when creating an app.

C. A Dataverse environment that is automatically created for the team.
Incorrect: Standard Dataverse environments are never automatically created. They require manual provisioning by an administrator with appropriate licenses. The automatically created environment for Teams is specifically a Dataverse for Teams environment, which has different characteristics, limits, and capabilities than a full Dataverse environment.

Reference

Microsoft Learn: Dataverse for Teams overview

Microsoft Learn: Environments overview in Power Platform

Microsoft Learn: About Dataverse for Teams environment provisioning

Explanation
For unattended RPA (Robotic Process Automation) to work with UI flows in Power Automate, the target Windows 10 device must have no active user sessions. When a scheduled UI flow runs in unattended mode, the service needs to take control of a clean desktop session. Any active user session, even a locked one, will prevent the UI flow from successfully executing as it cannot establish the required session with the specified credentials.

Correct Option:

D. Ensure that there are no active user sessions on the device.
Correct: For unattended execution, the device must have all user sessions signed out completely. When the scheduled UI flow triggers, Power Automate will sign in using User1 credentials on the clean Windows 10 device, run the automation, and then sign out. This ensures the flow can run during non-peak hours without any physical intervention, exactly as the requirement states.

Incorrect Options:

A. Ensure that all user sessions are signed out except for locked user sessions.
Incorrect: Locked sessions are still active user sessions. When a session is locked, the user context is still loaded in memory, and unattended RPA cannot establish its own session. The automation service requires a completely signed-out state to initiate a fresh session with User1 credentials.

B. Ensure that the User1 account has an active user session on the device.
Incorrect: This describes an attended RPA scenario where a user is physically present. The requirement specifically calls for "no physical user intervention" and "non-peak hours" - which is exactly the unattended automation scenario that requires all sessions to be signed out, not active.

C. Ensure that all user sessions are signed out.
Incorrect: While this option gets closer to the correct answer, it is not the most precise option available. Option D specifically states "no active user sessions" which is the exact technical requirement for unattended UI flows. Option C could be interpreted as simply signing out sessions manually without addressing the active session state.

Reference
Microsoft Learn: Run UI flows in unattended mode

Microsoft Learn: Set up UI flows for unattended automation

Microsoft Learn: Requirements for unattended RPA with Power Automate

Explanation
In Power Platform, creating canvas apps that consume data requires specific permissions. The question specifies that the user already has access to the Common Data Service (Dataverse) database, meaning they can already view and interact with data. To create canvas apps specifically, they need the Environment Maker role, which grants permission to create resources within an environment including apps, flows, and connections, without granting administrative privileges or unnecessary data modification rights.

Correct Option:

D. Environment Maker
Correct: The Environment Maker role is specifically designed for users who need to create resources like canvas apps, cloud flows, and connections within a Power Platform environment. This role allows the user to create apps that consume Dataverse data but does not grant permissions to modify the Dataverse schema or data structure. Since the user already has database access (presumably through the Common Data Service User role or similar), adding Environment Maker gives them exactly the app creation capability they need without over-permissioning.

Incorrect Options:

A. Environment Admin
Incorrect: Environment Admin has full administrative permissions over the environment, including managing all resources, users, and settings. This role grants far more permissions than needed for simply creating canvas apps, violating the requirement to "not grant permissions that are not required."

B. System Customizer Incorrect: System Customi
zer has permissions to customize the Dataverse system, including creating and modifying entities, fields, and relationships. While this role does allow some app creation, it also grants extensive schema modification rights that exceed what the user needs. The user only needs to create canvas apps, not customize the underlying data structure.

C. Common Data Service User
Incorrect: This role (now called "Basic User" in Dataverse) provides fundamental access to read and interact with Dataverse data records. Since the user already has database access, they likely already have this role or its equivalent. However, this role alone does NOT grant permission to create canvas apps - it only allows using existing apps and accessing data.

Reference

Microsoft Learn: Security roles in Dataverse

Microsoft Learn: Environment Maker role overview

Microsoft Learn: Assign security roles to users in Power Platform

Explanation
This question tests your knowledge of AI Builder prebuilt models and their specific capabilities. Prebuilt models are ready-to-use AI models that require no training data. You need to match each business scenario with the correct prebuilt model that performs that specific function. Understanding the distinct purpose of each AI Builder model type is essential for the PL-200 exam.

Correct Answers:

Scenario 1: "Extract specific text from a PDF document"

Model: Text recognition model
The Text recognition model (also called OCR - Optical Character Recognition) is designed to extract printed or handwritten text from images and documents including PDF files. This prebuilt model can analyze PDF documents and extract the text content, making it the perfect choice for this requirement.

Scenario 2: "Determine the likelihood that customers will purchase additional products"

Model: Prediction model
The Prediction model is specifically designed for forecasting outcomes based on historical data. This scenario requires predicting future customer behavior (purchase likelihood), which is exactly what prediction models do. They analyze patterns in existing data to predict probabilities for new records.

Incorrect Options:
Key phrase extraction model: This model identifies the main talking points or key topics in a text, not for extracting all text from a PDF or predicting purchase behavior.

Sentiment analysis model: Detects positive, negative, or neutral sentiment in text, useful for customer feedback analysis but not for text extraction or purchase prediction.

Category classification model: Organizes text into predefined categories, useful for ticket routing or document classification, not for the scenarios described.

Entity extraction model: Identifies specific data elements like names, dates, or locations from text, different from full text extraction or purchase prediction.

Text recognition + key phrase extraction: Combining models isn't necessary for either scenario and adds unnecessary complexity.

Reference

Microsoft Learn: Prebuilt models in AI Builder

Microsoft Learn: Use the text recognition prebuilt model

Microsoft Learn: Use the prediction prebuilt model in AI Builder

Explanation
This question focuses on form customization options in Dynamics 365 Customer Service. The requirement has two distinct parts: embedding information from other entities (viewing data) and allowing users to edit that data. Different form components serve different purposes - some are read-only while others allow editing. Understanding these distinctions is critical for proper form design in model-driven apps.

Correct Answers:

For embedding information from other entities (View data):

Action: Add a quick view
A Quick View form displays read-only information from a related entity on a parent entity form. When you have a lookup field on a form, you can add a Quick View form to show selected fields from the related entity record. For example, on a Case form, you can show key fields from the related Contact record. This perfectly meets the requirement to "embed information from other entities" in a view-only format.

For allowing users to edit data from other entities:

Action: Add a sub-grid
A sub-grid displays a list of related entity records and, crucially, allows users to edit those records directly from the parent form. When you configure a sub-grid with the appropriate settings, users can perform inline editing or open the related records for full editing. This meets the requirement to "allow users to edit data" from other entities, as sub-grids provide the necessary editing capabilities.

Incorrect Options:

Edit Data Options:
Add a mobile form: This creates a form optimized for mobile devices but doesn't specifically address displaying or editing data from other entities on the main form.

Add a quick create form: This enables quick record creation using a simplified form, but it doesn't embed data from other entities on the main form or allow editing of existing related data.

Add a virtual entity: Virtual entities display data from external sources without replication, but they don't specifically address embedding information from other entities on forms or enabling editing.

View Data Options:

Add a reference panel: While reference panels can display related information, they are typically used in specific scenarios like knowledge base search and may not provide the same level of integration as quick view forms for displaying related entity data.

Reference

Microsoft Learn: Create and edit quick view forms

Microsoft Learn: Configure a sub-grid on a form

Microsoft Learn: Design model-driven app forms for Dynamics 365 Customer Service

Explanation
This question tests your knowledge of Power Virtual Agents chatbot sharing and deployment options. Different access scenarios require different sharing methods based on user licensing, permissions needed, and deployment targets. Understanding the distinction between testing access (unlicensed users), co-authoring access (licensed editors), and public deployment is essential for the PL-200 exam.

Correct Answers:

Requirement 1: Test the chatbot with unlicensed internal users

Method: Use the demo website
The Power Virtual Agents demo website allows anyone with the link to test the chatbot without requiring a license. This is specifically designed for testing with unlicensed users, making it the perfect choice for this requirement. The demo website provides a safe testing environment that doesn't consume capacity or require user licenses.

Requirement 2: Allow other licensed internal users to edit the chatbot

Method: Share the chatbot to a security group containing all users
For users who need to edit (co-author) the chatbot, they must have appropriate Power Virtual Agents licenses. Sharing to a security group is the most efficient method when multiple users need the same access level. This allows administrators to manage access through group membership rather than individually sharing with each user.

Requirement 3: Deploy the chatbot to production for public consumption

Method: Embed the chatbot code in an IFrame on your company's public website
For public-facing production deployment where external users (customers) will interact with the chatbot, embedding the chatbot in an IFrame on the public website is the standard approach. Power Virtual Agents provides generated code snippets that can be embedded on any website, allowing unlimited public users to interact with the chatbot without requiring individual licenses.

Incorrect Options:

For Requirement 1 (Testing with unlicensed internal users):
Share to each user individually: This would assign licenses unnecessarily and is inefficient

Share to security group: This would assign licenses to all group members, which isn't needed for testing

For Requirement 2 (Licensed editors):
Share to each user individually: While possible, this is less efficient than using a security group

Deploy to Microsoft Teams: This is for deployment, not for granting edit permissions

For Requirement 3 (Public production deployment):
Deploy to Microsoft Teams: This limits access to Teams users only, not the general public

Deploy to AppSource: This is for publishing apps to Microsoft commercial marketplace, not for embedding on public websites

Reference

Microsoft Learn: Share chatbots in Power Virtual Agents

Microsoft Learn: Deploy chatbots to websites

Microsoft Learn: Manage chatbot access and security in Power Virtual Agents