Microsoft Power Platform Functional Consultant Free Sample Questions

Business rules with a scope of 'All Forms' or a specific form execute on the client-side (in the user's browser) and will only trigger when a user interacts with a form in a model-driven app. To ensure the logic runs for server-side changes, such as those made by Power Automate flows or other API calls, the scope must be set to 'Entity'. This makes the business rule execute on the Dataverse server, regardless of how the data is modified.

To allow all authenticated students to see all available courses for their major, a Table Permission with a 'Global' scope is appropriate for the 'Course' table, which can then be filtered by the student's major on the list component.

To ensure students can only see their own enrollments, a Table Permission with a 'Contact' scope is necessary. This scope filters the 'Enrollment' records to only those associated with the currently logged-in student (who is represented as a contact record).

The correct ALM process for updating a foundational or core managed solution is to increment the version number, export it again as a managed solution, and import it into the target environments using the 'Upgrade' option. This approach properly applies the updates, maintains the solution layers, and ensures that dependent solutions in the regional environments are not broken. This is a standard practice for solution patching and upgrades.

A Rollup column is the correct choice because it is designed to aggregate data from related records. By using the MAX function on the 'Donation Date' column of the child 'Donation' records, it will find the most recent date. Crucially, rollup columns store the calculated value in the database, which allows the data to be used in sorting and filtering within views, satisfying all requirements. Calculated and Formula columns are computed on-the-fly when retrieved and cannot be used for sorting in views.

A Quick View form is specifically designed to display read-only information from a related record on another record's form. By creating a Quick View form for the 'Policyholder' table and adding it to the 'Claim' form via the lookup field, the consultant can display the required summary information directly on the claim record.

The 'Configure Run After' setting is the primary mechanism for error handling in Power Automate. By setting the error logging action to run after the email action fails, you create a specific error handling path. The subsequent 'Create a task' action should then run after the error logging action completes, ensuring it executes regardless of the email action's outcome, fulfilling the business requirement.

This statement is false. An embedded canvas app is a separate app and must be explicitly shared with users. While it can receive context from the model-driven form (like the current record's ID), users must have separate permissions to run the canvas app itself. They also need appropriate permissions for any data sources the canvas app connects to, which may be different from the parent form's data source.

By setting the relationship behavior to Referential and the Delete action to 'Restrict', you are configuring a standard database constraint. This setting tells Dataverse not to allow the deletion of the parent record (Project) if any related child records (Risks) exist. This is the most direct and efficient way to enforce this rule at the data layer without requiring additional logic like flows or plugins. The condition of 'Active' risks would require a plugin or flow, but the general prevention of deletion is handled by Restrict.

The modern command designer is the recommended approach for customizing command bars. It uses Power Fx for both actions and visibility rules. You can write a formula in the 'Visible' property of the button that checks if the current user's security roles include 'Sales Managers'. This is a low-code, supported, and modern way to implement conditional visibility.

Dataverse search must first be enabled at the environment level in the Power Platform admin center before it can be configured and used.

Dataverse search uses the columns defined in a table's Quick Find View to determine which columns to search and which to display in the search results. This must be configured for each table intended to be part of the search.

After enabling Dataverse search for the environment, you must explicitly select which tables should be included in the search index. This is done within the solution or the default configuration area for search.