AB-410 sample exam questions

A public view can be limited to specific people by assigning it to a security role, which makes it appear in the view selector only for managers. Table permissions would affect all views, removing it from navigation does not secure it, and quick find is a search view, not an access control.

The Parental relationship behavior cascades assign, share, delete, reparent and unshare from the parent to all child rows, so changing the owner reassigns the children. Referential and Restrict options do not cascade assignment.

Classification and tier are values picked from a fixed list, so a choice column fits both without adding tables. An alternate key creates a unique index over selected columns, which enforces uniqueness and speeds up lookups.

Teams working independently should each use their own development environment with separate solutions, then deploy them as managed solutions through test to production. A shared environment lets teams overwrite each other's changes, and changing production directly or using unmanaged solutions there is uncontrolled.

Copilot Studio agents and the app assistant agent give conversational, context-aware generated responses inside the model-driven app. Business rules are fixed logic and not generated responses. Smart assist gives suggestions but is not an interactive agent the user converses with, so it is the weaker choice.

User-level access limits read and write privileges to rows the user owns, which suits representatives. Organization-level access in a security role grants visibility of every row in the environment regardless of business unit, which suits managers who need all opportunities.

For a prompt used in Power Automate, the knowledge sources that ground the model through retrieval are Dataverse tables and their columns. Plain text, PDFs and images can be provided as inputs but are not grounding knowledge sources in the prompt builder.

A lookup column references one related row and stores the relationship in the table definition, with Dataverse maintaining the link. Rollup aggregates many related rows, and calculated and formula columns compute values rather than defining a relationship.

Business rules run client-side on the form as users interact, and they can show an error message on a column and set required, visibility or values. This meets the requirement for real-time form behavior. Server-side automation would not do this.

Community answer B is wrong. Dataverse users are synced from Microsoft Entra ID, so changing the user name in the Microsoft 365 admin center updates the sign-in name on the same user object. The Dataverse user row and all its history are kept, and no new user is created.

Canvas apps only run business rules scoped to Table, because that logic executes on the server rather than on a form. A recommendation is a form-only action, and a specific form scope confines it to the form used by the model-driven app.

Use one approval action with multiple approvers and a Custom Responses - Wait for one response type, so the flow continues after the first decision, including escalated. Then use a condition on the outcome to send the confirmation email. First to respond only supports Approve and Reject, so it misses escalation.

A lower temperature makes the model more deterministic and less creative, reducing unsupported or invented content while staying useful. Raising temperature increases randomness and hallucination risk. Content moderation filters harmful content, not factual accuracy.

Do until repeats its actions until a condition is true, so it suits waiting for a status of Complete. Apply to each runs once per item in an array obtained earlier, so a fixed list is handled exactly once per record.

The greater function returns true only when the first value is larger than the second, matching totals above 1,000. The contains function finds VIP anywhere in the name, whereas startsWith and equals would miss names with the string elsewhere.