Visit here for our full Microsoft PL-200 exam dumps and practice test questions.
Question 61:
You are creating a model-driven app view that needs to display accounts with opportunities in the current fiscal year. What type of filter should you use?
A) Static filter with date range
B) Dynamic filter with fiscal year
C) Related records filter with date condition
D) FetchXML with date functions
Answer: C) Related records filter with date condition
Explanation:
Related records filter with date condition is the correct approach for filtering a view based on criteria in related records. In this case, you’re filtering accounts based on whether they have related opportunities meeting a date criterion. You would configure the view filter to check for related opportunities where the estimated close date or created date falls within the current fiscal year. The view designer supports filtering based on related table data through relationship paths.
This filter dynamically evaluates for each account whether it has any related opportunities matching the date criteria and includes only those accounts in the view results. You can combine multiple conditions such as opportunity status and date ranges to create sophisticated filters. The fiscal year filtering can use relative date operators that automatically adjust based on the current date, ensuring the view always shows current fiscal year data without manual updates.
Static filters would require manual updates as fiscal years change. Dynamic filters with fiscal year would work but related records filter is more specific to the requirement. FetchXML could accomplish this but is more complex than necessary. For filtering parent records based on the existence of related child records meeting specific criteria like date ranges, configuring related records filters provides the view designer capability to implement cross-table filtering that keeps views dynamically current based on relationships and conditions.
Question 62:
You need to create a Power Automate flow that processes rows from an Excel file stored in SharePoint. Which actions should you use?
A) List rows present in a table and Apply to each
B) Get file content and Parse JSON
C) Excel connector with table operations
D) Import data action
Answer: A) List rows present in a table and Apply to each
Explanation:
List rows present in a table combined with Apply to each is the correct approach for processing Excel data in Power Automate flows. The Excel Online connector’s “List rows present in a table” action retrieves all rows from a specified table in an Excel file stored in SharePoint or OneDrive. This action returns an array of row objects where each row’s columns are accessible as properties. You then use Apply to each to iterate through the array and process each row individually.
This pattern allows you to perform operations on each Excel row such as creating Dataverse records, sending emails, or updating other systems. Inside the Apply to each loop, you can reference column values from the current row using dynamic content and implement conditional logic to process different rows differently. This is the standard approach for Excel integration and handles files with any number of rows efficiently.
Get file content retrieves the entire file as binary but doesn’t parse Excel structure. Parse JSON is for JSON data, not Excel. Excel connector with table operations is correct but the specific action is List rows. Import data action isn’t specific enough. For reading and processing individual rows from Excel tables in SharePoint through Power Automate, using the List rows present in a table action with Apply to each iteration provides the straightforward pattern that makes Excel data accessible for processing and integration with other systems.
Question 63:
You are configuring a calculated field that should display a different message based on an option set field value. Which formula structure should you use?
A) IF with nested conditions
B) SWITCH function
C) CASE statement
D) Multiple IF functions
Answer: A) IF with nested conditions
Explanation:
IF functions with nested conditions are the correct approach for conditional logic in Dataverse calculated fields. While some database systems have SWITCH or CASE statements, Dataverse calculated field formulas use nested IF functions to evaluate multiple conditions. The syntax would be IF(field = value1, “message1”, IF(field = value2, “message2”, IF(field = value3, “message3”, “default message”))) to check an option set value and return different text based on the selected option.
Nested IF functions allow you to create complex conditional logic evaluating multiple scenarios. Each IF function checks a condition and returns one value when true or moves to the next IF when false. The innermost value acts as the default returned when no conditions match. This approach works with option sets, two-option fields, or any other field types, comparing values and returning appropriate results for calculated field display.
SWITCH and CASE are not available functions in Dataverse calculated fields. Multiple separate IF functions would need to be combined through nesting to handle multiple conditions. For implementing multi-condition logic that returns different values based on option set selections or other field values in calculated field formulas, using nested IF functions provides the conditional logic structure that evaluates multiple scenarios and returns appropriate values based on which conditions are met.
Question 64:
Your organization uses business process flows with branching. You need to ensure specific stages appear only when an opportunity value exceeds 100,000 dollars. What should you configure?
A) Stage conditions
B) Branch rules
C) Conditional stages
D) Workflow rules
Answer: C) Conditional stages
Explanation:
Conditional stages are the correct feature for creating branches in business process flows that appear based on specific rules. Business process flows (BPFs) guide users through a series of stages to complete a business process in a structured and consistent manner. However, not all stages are relevant for every record, and this is where conditional stages provide flexibility. By configuring conditional branching in the BPF designer, you can create stages that only appear when predefined conditions are met, ensuring that users are presented with a tailored workflow that adapts to each record’s data. For example, in an opportunity management process, you might create a branch where certain stages only appear when the estimated opportunity value exceeds $100,000. Opportunities below that threshold would skip those stages entirely, simplifying the process for users and focusing attention on the most relevant steps.
Conditional stages help reduce process clutter and prevent users from seeing unnecessary stages that do not apply to their scenario. Branch conditions can be defined using field values, option set selections, two-option fields, or other attributes of the record. When a record enters the BPF, the system evaluates the conditions for each branch and determines which stages should be displayed. This ensures that each user sees a process flow customized to the record’s data, enhancing efficiency, accuracy, and compliance. For instance, high-value opportunities may require additional approval or risk assessment stages, whereas standard opportunities can follow a shorter path to closure.
It is important to distinguish conditional stages from other features. Stage conditions control the progression between stages but do not manage stage visibility; they determine whether a user can advance to the next stage based on certain criteria. “Branch rules” is not the official terminology used in BPFs, and workflow rules apply to classic workflows rather than modern business process flows. Conditional stages specifically provide branching logic that dynamically adapts the process path for each record based on evaluated conditions.
Implementing conditional stages also enhances user experience and operational efficiency. Users are guided only through the stages relevant to their specific case, reducing errors, avoiding unnecessary steps, and accelerating completion of business processes. Administrators can maintain a single BPF that handles multiple scenarios, rather than creating separate flows for each condition, which improves maintainability and reduces administrative overhead. Additionally, combining conditional stages with required data steps ensures critical information is collected at the appropriate stages, while irrelevant fields or steps are hidden for certain records.
Question 65:
You need to create a security role that allows users to share their own records with other users but prevents them from sharing records they don’t own. What privilege configuration should you use?
A) Share: User level
B) Share: Organization level
C) Assign: User level
D) Append: User level
Answer: A) Share: User level
Explanation:
Share privilege at the User level is the correct configuration for allowing users to share only the records they own in Dataverse. The Share privilege is part of the security role model and determines whether a user can share a record with other users or teams, granting those recipients access to records they might not otherwise have permission to view or modify. By setting the Share privilege to the User level, you ensure that a user can only share records where they are the owner. This restriction prevents users from sharing records owned by other users, maintaining security boundaries and ensuring appropriate access control within the organization.
This configuration is particularly useful in collaborative scenarios where users need to work together on individual records. For example, a sales representative may want to share a specific opportunity record with a manager or colleague for review or approval. By granting Share privilege at the User level, the representative can share only the opportunities they own, providing access to collaborators while maintaining control over the rest of the organization’s records. When sharing a record, the owner can specify the level of access for the recipient, such as read-only, read-write, or delete permissions, giving precise control over what collaborators can do with the shared record. This combination of ownership-based restriction and configurable access ensures both collaboration and security.
It is important to contrast the User-level Share privilege with other related privileges. Setting Share at the Organization level would allow users to share any record in the organization, which may violate data governance policies. The Assign privilege allows users to transfer ownership of records to others but does not control shared access. Append and Append To privileges govern how records are related or attached to other records, but they do not provide control over sharing access. Only the Share privilege specifically controls the ability to grant other users access to individual records while respecting ownership boundaries.
Additionally, User-level Share privileges support compliance and operational policies by ensuring that sensitive data is not inadvertently shared beyond the owner’s authority. It allows organizations to foster collaboration while enforcing least-privilege access principles. Administrators can apply this privilege selectively across different tables and security roles, ensuring that only appropriate records are shareable by each user group. This granular control helps maintain data integrity, prevent unauthorized access, and ensure that sharing is intentional and auditable.
Question 66:
You are creating a canvas app that needs to display a filtered list of items where the category field matches a user selection and the status is Active. What formula should you use?
A) Filter(Items, Category = Dropdown.Selected AND Status = “Active”)
B) Filter(Items, Category = Dropdown.Selected, Status = “Active”)
C) Filter(Items, Category = Dropdown.Selected && Status = “Active”)
D) Search(Items, Dropdown.Selected, “Category”) AND Status = “Active”
Answer: C) Filter(Items, Category = Dropdown.Selected && Status = “Active”)
Explanation:
The correct formula uses the Filter function with multiple conditions joined by the && (AND) operator in Power Apps. The Filter function is used to return a subset of a data source based on one or more conditions. The first parameter is always the data source you want to filter, followed by one or more logical conditions that determine which records are included. When multiple conditions need to be applied, they are combined using logical operators. The && operator represents a logical AND, meaning all conditions connected with && must evaluate to true for a record to be returned. Conversely, the || operator represents a logical OR, where a record is included if any condition is true.
For example, the formula Filter(Items, Category = Dropdown.Selected && Status = “Active”) will return only those records where both conditions are satisfied: the Category field matches the selected value in the dropdown control, and the Status field is equal to “Active.” This ensures that the resulting data set is precisely filtered according to multiple criteria, allowing users to see only relevant records. This pattern is fundamental when building responsive canvas apps that require dynamic filtering, such as dashboards, search interfaces, or forms that display context-specific records.
Using the && operator correctly is crucial for efficiency and proper results. Each condition is evaluated for every record in the data source, and only records that meet all criteria are included. Additional conditions can be chained using && to enforce more complex requirements. For instance, Filter(Items, Category = Dropdown.Selected && Status = “Active” && Priority = “High”) will further narrow results to records that are high-priority, active, and match the selected category. The Filter function also supports delegation to data sources like Dataverse, SharePoint, or SQL, meaning the filtering occurs server-side when supported, which improves performance for large datasets and reduces data transfer to the client.
Alternative approaches are less effective or incorrect. Option A, using AND as text, is not valid in Power Apps formulas. Option B, separating conditions with commas, evaluates conditions independently rather than combining them, which can produce unexpected results. Option D incorrectly uses the Search function, which performs text search but does not support complex field-based conditions or multiple logical operators.
Question 67:
Your organization needs to display a countdown timer on opportunity forms showing days until the estimated close date. What should you implement?
A) Calculated field with DATEDIFF
B) PCF control
C) JavaScript timer
D) Rollup field
Answer: B) PCF control
Explanation:
A Power Apps Component Framework (PCF) control is the correct solution for implementing custom visual components like countdown timers in model-driven apps. PCF controls are custom code components that can replace or enhance standard field controls with rich interactive experiences. You would create or install a PCF countdown control that displays the time remaining until the estimated close date with dynamic updating, visual styling, and interactive features that standard fields cannot provide.
PCF controls can render HTML, update dynamically, respond to user interactions, and integrate with the form’s data context accessing field values. A countdown timer control would read the estimated close date field, calculate the remaining time, and display it in an engaging format that updates in real-time. PCF controls are reusable across forms and can be configured with parameters to customize behavior and appearance for different scenarios.
Calculated fields with DATEDIFF would show days remaining but as a static number without timer functionality. JavaScript could create a timer but PCF is the proper framework for custom controls. Rollup fields aggregate related data. For implementing rich, interactive custom UI elements like countdown timers that go beyond standard field capabilities, creating or implementing PCF controls provides the modern, supported framework for extending model-driven app forms with custom visual components that enhance user experience.
Question 68:
You are configuring a Power Automate flow that needs to update multiple records in Dataverse based on results from an external API. What is the most efficient approach?
A) Apply to each with Update a row
B) Perform a changeset request
C) Multiple Update a row actions
D) Batch job with updates
Answer: B) Perform a changeset request
Explanation:
Perform a changeset request is the most efficient approach for updating multiple records in Power Automate when you need transactional behavior and optimal performance. Changesets are a feature in the Dataverse connector that allow multiple operations—such as create, update, or delete actions—to be grouped into a single request. All operations within the changeset are executed as a single transaction, which means they either all succeed or all fail together. This transactional behavior ensures data consistency and integrity, which is critical when updating related records or processing data from external sources where partial updates could cause inconsistencies.
Using a changeset significantly reduces the number of API calls sent to Dataverse. Normally, performing multiple updates individually in a flow triggers one API call per record, which increases network traffic, execution time, and potential throttling issues. In contrast, grouping updates into a changeset allows the flow to send all updates in a single request, reducing network round trips and improving overall flow performance. This is especially valuable when processing API responses or bulk data imports, such as updating a batch of contact records, invoice records, or inventory items, where each record must be updated in relation to the others.
To implement a changeset in Power Automate, you use the Perform a changeset request action available in the Dataverse connector. Within this action, you include multiple operations, typically Update a row actions, inside the changeset scope. The Dataverse platform then processes these updates together. If one operation fails due to validation errors or other constraints, all changes are rolled back automatically, ensuring the database remains in a consistent state. This all-or-nothing execution provides the transactional integrity necessary for critical business processes, such as financial updates, order processing, or case management, where partial updates could result in data corruption or incorrect business decisions.
Alternative approaches exist but have limitations. Using an Apply to each loop with individual Update a row actions works, but it executes each update sequentially, generating one API call per record, which is less efficient and slower for large datasets. Separate update actions without a changeset also fail to provide transactional guarantees and increase maintenance overhead. The term batch job is sometimes used to describe grouping updates conceptually, but Power Automate does not provide a specific “batch job” action for transactional execution; the changeset is the supported method for this purpose.
Question 69:
You need to create a view that displays opportunities grouped by owner with a count of opportunities for each owner. What should you configure?
A) Group by Owner with Count aggregate
B) Personal view for each user
C) Rollup field on User table
D) Chart with grouping
Answer: A) Group by Owner with Count aggregate
Explanation:
Group by Owner with Count aggregate is the correct configuration for creating a view that organizes and counts records by owner. In the view designer, you configure grouping by selecting the Owner field as the group-by field, then add a Count aggregate function to display the number of opportunities for each owner. This creates an expandable grouped view where each owner appears as a group header showing the count, with individual opportunities listed beneath when expanded.
This grouped view provides immediate visibility into opportunity distribution across the sales team, allowing managers to see workload balance and individual activity levels at a glance. Users can expand or collapse groups to see details when needed while maintaining the summary counts at the group level. The view can include additional aggregates like sum of estimated revenue per owner, providing comprehensive analytical insights directly within the list view without requiring separate reports.
Personal views would require each user to configure separately and wouldn’t show all owners. Rollup fields on User would require customization and aren’t appropriate for view-level aggregation. Charts visualize data but are separate from list views. For creating views that organize records into groups by a field like owner and display aggregate counts for each group, configuring group by with count aggregation provides the built-in analytical view capability that transforms standard lists into summarized group reports.
Question 70:
You are creating a business rule that should run on the server even when records are created through API or imports. What scope should you set?
A) Entity
B) All Forms
C) Specific Form
D) API Only
Answer: A) Entity
Explanation:
Entity scope is the correct setting for business rules that must execute server-side regardless of how records are created or updated. When a business rule is scoped to Entity, it runs on the Dataverse server and applies to all operations including form submissions, API calls, imports, and integrations. This ensures consistent business logic enforcement across all entry points, preventing users or systems from bypassing rules by creating records through methods other than forms.
Entity-scoped business rules are essential for data integrity requirements that must always be enforced such as required fields, field calculations, or validations that protect data quality. These rules execute during the save operation on the server, providing reliable enforcement that cannot be circumvented. The tradeoff is that entity-scoped rules have some limitations compared to form-scoped rules, such as not supporting UI actions like showing or hiding fields.
All Forms and Specific Form scopes make rules client-side only, executing when forms load or field values change in the UI but not during API operations or imports. API Only is not a valid scope option. For implementing business rules that must execute consistently regardless of data entry method ensuring server-side enforcement across forms, APIs, and imports, setting the scope to Entity provides the comprehensive server-side execution that maintains data integrity across all access methods.
Question 71:
Your organization uses Power Apps portals for customer case submission. You need to send an email notification when a customer submits a new case. What should you configure?
A) Portal webhook
B) Power Automate flow triggered on case creation
C) Entity form settings
D) Table permissions
Answer: B) Power Automate flow triggered on case creation
Explanation:
Power Automate flow triggered on case creation is the correct solution for sending notifications when portal users submit cases. You would create an automated cloud flow using the “When a row is added” trigger for the Case table in Dataverse. When a customer submits a case through the portal, it creates a new case record in Dataverse, which triggers the flow to send email notifications to support team members or managers about the new case submission.
The flow can include logic to route notifications to different people based on case category, priority, or customer segment. You can customize the email content with case details, customer information, and links to the case record. This approach provides reliable notification delivery and allows sophisticated routing logic, escalation rules, and integration with other systems beyond simple email notifications, such as creating tasks or updating dashboards.
Portal webhooks are for portal-specific events and are more complex than needed. Entity form settings control form behavior but don’t send notifications. Table permissions control data access. For sending email notifications when customers create records through portals, using Power Automate flows triggered on record creation provides the straightforward, flexible automation approach with rich notification capabilities and routing logic that integrates naturally with Dataverse data operations.
Question 72:
You need to create a canvas app that works with data from multiple Dataverse environments. What should you configure?
A) Multiple data connections
B) Environment variables
C) Data gateway
D) Cross-environment queries
Answer: A) Multiple data connections
Explanation:
Multiple data connections is the correct approach for accessing data from different Dataverse environments in a canvas app. Canvas apps support adding multiple Dataverse connections, and you can connect to different environments by adding separate Dataverse connections for each environment. Each connection is authenticated and authorized independently, allowing the app to retrieve and manipulate data from multiple environments within a single app experience.
When adding Dataverse connections, you specify the environment URL, and the app can then access tables from that environment. You can display data from different environments in different galleries or screens, merge data from multiple environments, or provide users with environment selection options. This is useful for scenarios like consolidating reports across development and production environments or providing administrative tools that manage multiple organizational units with separate environments.
Environment variables are for configuration within a single environment. Data gateway is for on-premises data sources. Cross-environment queries are not a standard feature. For building canvas apps that access and display data from multiple Dataverse environments, adding multiple data connections with each pointing to a different environment provides the capability to work with data across environment boundaries within a single app.
Question 73:
You are configuring a model-driven app and need to ensure users can quickly search for accounts by name or account number across the entire table. What should you configure?
A) Quick Find view
B) Advanced Find
C) Global search
D) Lookup view
Answer: A) Quick Find view
Explanation:
Quick Find view is the correct configuration for enabling quick search functionality across specific fields in model-driven apps. The Quick Find view defines which fields are searchable when users enter text in the search box at the top of views. By default, Quick Find searches the primary name field, but you can configure it to include additional fields like account number, phone number, or email address, providing users with fast multi-field search capabilities.
Configuring the Quick Find view involves editing the view definition and selecting which fields should be included in search operations. When users type in the search box and press Enter, the system searches across all configured Quick Find fields and displays matching records. This provides a fast, efficient way to locate records without using complex filter criteria, enhancing user productivity when they need to quickly find specific accounts or other records.
Advanced Find is a tool for creating complex queries but is separate from the quick search box. Global search (Categorized Search) searches across multiple tables but Quick Find is table-specific. Lookup views are for selecting related records. For enabling users to quickly search within a specific table across multiple fields using the search box in views, configuring the Quick Find view to include relevant searchable fields provides the fast search capability that makes record location efficient and intuitive.
Question 74:
You need to create a Power Automate flow that pauses execution for a specific period after sending an email before proceeding to the next action. Which action should you use?
A) Delay
B) Delay until
C) Wait
D) Pause
Answer: A) Delay
Explanation:
Delay is the correct action for pausing flow execution for a specified duration. The Delay action accepts a time value in various units including seconds, minutes, hours, or days, and suspends the flow’s execution for that period before proceeding to subsequent actions. This is useful when you need to space out actions, wait for external systems to process information, or implement reminder sequences with specific timing between notifications.
For example, after sending an initial email, you might use a Delay action set to 3 days before sending a follow-up reminder. The flow remains paused during this period without consuming resources, then automatically resumes and continues with the next action when the delay period expires. This enables creating time-based workflows and automated reminder sequences without requiring separate scheduled flows for each step.
Delay until is for pausing until a specific date and time rather than for a duration. Wait is not a standard Power Automate action. Pause is not the correct action name. For pausing flow execution for a specific time period such as hours or days between actions in automated workflows, the Delay action provides the timing control that enables creating sequences with appropriate spacing between steps without additional flow complexity.
Question 75:
You are configuring field-level security and need to allow users to create records with a secured field populated but prevent them from viewing the field value later. What should you configure?
A) Field permission profile with Create enabled, Read disabled
B) Business rule to clear the field after save
C) JavaScript to hide the field
D) Field permissions cannot support this scenario
Answer: D) Field permissions cannot support this scenario
Explanation:
Field-level security cannot support this specific scenario because Create permission is not a separate privilege for secured fields. Field-level security in Dataverse provides only Read and Update permissions for secured fields. Users must have Read permission to populate a field’s value during record creation. You cannot grant the ability to set a field value without also granting permission to read that value later. The security model treats field access as read/update operations without a distinct create-only permission.
This limitation is by design because creating a record with a field value requires knowing what value to set, which implies reading capability. If users should not see field values after initial creation, alternative approaches would be needed such as using a different field for input that a workflow or flow copies to the secured field, then clearing the input field. However, pure field-level security cannot enforce create-without-read scenarios.
A field permission profile with Create enabled doesn’t exist as Create is not an available field permission. Business rules could clear values but don’t address the core security requirement. JavaScript could hide fields in forms but doesn’t provide security enforcement. For scenarios requiring users to provide sensitive data during record creation that they shouldn’t see afterward, field-level security’s inherent limitation requires alternative architectural approaches beyond standard field permissions since create-only without read permissions is not supported.
Question 76:
You need to create a view that shows only records created in the last 30 days. What filter operator should you use?
A) On or after with date calculation
B) Last X days with 30
C) In the last 30 days
D) Greater than with calculated date
Answer: B) Last X days with 30
Explanation:
Last X days with the value 30 is the correct dynamic filter operator for showing records created in the last 30 days. This relative date operator automatically calculates the date range based on the current date, ensuring the view always shows records from the rolling 30-day window without manual updates. You would apply this filter to the Created On field, setting the operator to “Last X Days” and specifying 30 as the value.
Relative date operators like Last X Days are valuable for creating dynamic views that remain current without configuration changes. The view automatically adjusts its date range as time passes, always displaying the most recent 30 days of data. This is commonly used for views showing recent activity, new records, or time-sensitive information where the relevant timeframe moves forward with the calendar.
On or after with date calculation would require manual date updates. Greater than with calculated date is not available as a view filter. While “In the last 30 days” might sound correct, the actual operator name is “Last X Days” where X is configurable. For creating views that dynamically filter to recent records within a rolling timeframe, using the Last X Days operator with an appropriate number provides the dynamic date filtering that keeps views current automatically.
Question 77:
You are configuring a business process flow that spans multiple tables. Users report confusion about which table they are currently working with. What should you configure?
A) Stage categories
B) Display names for stages
C) Process stage indicators
D) Cross-entity stage labels
Answer: B) Display names for stages
Explanation:
Display names for stages are the correct configuration for providing clarity about which table and context users are in during cross-entity business process flows. Each stage in a business process flow has a display name that appears in the process bar. Using descriptive stage names that clearly indicate the table context and purpose helps users understand where they are in the process. For example, naming stages “Lead Qualification,” “Opportunity Development,” and “Quote Preparation” clearly indicates both the process phase and associated table.
Clear stage naming is particularly important in cross-entity flows where the process moves between tables like Lead, Opportunity, and Quote. Users need visual cues about these transitions. Including the entity name or context in stage labels helps users understand when they’ve transitioned to working with a different record type. Consistent naming conventions and descriptive labels improve user adoption and reduce errors by making the process progression intuitive.
Stage categories classify stages for reporting but don’t appear to users. Process stage indicators are not a configuration option. Cross-entity stage labels is not standard terminology. For helping users understand their current location and context in business process flows especially those spanning multiple tables, using clear, descriptive display names for stages that indicate both the process phase and table context provides the user-facing clarity that improves navigation and reduces confusion.
Question 78:
You need to create a Power Automate flow that sends different approval requests to different managers based on the opportunity amount. What should you implement?
A) Multiple Start and wait for approval actions with conditions
B) Parallel branches with approvals
C) Approval action with dynamic approvers
D) Switch case with approval actions
Answer: A) Multiple Start and wait for approval actions with conditions
Explanation:
Multiple Start and wait for approval actions with conditions is the correct approach for implementing amount-based approval routing. You would use Condition actions to check the opportunity amount against thresholds, then include different approval actions in each condition branch that send approval requests to appropriate managers. For example, opportunities under 50,000 dollars go to team leads, 50,000 to 100,000 go to directors, and over 100,000 go to VPs.
This pattern allows complete customization of the approval request for each tier including different approvers, approval types like first-to-respond versus everyone must approve, custom instructions, and different post-approval actions. The flow evaluates conditions sequentially and executes only the approval action in the matching condition branch, ensuring each opportunity is routed to the correct approval level based on its value.
Parallel branches would send approvals simultaneously to all managers rather than routing to the appropriate tier. Approval action with dynamic approvers could work but doesn’t handle different approval types for different amounts as cleanly. Switch case is not a standard Power Automate action. For implementing tiered approval workflows where different managers approve based on amount thresholds, using conditional logic with separate approval actions in each branch provides the flexible routing that ensures opportunities reach appropriate approval levels.
Question 79:
You are configuring a canvas app gallery that displays thousands of records. Users report slow performance when scrolling. What should you implement?
A) Data filtering with delegation
B) Collection with all data loaded
C) Concurrent loading
D) Increase gallery height
Answer: A) Data filtering with delegation
Explanation:
Data filtering with delegation is the correct solution for improving gallery performance with large datasets. Delegation allows the data source to handle filtering, sorting, and other operations server-side rather than bringing all data to the canvas app. You should ensure your gallery’s Items formula uses delegable functions and operators so the data source processes queries and returns only the necessary records that users view, rather than loading thousands of records into the app.
Properly implemented delegation means only a subset of records loads initially, with additional records retrieved as users scroll. This dramatically improves initial load time and overall responsiveness. You should check the delegation warnings in Power Apps Studio and rewrite formulas to use delegable patterns. Connecting to data sources that support delegation like Dataverse, SharePoint, and SQL Server and using supported operators ensures efficient data retrieval that scales to large datasets.
Loading all data into a collection would make performance worse by requiring download of all records. Concurrent loading is for running multiple operations simultaneously, not for data retrieval efficiency. Increasing gallery height doesn’t address the underlying data loading issue. For optimizing canvas app gallery performance with large datasets, implementing proper data filtering using delegation ensures efficient server-side query processing that only retrieves and displays the data users need when they need it.
Question 80:
You need to configure a security role that allows users to see all account records but only edit accounts in their business unit. Which privilege configuration should you use?
A) Read: Organization, Write: Business Unit
B) Read: Business Unit, Write: User
C) Read: Organization, Write: User
D) Read: Business Unit, Write: Business Unit
Answer: A) Read: Organization, Write: Business Unit
Explanation:
Read at Organization level and Write at Business Unit level is the correct configuration for this access pattern. The Read privilege at Organization level allows users to view all account records throughout the entire organization regardless of business unit ownership. The Write privilege at Business Unit level restricts editing to only accounts owned by users or teams within the user’s business unit. This combination provides broad visibility with restricted modification rights.
This configuration is common in organizational structures where users need visibility into all accounts for coordination and reference purposes but should only modify accounts within their own business unit to maintain data governance and prevent cross-division changes. Users can view accounts owned by any business unit but attempting to edit an account from a different business unit would result in insufficient privileges error.
Option B would restrict read access to the business unit. Option C would further restrict write access to only user-owned records. Option D would restrict both read and write to business unit. For providing organization-wide read visibility while limiting write capabilities to accounts within the user’s business unit, configuring Read at Organization level with Write at Business Unit level provides the appropriate combination of broad visibility with restricted modification rights aligned to organizational structure.
