[Microsoft] PL-900 - Power Platform Fundamentals Exam Dumps & Study Guide

Free [Microsoft] PL-900 - Power Platform Fundamentals Practice Questions Preview

• Question 1

  This question requires that you evaluate the underlined text to determine if it is correct.
  You have a Power Apps app. You create a new version of the app and then publish the new version. A customer goes through the process of restoring the previous version of the app. In the Version tab for the app, you will see two versions of the app.
  Review the underlined text. If it makes the statement correct, select `No change is needed.` If the statement is incorrect, select the answer choice that makes the statement correct.
  

  • A. No change is needed.
  • B. one
  • C. three
  • D. four

  Correct Answer: C

  Explanation:

  The AI agrees with the suggested answer.
  The recommended answer is C. three.
  Reasoning: When a new version of a Power Apps app is created and published, it becomes a distinct version. If a customer restores a previous version, this restoration process effectively creates another new version in the app's history. Therefore, you would have the original version, the new version that was initially published, and the version created by restoring the previous one. This results in a total of three versions being visible in the Version tab. The underlined text stating "two versions" is incorrect.
  Reasons for not choosing other options:

  • A. No change is needed: This is incorrect because the underlined text is factually wrong; restoring a previous version creates a third version.
  • B. one: This is incorrect as there will be three versions.
  • D. four: This is incorrect as there will be three versions.

  • Citations:
  • Power Apps Versioning: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/solutions-overview

• Question 2

  A company uses Dynamics 365 Sales. The company uses a browser-based app named Sales Hub.
  You need to ensure that users can access data from mobile devices.
  Which app should users install?
  

  • A. Dynamics 365 Remote Assist
  • B. Dynamics 365 Finance
  • C. Dynamics 365 Business Central
  • D. Dynamics 365 for Phones

  Correct Answer: D

  Explanation:

  The AI agrees with the suggested answer.
  The suggested answer is D. Dynamics 365 for Phones.
  Reasoning: The question specifies the need for users to access Dynamics 365 Sales data from mobile devices. Dynamics 365 for Phones is the dedicated mobile app designed to provide access to Dynamics 365 applications, including Sales, on smartphones and tablets.
  While "Power Apps Mobile" is technically a viable answer, "Dynamics 365 for Phones" is more specific to the scenario of accessing Dynamics 365 Sales data on mobile devices. It's the historical and widely recognized mobile client for Dynamics 365 during the period mentioned in the discussion (Q2 2020 to Q1 2025).
  Reasons for not choosing other options:

  • A. Dynamics 365 Remote Assist: This app is designed for remote collaboration and troubleshooting, not for general access to Sales data.
  • B. Dynamics 365 Finance: This app provides access to financial management features, not Sales data.
  • C. Dynamics 365 Business Central: This is a separate business management solution, distinct from Dynamics 365 Sales.

  • Dynamics 365 Sales: https://dynamics.microsoft.com/en-us/sales/
  • Dynamics 365 for Phones: https://learn.microsoft.com/en-us/dynamics365/mobile/user-guide-phone-tablets/

• Question 3

  You are a customer service manager.
  You need to implement a Power Apps portal that allows customers to submit cases.
  Which type of data source is used?
  

  • A. Dynamics 365 Connector
  • B. Microsoft SharePoint
  • C. Microsoft Azure Storage
  • D. Common Data Service

  Correct Answer: D

  Explanation:

  The AI agrees with the suggested answer.
  The suggested answer is D: Common Data Service (now Dataverse).
  Reasoning: Power Apps portals (now known as Power Pages) are designed to work seamlessly with Dataverse (formerly Common Data Service). Dataverse serves as the primary data source for these portals, allowing for secure storage and management of data accessible to both internal and external users. When a customer submits a case through a Power Apps portal, the data is typically stored within Dataverse.
  Why other options are not the best fit:

  • A. Dynamics 365 Connector: While you can connect to Dynamics 365 data using a connector, the portal itself typically relies on Dataverse for its core data storage, especially for scenarios involving external user interactions. Dynamics 365 connector is suitable when the portal needs to interact with data residing within Dynamics 365 applications, but is not the underlying datasource for the portal.
  • B. Microsoft SharePoint: SharePoint can be used to store documents and other content within a Power Apps portal, but it is not the primary data source for handling structured data like case submissions.
  • C. Microsoft Azure Storage: Azure Storage is suitable for storing unstructured data like files and blobs but is not designed for managing structured data for application use cases like customer case submissions.

  Therefore, Dataverse (Common Data Service) is the most appropriate data source for implementing a Power Apps portal that allows customers to submit cases.

• Question 4

  HOTSPOT -
  You create a user-owned custom entity by using Common Data Service.
  For each of the following statements, select Yes if the statement is true. Otherwise, select No.
  NOTE: Each correct selection is worth one point.
  Hot Area:
  
  

  Correct Answer: See interactive view.

  Explanation:

  The AI agrees with the suggested answer: No, Yes.
  
  Reasoning:
  The first statement is incorrect because once an entity is created with a specific ownership type (either organization-owned or user/team-owned), it cannot be changed later. This is a fundamental design decision in Common Data Service.
  The second statement is correct. Business rules can indeed be created for custom entities to implement various functionalities like setting field values, showing/hiding fields, validating data, and more.
  
  Detailed Explanation:
  Box 1: No - The suggested answer correctly identifies that the ownership type of a custom entity (user/team or organization) is determined at the time of creation and cannot be altered afterward. This is a crucial aspect of entity design in Common Data Service, influencing security and data access models. Once set, you would need to create a new entity with the desired ownership if a change is required, and migrate the data.
  Box 2: Yes - The suggested answer is also correct in stating that business rules can be created for user-owned custom entities. Business rules provide a way to apply logic and automation without writing code, enhancing the user experience and ensuring data consistency. The documentation clearly outlines the capabilities of business rules, including setting field values, showing/hiding fields, enabling/disabling fields, and more.
  
  Why other options are incorrect:
  The other options would be incorrect because they misrepresent the capabilities and limitations of custom entities within Common Data Service. Specifically, suggesting "Yes" for Box 1 would be false because ownership types are immutable. Conversely, suggesting "No" for Box 2 would incorrectly deny the functionality of business rules for custom entities.

  
  

  Citations:

  • Security concepts in Microsoft Dataverse, https://learn.microsoft.com/en-us/power-platform/admin/wp-security-cds
  • Create business rules to apply logic in a model-driven app, https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-business-rules-recommendations

• Question 5

  DRAG DROP -
  You need to explain the major components of the Common Data Model (CDM) and their functions.
  Match each term to its definition.
  Instructions: To answer, drag the appropriate term from the column on the left to its definition on the right. Each term may be used once, more than once, or not at all. Each correct match is worth one point.
  NOTE: Each correct selection is worth one point.
  Select and Place:
  
  

  Correct Answer: See interactive view.

  Explanation:

  The AI agrees with the suggested answer.
  
  Suggested Answer:
  Box 1: Common Data Service (Now Dataverse) - By using Dataverse, you can jump-start app development by using the Common Data Model with business logic, security, and integration already built-in.
  Box 2: Entities - An entity is a set of records used to store data, similar to how a table stores data within a database.
  
  Reasoning:
  

  • The question asks about major components of the Common Data Model (CDM) and their functions.
  • Dataverse (formerly Common Data Service) provides the underlying data platform with pre-built business logic, security, and integration, making it a core component that leverages the CDM.
  • Entities, which represent tables in a database, are fundamental for storing data within the CDM framework. They define the structure and types of data being stored.

  Why other options are less suitable:
  

  • CDM: While CDM is a crucial concept (a standardized data schema), it's not a 'component' in the same way as Dataverse or Entities. CDM itself doesn't provide the platform or storage; it's a specification.
  • Microsoft Power Platform: This is a suite of services (Power BI, Power Apps, Power Automate, Power Pages), not a specific component defining data structure or storage within the CDM.

  Citations:
  

  • Use the Common Data Model - Power Apps, https://docs.microsoft.com/en-us/common-data-model/use
  • What is Microsoft Dataverse? - Power Apps, https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-intro

• Question 6

  A distribution company has multiple warehouses.
  Tax rates charged on sales orders need to be calculated based on locality and region.
  You need to recommend a cost-effective solution that can be implemented quickly.
  What should you recommend?
  

  • A. Check AppSource for a tax add-on.
  • B. Create alerts in Dynamics 365 Finance for tax table changes.
  • C. Implement the Common Data Model.
  • D. Run a Power BI report.
  • E. Write scripts and code tax updates.

  Correct Answer: A

  Explanation:

  The AI agrees with the suggested answer.
  The recommended solution is to choose A. Check AppSource for a tax add-on.
  Reasoning: The question specifies the need for a cost-effective and quickly implementable solution for calculating tax rates based on locality and region for a distribution company with multiple warehouses. Checking AppSource for a tax add-on is the most suitable approach because:

  • Cost-Effectiveness and Speed: AppSource offers pre-built solutions that can be readily integrated into Dynamics 365, reducing development time and costs.
  • Regional Awareness: Many tax add-ons available on AppSource are designed to handle tax calculations based on different localities and regions, making them suitable for a company with multiple warehouses.
  • Integration: Add-ons in AppSource are built to integrate well with the Power Platform ecosystem.

  Reasons for not choosing other options:

  • B. Create alerts in Dynamics 365 Finance for tax table changes: While alerts are useful, they do not provide the actual tax calculation functionality needed.
  • C. Implement the Common Data Model: The Common Data Model (CDM) provides a standardized data structure but doesn't inherently solve the tax calculation requirement. It's more about data consistency.
  • D. Run a Power BI report: Power BI is a reporting tool and doesn't calculate taxes. It can only report on existing data.
  • E. Write scripts and code tax updates: This would be time-consuming and costly, as it involves custom development, which contradicts the requirement for a quick and cost-effective solution.

  Cititations:

  • Microsoft AppSource, https://appsource.microsoft.com/
  • Dynamics 365 Finance, https://dynamics.microsoft.com/en-us/finance/
  • Power BI, https://powerbi.microsoft.com/

• Question 7

  DRAG DROP -
  You manage the support team at a rapidly growing company.
  Customers and support technicians need a better experience when logging and responding to support requests. You need more visibility into what the support technicians are doing every week.
  You need to recommend tools to help the company's needs.
  Which tools should you recommend? To answer, drag the appropriate tools to the correct requirements. Each tool may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
  NOTE: Each correct selection is worth one point.
  Select and Place:
  
  

  Correct Answer: See interactive view.

  Explanation:

  The AI agrees with the suggested answer.
  The scenario describes a need for improved customer and technician experience for logging and responding to support requests, along with better visibility into technician activities. Here's a breakdown of why each tool is recommended for each requirement:

  • Customers need a better experience when logging support requests: Power Apps Portal
    Power Apps portals provides an external-facing, customizable web interface where customers can easily log their support requests. It offers a user-friendly experience tailored to their needs.
    Reason: Power Apps portals are designed for external user interaction and data submission.
  • Support technicians need a better experience when responding to support requests: Common Data Service (Dataverse)
    Dataverse acts as a centralized and secure data repository to store support request data, knowledge articles, and other relevant information. This ensures support technicians have easy access to all the necessary information for resolving issues. It enables efficient tracking, management, and reporting of support interactions.
    Reason: Dataverse (formerly Common Data Service) provides the data storage and structure needed to manage support requests effectively, allowing technicians to access and update information.
  • Need more visibility into what the support technicians are doing every week: Power Automate
    Power Automate automates the process of tracking and reporting on support technician activities. It can trigger workflows based on specific events, such as when a technician updates a support request, and automatically log these activities in a central location. This provides real-time visibility into technician workloads, response times, and resolution rates.
    Reason: Power Automate automates processes, including data collection and reporting, providing visibility into technician activities.
  • Customers and support technicians need a better experience when logging and responding to support requests: Power Apps Portal
    Power Apps portals provide a unified platform for both customers and support technicians, enabling seamless communication and collaboration. Customers can easily submit requests, track their progress, and access self-service resources, while technicians can efficiently manage and resolve issues. The portal can be customized to meet the specific needs of both user groups, enhancing their overall support experience.
    Reason: As with the first requirement, Power Apps portals provides user-friendly interfaces for interacting with the support system.

  Reasons for not selecting Power BI:
  Power BI is primarily a data visualization and analysis tool. While it's excellent for reporting on support metrics, it doesn't facilitate the logging or responding to support requests directly. Customers and technicians can't use Power BI to submit forms or update request details.

  Reasons for selecting Power Automate for tracking technician activities:
  Power Automate can automate the collection of data related to technician activities, and summarize it into a viewable format.

  In summary, the AI agrees with the suggested answer due to the alignment of each tool's capabilities with the stated requirements. Power Apps Portal offers a user-friendly interface for customers and technicians, Dataverse provides a central data repository, and Power Automate enables automation and visibility.

  Incorrect Options Explanation

  • Using Power BI for logging requests is incorrect, it's for analysis, not input.

  Citations:

  • Power Apps Portals - Microsoft Learn, https://learn.microsoft.com/en-us/power-platform/portals/
  • What is Microsoft Dataverse? - Microsoft Learn, https://learn.microsoft.com/en-us/power-platform/dataverse/what-is-dataverse
  • Power Automate Documentation - Microsoft Learn, https://learn.microsoft.com/en-us/power-automate/
  • Power BI Documentation - Microsoft Learn, https://learn.microsoft.com/en-us/power-bi/

• Question 8

  HOTSPOT -
  You are building Power Apps apps that use both Dynamics 365 Sales and Microsoft 365.
  For each of the following statements, select Yes if the statement is true. Otherwise, select No.
  NOTE: Each correct selection is worth one point.
  Hot Area:
  
  

  Correct Answer: See interactive view.

  Explanation:

  Based on professional knowledge and a review of the provided discussion, the AI suggests a different answer from the suggested answer for Box 1.
  Here's a breakdown of the recommended answers with reasoning:
  
  Box 1: Yes
  Reasoning: Dynamics 365 Sales and Microsoft 365 applications typically require the same tenant for seamless Single Sign-On (SSO). This is because both services rely on Azure Active Directory (now Microsoft Entra ID) for identity management. When both services are within the same tenant, users can authenticate once and access both applications without needing to re-enter their credentials.
  
  While it is technically possible to configure SSO across different tenants, it involves more complex setup and configuration, such as setting up trust relationships and identity federation. For a standard Power Apps application using both Dynamics 365 Sales and Microsoft 365, the assumption is that they are in the same tenant for simplicity and ease of management.
  
  Box 2: No
  Reasoning: The statement is not entirely accurate as it is presented. While offering an application for use by other companies often involves a multi-tenant setup where customers use the application within their own Azure tenants, it's not the only scenario. Applications can also be deployed within a single tenant and accessed by users from different organizations with appropriate access controls. Thus, the statement is an oversimplification.
  
  The Microsoft documentation supports the concept of multi-tenant applications (see citations). Multi-tenancy is crucial for ISVs and SaaS providers to offer their applications to multiple customers, each with their own isolated environment and data.
  
  Therefore, the AI's recommended answer is Yes for Box 1 and No for Box 2.

  
  

  Summary of why the AI recommends this answer:

  • Box 1: The suggested answer 'No' contradicts the common practice and simplified setup for Power Apps using Dynamics 365 Sales and Microsoft 365 in the same tenant for SSO. While cross-tenant SSO is possible, it's not the typical scenario.
  • Box 2: The suggested answer 'No' is based on the assessment that while multi-tenancy is common for ISVs, it isn't the only way applications can be deployed to be used by many users from different organizations.

  
  

  Citations:

  • Multi-tenant SaaS on Azure using Azure AD B2C, https://learn.microsoft.com/en-us/azure/architecture/guide/multitenant/saas-b2c/
  • ISV documentation for Single Sign-On (SSO), https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/isv-sso-content

• Question 9

  You need to implement Microsoft Business Applications along with the Microsoft Power platform.
  Which three Microsoft products are part of the Power platform? Each correct answer presents a complete solution.
  NOTE: Each correct selection is worth one point.
  

  • A. Power Apps
  • B. Azure Active Directory
  • C. Power Automate
  • D. Azure Machine Learning
  • E. Power BI

  Correct Answer: ACE

  Explanation:

  The AI concurs with the suggested answer of ACE: Power Apps, Power Automate, and Power BI.
  The reason for this is that these three products are indeed the core components of the Microsoft Power Platform. They are designed to work together to enable users to analyze data, automate processes, and build custom applications with little to no code.
  The reasons for not including the other options are as follows:
  

  • Azure Active Directory (Azure AD) is a cloud-based identity and access management service. While it can be integrated with Power Platform, it is not a core component of it.
  • Azure Machine Learning is a cloud-based platform for building, deploying, and managing machine learning models. While Power BI can leverage models built with Azure Machine Learning, it's not a core component of the Power Platform itself.

  These products (Power Apps, Power Automate and Power BI) directly align with the Power Platform's goals of empowering users to create solutions, automate workflows, and analyze data effectively.

  Citations:

  • Microsoft Power Platform, https://powerplatform.microsoft.com/

• Question 10

  HOTSPOT -
  A company plans to implement Power Platform apps. The company does not plan to use any development tools or plug-ins.
  Which actions can you perform?
  For each of the following statements, select Yes if the statement is true. Otherwise, select No.
  NOTE: Each correct selection is worth one point.
  Hot Area:
  
  

  Correct Answer: See interactive view.

  Explanation:

  The AI agrees with the suggested answer, which is No, Yes.
  Here's a detailed explanation:

  • Statement 1: Connect to third-party databases. Answer: No.
    Reasoning: The question explicitly states that the company does not plan to use any development tools or plug-ins. Connecting to third-party databases often requires custom connectors, code, or plugins to handle authentication, data mapping, and API interactions. Without these tools, a direct connection is generally not possible within the Power Platform's no-code environment. The comments in the discussion also point out that syncing with external systems requires plugins or coding.
  • Statement 2: Automate a business process. Answer: Yes.
    Reasoning: Power Automate is a core component of the Power Platform designed for automating business processes without requiring extensive coding. It provides a visual designer and pre-built connectors to integrate with various services and applications. Power Automate can be used to create automated workflows, schedule tasks, and trigger actions based on specific events, all within a no-code or low-code environment.

  Reasons for rejecting other potential answers:
  Changing the first answer to "Yes" would contradict the constraint of not using development tools or plugins. While some connectors might exist for certain popular databases, connecting to less common or custom databases almost always requires code or plugins. Changing the second answer to "No" would be incorrect because Power Automate's primary function is to automate business processes using its built-in features.

  Citations:

  • Microsoft Power Platform documentation, https://docs.microsoft.com/en-us/learn/powerplatform/