Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.A company uses a model-driven app.The company must be able to dynamically control how components of the form behave as users interact with it. The solution must modify the form in real time while the user interacts with the interface.You need to enforce client-side behavior dynamically.Solution: Use JavaScript to dynamically show and hide columns.Does the solution meet the goal?
Answer(s): A
Using JavaScript to dynamically show, hide, or disable columns is an excellent and widely used solution for enforcing client-side behavior in a model-driven app. You achieve this in real time by adding JavaScript web resources and attaching event handlers to the form's OnLoad and OnChange events.
https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/use-main-form-and-components
A company uses Power Apps.Users must be able to view only the address1 columns in the Account table.You need to ensure other address columns are not visible to users when creating views and filters.What should you do?
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.
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-field-solution-explorer
HOTSPOT (Drag and Drop is not supported)A company is implementing a data model by using Dataverse.The company requires the following columns in a new custom table:You need to choose the column type that uses the least amount of database storage for each column.Which column types should you choose? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Text AreaSingle Line of TextThis field can contain up to 4,000 text characters. You can set the maximum length to be less than this. This field has several format options that will change the presentation of the text. These options are Email, Text, Text Area, URL, Ticker Symbol, and Phone.* TextThis option simply displays text.* Text AreaThis format option can be used to display multiple lines of text. But with a limit of 4000 characters, the Multiple Lines of Text field is a better choice if large amounts of text are expected.Box 2: Multiline TextMultiple Lines of TextThis field can contain up to 1,048,576 text characters. You can set the maximum length to be less than this. When you add this field to a form, you can specify the size of the field.Box 3: CustomerCustomerA lookup field that you can use to specify a customer, which can be an account or contact.Customer fieldIn previous releases of Dynamics 365 Customer Engagement (on-premises), several out-of-the-box entities such as the Case, Lead, and Opportunity entities, included a special kind of lookup field that represented a customer. Using this lookup field you could choose between two entities: Account or Contact. With this new capability, you can add the Customer field to any system or custom entity. You can use the Customer field in more entities to track the customer's information in the same way you've used the Customer field in the Case, Lead, and Opportunity entities.Box 4: ChoiceDataverse Choice vs ChoicesThe number of options that can be selected defines a choice from a choices column. A choice column just supports one option, whereas a choice column also supports the addition of numerous values.
https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/types-of-fields https://www.spguides.com/power-apps-dataverse-choices/
DRAG DROP (Drag and Drop is not supported)You are designing a data model for a company. The model uses only standard Microsoft Dataverse tables.You must extend the existing Accounts and Contacts tables to support the following business requirements:-Store an additional classification value on the Accounts table.-Add a field that indicates a customer’s engagement tier on the Contacts table.-Create a mechanism to improve lookup performance and ensure uniqueness across selected fields. You need to modify the tables to support the business requirements.Which components should you use? To answer, move the appropriate components to the correct requirements. You may use each component once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.Note: Each correct selection is worth one point.Select and Place:
Box 1: Choice columnYou should use a Choice column (formerly known as an Option Set).This column type allows you to define a static list of predefined classification values (e.g., "Tier 1", "Tier 2", or "VIP") that users can select from a drop-down menu on the Account table/entity reference (Microsoft Dataverse).Predefined List: A classification value implies choosing from a fixed, standard set of options (e.g., Gold/Silver/Bronze or VIP/Standard).Native Feature: Choice columns allow users to select one or more values from a dropdown menu.Low Overhead: They do not require creating or maintaining separate tables.Box 2: Customer columnBox 3: Alternate keyYou should use an Alternate key.An alternate key in Microsoft Dataverse allows you to define a unique business key made of one or more columns. When you create an alternate key, the platform automatically generates a database index to enforce uniqueness and significantly optimize lookup performance.
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/define-alternate-keys-entity
HOTSPOT (Drag and Drop is not supported)You are designing the organization structure for a company that has 5,000 users.You need to configure security roles for the company while minimizing administrative effort.What should you do? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Create a new team, and the business unit users, and the assign the security role to the team.Change the business unit for a teamImportantBy changing the business unit for a team, you can remove all security role assignments for the team. At least one security role must be assigned to the team in the new business unit.1. Select an environment and go to Settings > Users + permissions > Teams.2. Select the checkbox for a team name.3. Screenshot selecting a team.4. On the menu bar, select Change Business Unit.5. In the Change Business Unit dialog box, select a business unit. Enable Move records to new business unit to move to a new business unit. Select OK.Box 2: Grant the user a security role from the child business unit.Incorrect:* Grant the user the Parent: Child Business Units security permission.Too much permissions granted.The application refers to this access level as Parent: Child Business Units.This access level gives a user access to records in the user's business unit and all business units subordinate to the user's business unit.* Grant the user a security role from the root business unit.Too much permissions granted.
https://docs.microsoft.com/en-us/power-platform/admin/create-edit-business-units https://docs.microsoft.com/en-us/power-platform/admin/security-roles-privileges
Post your Comments and Discuss Microsoft AB-410 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AB-410 content, but please register or login to continue.