Dataverse table columns are the appropriate knowledge source for a prompt that must use Retrieval- Augmented Generation with current business information. Grounding the prompt with selected Dataverse data allows the model to incorporate governed product specifications at runtime instead of relying only on its pretrained knowledge. The maker can identify the relevant table and columns and then pass or retrieve the business context required by the prompt. A PNG image is an input artifact, not the structured knowledge source needed for specification retrieval. Plain text can provide fixed instructions or context but does not create a maintained enterprise data source. A PDF can be useful in other grounding experiences, but under the available prompt knowledge options in this scenario, the Dataverse table provides the direct, structured, updateable source. Access remains subject to environment and table security, so only approved data should be exposed to the prompt. The AB-410 Study Guide explicitly measures the ability to "add knowledge to a prompt." Selecting Dataverse table columns implements that objective while minimizing duplication of product data.
Study Guide reference/topic: "Create prompts and models in AI Hub - Add knowledge to a prompt." AB-
410 Study Guide | Microsoft Learn technical reference

To achieve this goal, you should restrict the view by assigning it to the manager security role.
Incorrect:
[Not B]
Table-level permissions (Security Roles) control access to the data rows themselves, not the user interface components like views.
Reference:
https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/manage-view-access

Explanation:
Build and validate new features - Sandbox; Host stable workloads - Production

A Sandbox environment is appropriate for building and validating new features. It supports development and testing activities while isolating unfinished work from operational users and production data. It can be reset, copied, placed in administration mode, or otherwise managed for lifecycle work without treating it as the stable system of record. A Production environment is intended to host the approved business workload, with controlled access, monitoring, backup, and managed solution deployment. The Default environment is automatically available to users in a tenant and is not the recommended controlled development or enterprise- production boundary. A Developer environment is designed for an individual maker rather than the shared development team described in the scenario. Security groups can restrict membership, but the environment type still needs to reflect its lifecycle purpose. The team should also use solutions and deployment pipelines so validation occurs before production import. The AB-410 Study Guide explicitly asks candidates to
"recommend environment types" and "apply a Microsoft Power Platform solution and ALM strategy." Sandbox for build/validation and Production for stable workloads is the aligned environment architecture.
Study Guide reference/topic: "Design Power Platform solutions - Recommend environment types." AB-410 Study Guide | Microsoft Learn technical reference

Using column-level security to remove read access is the correct and most appropriate approach.
In Microsoft Dataverse, column-level security (CLS) applies a restrictive model organization-wide.
Once you enable column security on a column, all users automatically lose read, create, and write access to that column by default. Because the underlying data engine strictly blocks unauthorized access, these columns are automatically hidden from forms, system views, personal views, and filter dropdowns. This safely prevents users from adding restricted columns when they try to build their own custom views or query filters.
Reference:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-field-solution-explorer

Correct:
* Ask the Microsoft 365 administrator to sign in to the admin portal and change the user name.
Changing the username (User Principal Name/UPN) in the Microsoft 365 admin center updates the credentials the user employs to sign into the model-driven app. Because Microsoft Power Platform and Dataverse map permissions and record histories to the underlying, immutable object identifier (GUID) of the user record, modifying the UPN:
Preserves history: The system retains all ownership of records, historical timelines, and application tracking linked to that user account.
Updates the sign-in name: The new name flows directly into Microsoft Entra ID and syncs automatically with the Power Platform environment.
Incorrect:
* Change Elizabeth's username in the user record for the app.
* From Dynamics 365 Settings, select Email Configuration. In the active mailbox for the user, update the name.