Microsoft PL-900 Power Platform Fundamentals Exam Dumps and Practice Test Questions Set 12 Q166 — 180
Visit here for our full Microsoft PL-900 exam dumps and practice test questions.
Question 166
A company wants to automate the process of creating a new folder in OneDrive and sending a notification email whenever a new employee is added to their HR system. Which Power Platform component should be used?
A) Power Apps
B) Power Automate
C) Power BI
D) Power Virtual Agents
Answer: B
Explanation:
Power Automate is the appropriate component for automating the process of creating folders and sending notifications based on triggers from the HR system. Power Automate is designed specifically for workflow automation and orchestrating multi-step processes across different applications and services. It enables users to create automated workflows that respond to events, perform actions across multiple systems, and ensure consistent execution of business processes without manual intervention.
In this scenario, Power Automate can be configured with a trigger that monitors the HR system for new employee additions. When a new employee record is detected, the flow automatically executes a series of actions including creating a new folder in OneDrive with appropriate naming conventions and permissions, then sending a notification email to relevant stakeholders such as the IT department, manager, or the new employee themselves. Power Automate provides pre-built connectors for both OneDrive and email systems like Outlook, making it straightforward to implement this automation without custom coding. The flow can also include conditional logic, error handling, and integration with additional systems if needed for more complex onboarding workflows.
Power Apps is designed for building user interfaces and custom applications where users interact directly with data, not for background automation processes. Power BI focuses on data visualization and analytics, not process automation. Power Virtual Agents creates conversational chatbots and would not be suitable for automated backend processes like folder creation. While these components could be part of a larger solution, Power Automate is specifically designed for and best suited to the automation workflow described in this scenario.
Question 167
What is the primary purpose of AI Builder in Power Platform?
A) To replace all manual data entry processes
B) To add artificial intelligence capabilities to apps and flows without requiring data science expertise
C) To create virtual machines for running applications
D) To design user interfaces for mobile apps
Answer: B
Explanation:
The primary purpose of AI Builder is to add artificial intelligence capabilities to apps and flows without requiring data science expertise. AI Builder is a low-code AI capability within Power Platform that enables users to incorporate intelligent features into their Power Apps and Power Automate workflows. It provides pre-built AI models for common scenarios as well as the ability to create custom AI models using a guided interface that does not require programming or data science knowledge.
AI Builder offers several types of AI models including form processing to extract information from documents, object detection to identify items in images, prediction models to forecast outcomes based on historical data, text recognition for extracting text from images, sentiment analysis to understand customer feedback, and business card reading to capture contact information. Users can train custom models using their own data through a simple interface that guides them through the process of providing training data, configuring the model, and testing results. Once trained, these AI models can be embedded directly into Power Apps to provide intelligent features or used in Power Automate flows to make decisions and process information automatically.
AI Builder does not replace all manual data entry but can assist with specific data extraction tasks. It does not create virtual machines or infrastructure resources, as it operates as a service within Power Platform. While AI Builder can enhance user experiences in apps, it is not primarily focused on user interface design but rather on adding intelligent capabilities like prediction, recognition, and understanding. The key value of AI Builder is democratizing AI by making advanced capabilities accessible to business users and citizen developers without requiring specialized technical skills.
Question 168
A model-driven app in Power Apps automatically generates forms and views based on which of the following?
A) Custom JavaScript code written by developers
B) The data model and relationships defined in Dataverse
C) Pre-designed templates from the Power Apps gallery
D) User preferences and browsing history
Answer: B
Explanation:
Model-driven apps automatically generate forms and views based on the data model and relationships defined in Dataverse. This approach is fundamentally different from canvas apps where developers manually design every screen. In model-driven apps, the structure and appearance of the user interface are derived from the metadata that defines tables, columns, relationships, and business logic in the underlying Dataverse database. This metadata-driven approach ensures consistency, reduces development time, and automatically applies best practices for data entry and display.
When creating a model-driven app, developers first define their data model in Dataverse including tables for entities like customers, orders, or products, the columns within those tables, and the relationships between tables such as one-to-many or many-to-many associations. Based on this data model, Power Apps automatically generates appropriate forms for creating and editing records, views for displaying lists of records with filtering and sorting capabilities, and navigation structures that reflect the relationships between different entities. Developers can customize these generated components by modifying form layouts, adding or removing fields, creating custom views, and configuring business rules, but the foundation is automatically created from the data model.
Model-driven apps do not require or rely on custom JavaScript code for basic functionality, though JavaScript can be added for advanced customizations. They are not based on pre-designed templates from galleries, though solution templates may include pre-configured data models. User preferences and browsing history do not determine the structure of model-driven apps. The key principle is that the data model defined in Dataverse drives the user interface, enabling rapid development of consistent, data-centric applications.
Question 169
Which type of Power Automate flow is best suited for automating repetitive desktop application tasks such as data entry into legacy systems?
A) Cloud flows
B) Desktop flows
C) Business process flows
D) Scheduled flows
Answer: B
Explanation:
Desktop flows are best suited for automating repetitive desktop application tasks such as data entry into legacy systems. Desktop flows, also known as robotic process automation or RPA, enable users to record and automate interactions with desktop applications, web applications, and legacy systems that may not have APIs or modern integration capabilities. This technology allows organizations to automate tasks that previously required manual human interaction with user interfaces.
Desktop flows work by recording user actions such as mouse clicks, keyboard inputs, and navigation through application screens, then playing back those actions automatically. This is particularly valuable for legacy systems that lack modern APIs or connectors, making traditional integration approaches difficult or impossible. For data entry scenarios, desktop flows can automatically open applications, navigate to appropriate screens, fill in forms, submit data, and handle responses. They can also extract data from applications by reading screen elements, enabling information transfer between systems that cannot communicate directly. Desktop flows can run attended, where they assist users by automating portions of their work, or unattended, where they run completely automatically on dedicated machines or virtual machines.
Cloud flows connect to cloud services and applications through APIs and connectors but cannot directly interact with desktop applications or legacy systems without APIs. Business process flows provide guided experiences that lead users through defined stages but do not automate the actual data entry. Scheduled flows run at predetermined times but the designation refers to the trigger mechanism rather than the type of automation capability. Desktop flows specifically address the need to automate interactions with desktop and legacy applications.
Question 170
An organization needs to ensure that certain business logic executes consistently regardless of how data is entered into Dataverse. Which feature should they use?
A) Canvas app formulas
B) Power BI calculations
C) Business rules or Power Automate cloud flows
D) AI Builder models
Answer: C
Explanation:
Business rules or Power Automate cloud flows should be used to ensure that business logic executes consistently regardless of how data is entered into Dataverse. These server-side mechanisms execute within Dataverse itself rather than in specific client applications, ensuring that the logic applies universally whether data is created or modified through Power Apps, Power Automate, API calls, integrations, or other means. This consistency is essential for maintaining data integrity and enforcing business policies across the organization.
Business rules in Dataverse provide a simple way to implement common logic such as setting field values, showing or hiding fields, validating data, and displaying messages. They are defined at the table level and automatically execute whenever records are created or updated, regardless of the entry point. For more complex scenarios, Power Automate cloud flows can be triggered by Dataverse events and execute sophisticated multi-step logic, call external services, perform calculations, and update related records. Both approaches ensure centralized enforcement of business logic rather than relying on individual applications to implement the same rules, which could lead to inconsistencies if logic differs across apps or if rules are not implemented in all entry points.
Canvas app formulas execute only within specific Power Apps canvas applications and do not affect data entered through other means. Power BI calculations are used for analytical purposes in reports and dashboards, not for enforcing business logic during data entry. AI Builder models provide intelligent capabilities like prediction and recognition but are not designed for enforcing standard business rules consistently. Business rules and cloud flows operating at the Dataverse level are the appropriate tools for ensuring consistent business logic execution across all data entry methods.
Question 171
What is the maximum number of API calls per day allowed in the standard Power Automate per user license?
A) 5,000 API calls
B) 10,000 API calls
C) 40,000 API calls
D) Unlimited API calls
Answer: C
Explanation:
The standard Power Automate per user license allows 40,000 API calls per day. API calls represent the requests made by flows to connectors and services during execution. Each action in a flow that interacts with a connector typically counts as one API call, though some actions may result in multiple calls. Understanding API call limits is important for planning and designing flows, especially for high-volume automation scenarios, to ensure solutions remain within license entitlements and avoid throttling or service interruptions.
The 40,000 API calls per day limit applies per user and is calculated as a rolling 24-hour period. This allocation is designed to support typical business automation needs for individual users running multiple flows throughout the day. Organizations with higher-volume requirements can use additional licensing options such as Power Automate per flow licenses which provide 15,000 API calls per day per flow, or capacity add-ons that provide pools of additional API calls that can be shared across the organization. Monitoring API call usage is possible through the Power Platform admin center, allowing administrators to track consumption and identify flows that may be approaching limits.
Lower limits like 5,000 or 10,000 calls per day would be insufficient for many business automation scenarios involving frequent data synchronization or high-volume processing. While some older or trial plans may have had different limits, the current standard is 40,000 for per user licenses. Unlimited API calls are not provided in standard licenses as they could lead to resource abuse and would not allow Microsoft to manage service capacity effectively. Understanding these limits helps organizations choose appropriate licensing and design efficient flows that optimize API call usage.
Question 172
Which component of Power Platform allows users to create external-facing websites that anonymous users can access without requiring a license?
A) Power Apps canvas apps
B) Power Apps model-driven apps
C) Power Pages
D) Power BI reports
Answer: C
Explanation:
Power Pages allows users to create external-facing websites that anonymous users can access without requiring individual licenses. Power Pages is specifically designed for building public websites, customer portals, partner portals, and community sites where external users who are not part of the organization need access. Unlike Power Apps which typically require users to have Power Apps licenses, Power Pages websites can be accessed by unlimited anonymous users or authenticated external users based on the Power Pages subscription rather than per-user licensing.
Power Pages provides capabilities for creating professional websites with features including content management, form submission, user authentication and registration for scenarios requiring user accounts, knowledge bases, case management for customer support scenarios, and integration with Dataverse for data storage. The platform is optimized for external access with features like public web pages that require no authentication, self-service registration for users who need accounts, and granular permissions for authenticated users. This makes Power Pages ideal for scenarios like corporate websites, product catalogs, customer self-service portals, community forums, and event registration sites where the audience includes people outside the organization.
Power Apps canvas apps and model-driven apps are designed primarily for internal business applications and require users to have appropriate Power Apps licenses. While these apps can technically be shared with external users, this approach requires licensing for each external user and is not optimized for public access scenarios. Power BI reports can be embedded in websites or shared publicly with limitations, but Power BI is focused on data visualization rather than comprehensive website creation. Power Pages is the purpose-built solution for external-facing websites with public or authenticated external user access.
Question 173
A Power Apps canvas app uses a collection to store data temporarily during the user session. What happens to this data when the user closes the app?
A) The data is automatically saved to Dataverse
B) The data is permanently deleted and cannot be recovered
C) The data is saved to the user’s OneDrive
D) The data is emailed to the app creator
Answer: B
Explanation:
When a user closes a Power Apps canvas app, data stored in collections is permanently deleted and cannot be recovered. Collections in Power Apps are temporary, in-memory data structures that exist only during the current app session. They provide a way to store and manipulate data locally within the app while it is running, but they are not persistent storage mechanisms. Collections are useful for scenarios like temporarily holding data fetched from a data source, storing calculation results, maintaining state during complex operations, or buffering data before committing it to a permanent data source.
Since collections are session-based and stored in the device’s memory while the app runs, they are automatically cleared when the app is closed, the browser tab is closed, or the session ends. This behavior is by design and ensures that sensitive data does not persist on devices after users finish using the app. If data needs to be preserved beyond the current session, developers must explicitly save it to a permanent data source such as Dataverse, SharePoint, SQL Server, or another connected data service using the Patch, SubmitForm, or similar functions before the user exits the app.
Collections do not automatically save to any data source including Dataverse, OneDrive, or any other storage location. The app creator is not notified or sent the data when users close the app. If persistent storage is required, developers must design the app to write data to appropriate data sources at the right times during the user workflow. Understanding the temporary nature of collections is important for properly designing data handling in canvas apps and ensuring that important information is not lost when sessions end.
Question 174
Which Power Platform component provides pre-built industry-specific templates and accelerators for common business scenarios?
A) Power Platform Center of Excellence toolkit
B) AppSource
C) Power Platform admin center
D) Dataverse
Answer: B
Explanation:
AppSource provides pre-built industry-specific templates and accelerators for common business scenarios. AppSource is Microsoft’s marketplace for business applications, add-ins, and solutions built on Microsoft technologies including Power Platform. It offers a wide variety of ready-made solutions including complete apps, templates, connectors, and sample solutions that organizations can use as starting points for their own implementations or deploy directly to address specific business needs.
In AppSource, users can find solutions across various categories and industries including sales, customer service, field service, project management, human resources, finance, and many others. These solutions range from simple template apps that can be customized to comprehensive applications built by Microsoft partners. For Power Platform specifically, AppSource includes Power Apps templates, Power BI template apps with pre-built dashboards and reports, Power Automate templates for common workflows, and complete solutions that combine multiple components. Many of these are industry-specific, addressing needs unique to healthcare, manufacturing, retail, financial services, and other sectors. Organizations can browse AppSource, preview solutions, and install them into their environments to accelerate development and leverage best practices.
The Power Platform Center of Excellence toolkit is a set of tools and guidance for governance and administration, not pre-built business solutions. The Power Platform admin center is used for managing environments, users, and policies, not for accessing templates. Dataverse is the data platform for storing application data, not a marketplace for solutions. AppSource serves as the central repository where users discover and acquire pre-built solutions and templates that can accelerate their Power Platform initiatives.
Question 175
An organization wants to track the stages of a sales process from lead qualification through deal closure. Which Power Platform feature is specifically designed for this purpose?
A) Canvas app with custom screens
B) Power Automate cloud flow
C) Business process flow
D) Power BI dashboard
Answer: C
Explanation:
Business process flow is specifically designed for tracking and guiding users through the stages of a sales process from lead qualification through deal closure. Business process flows provide a guided experience that leads users through defined stages of a business process, ensuring consistency, improving adoption of best practices, and providing visibility into where opportunities or cases are in their lifecycle. They overlay on top of model-driven apps and Dataverse tables, creating a streamlined path that users follow as they work with records.
A business process flow for sales would typically include stages such as qualify lead, develop opportunity, propose solution, negotiate terms, and close deal. Each stage can contain specific steps that guide users to complete required activities, enter necessary information, or meet certain criteria before advancing to the next stage. Business process flows can span multiple tables, allowing a process to transition from lead records to opportunity records as the sales cycle progresses. They provide visual indicators of progress, prevent users from skipping important steps, and can include branching logic to handle different scenarios. Managers gain visibility into process adherence and can identify bottlenecks by seeing how many opportunities are in each stage.
A canvas app with custom screens could display process information but would require significant custom development and would not provide the built-in process management capabilities. Power Automate cloud flows automate actions and workflows but do not provide the guided user experience for moving through process stages. Power BI dashboards visualize data and metrics but do not guide users through operational processes. Business process flows are purpose-built for creating structured, stage-based processes that guide users and ensure consistency in how business processes are executed.
Question 176
What is the primary advantage of using environment variables in Power Platform solutions?
A) They increase application performance
B) They allow configuration values to be changed without modifying the solution code
C) They reduce the number of connectors needed
D) They automatically backup application data
Answer: B
Explanation:
The primary advantage of using environment variables is that they allow configuration values to be changed without modifying the solution code. Environment variables are configurable parameters that can be defined once and referenced throughout solutions including Power Apps, Power Automate flows, and other components. They provide a way to externalize configuration settings such as URLs, email addresses, numerical thresholds, feature flags, and connection information, making solutions more flexible and easier to deploy across different environments.
Environment variables are particularly valuable when moving solutions between development, test, and production environments. Instead of hardcoding values like API endpoints or email addresses directly into apps and flows, developers reference environment variables. When the solution is deployed to a new environment, administrators can update the environment variable values to match that environment’s configuration without needing to modify or redeploy the actual solution components. This separation of configuration from implementation reduces deployment errors, simplifies maintenance, and makes solutions more reusable. Environment variables also support different data types including text, numbers, JSON, and data source references.
Environment variables do not directly impact application performance, as they are simply configuration values that are read when needed. They do not reduce the number of connectors required, as connectors are determined by which services the solution needs to integrate with. Environment variables do not provide backup functionality for application data; backups are handled through separate mechanisms. The key value of environment variables is enabling flexible configuration management and supporting application lifecycle management by decoupling configuration from implementation code.
Question 177
Which licensing option is required to use premium connectors in Power Automate?
A) Office 365 license only
B) Power Automate per user or per flow license
C) Azure subscription only
D) No additional license is required
Answer: B
Explanation:
Power Automate per user or per flow licenses are required to use premium connectors. Premium connectors provide access to more advanced services and capabilities beyond what is included in the standard connectors available with Office 365 licenses. These premium connectors enable integration with on-premises systems through data gateways, enterprise applications, specialized cloud services, and other advanced scenarios that require additional licensing due to their enhanced capabilities and value.
The per user license provides an individual user with the ability to create and run unlimited flows that use premium connectors, along with access to other advanced Power Automate features. This is appropriate when a user needs to create multiple flows or when the specific user running the flows varies. The per flow license, alternatively, licenses a specific flow to use premium connectors and can be run by unlimited users within the organization. This option is cost-effective when a single flow serves many users, such as an approval workflow used across a department. Both licensing options also provide higher API call limits and access to advanced features beyond just premium connectors.
Office 365 licenses include limited Power Automate capabilities with standard connectors only, which is sufficient for many basic automation scenarios but does not grant access to premium connectors. An Azure subscription alone does not provide Power Automate licensing, though Azure services may be accessed through Power Automate with appropriate connector licensing. Premium connectors definitely require additional licensing beyond basic Office 365 entitlements. Organizations must evaluate which connectors their solutions require and ensure appropriate licensing is in place to remain compliant and avoid service interruptions.
Question 178
A company needs to create a mobile app that allows field technicians to update work order status even without internet connectivity. Which data storage approach is most appropriate?
A) Store all data in Excel files on SharePoint
B) Use a canvas app with offline mode and Dataverse
C) Use model-driven app with real-time synchronization only
D) Store data in Power BI datasets
Answer: B
Explanation:
Using a canvas app with offline mode and Dataverse is the most appropriate approach for field technicians who need to update work orders without internet connectivity. Canvas apps support offline capabilities that allow users to continue working when disconnected from the network, with automatic synchronization when connectivity is restored. This is essential for field service scenarios where technicians often work in areas with poor or no cellular coverage such as basements, remote locations, or areas with weak signal strength.
To implement offline functionality, developers create a canvas app and enable offline mode for specific data sources, primarily Dataverse tables. The app downloads relevant data to the device when connectivity is available, allowing users to view work orders, customer information, and other necessary data while offline. Technicians can update work order status, add notes, capture photos, and record time spent on tasks, with all changes stored locally on their device. When internet connectivity is restored, the app automatically synchronizes these changes back to Dataverse, updating the central database and making information available to dispatchers, managers, and other team members. The offline feature includes conflict resolution mechanisms for handling situations where the same record was modified by multiple users.
Excel files on SharePoint do not provide robust offline synchronization capabilities and have limitations for multi-user scenarios. Model-driven apps with real-time synchronization only would not work without connectivity, as they require constant connection to function. Power BI datasets are for analytical purposes and reporting, not for operational data entry and transaction processing. The canvas app with offline mode provides the mobile-optimized, disconnected-operation capabilities needed for field service scenarios.
Question 179
What is the purpose of the Common Data Model in Power Platform?
A) To provide a standardized schema for business data across applications
B) To encrypt all data stored in Dataverse
C) To automatically generate Power Apps from Excel files
D) To compress large files for storage
Answer: A
Explanation:
The Common Data Model provides a standardized schema for business data across applications. It is a shared data language for business and analytical applications that consists of a set of standardized, extensible data schemas that Microsoft and its partners have published. The Common Data Model includes definitions for common business concepts such as account, contact, lead, opportunity, case, product, and many others, establishing consistent structures, relationships, and semantics for these entities across different applications and services.
By using the Common Data Model, organizations benefit from consistency and interoperability across their applications. When multiple applications use the same standardized schemas for common entities, data exchange becomes seamless and integration is simplified. This standardization reduces the need for custom data transformations and mappings when connecting different systems. The Common Data Model also incorporates industry-specific schemas for sectors like healthcare, financial services, and others, providing domain-specific entities and relationships that reflect common practices in those industries. Organizations can extend standard Common Data Model entities with custom fields while maintaining the base structure, allowing flexibility while preserving compatibility.
The Common Data Model does not handle data encryption, which is a security feature managed separately in Dataverse. It does not automatically generate applications from Excel files, though Power Apps provides import capabilities. The Common Data Model is not related to file compression or storage optimization. Its fundamental purpose is providing a standardized, shared understanding of business data structures that enables applications from different vendors to work together more effectively and allows organizations to build solutions that are more consistent, maintainable, and interoperable.
Question 180
Which feature in Power Automate allows flows to wait for an external event or approval before continuing execution?
A) Parallel branches
B) Delay action
C) Wait for approval or webhook trigger
D) Terminate action
Answer: C
Explanation:
Wait for approval actions or webhook-based triggers allow flows to pause execution while waiting for an external event or human decision before continuing. This capability is essential for business processes that require human intervention, external system responses, or time-sensitive decisions. The approval functionality in Power Automate enables flows to send approval requests to designated users, then pause execution until the approver responds with their decision, after which the flow continues with conditional logic based on whether the request was approved or rejected.
Approval actions support various scenarios including single approver, multiple approvers with first-to-respond logic, multiple approvers requiring all responses, or sequential approvals through multiple stages. The approval request can include detailed information, attachments, and custom response options. Approvers can respond through email, Teams, the Power Automate mobile app, or the Approvals center, providing flexibility in how users interact with approval requests. For webhook scenarios, flows can register for callbacks from external systems and pause execution until the external system sends data back, enabling integration patterns where external processing must complete before the flow continues.
Parallel branches allow flows to execute multiple actions simultaneously but do not wait for external events. Delay actions pause flow execution for a specified time period but are time-based rather than event-based and do not involve external input or decisions. Terminate actions stop flow execution entirely rather than pausing and resuming. The wait for approval and webhook capabilities specifically address scenarios where flows must pause and wait for external input, human decisions, or events from other systems before proceeding with subsequent actions.