Topic 1: Terra Flora
You need to ensure the active stage of the business process flow is visible in the view. Which two actions should you perform? Each correct answer presents a complete solution. Choose two. NOTE: Each correct selection is worth one point.
A. Add a page for the Onboard new pet table to the Sales Professional app.
B. Add columns from the stable to the Active Onboard new pet view.
C. Add columns from the Pet table to the All Onboard new pet view.
D. Create a new column on the Pet table named "Onboarding stage" and add it to the Active pets view.
Explanation:
This question has been mistakenly mixed into your AZ-140 exam stream. This is not an Azure Virtual Desktop (AVD) question; it is a Microsoft Power Platform/Dynamics 365 question related to configuring business process flows and model-driven app views. The terms "business process flow," "table," "view," and "Onboard new pet" are specific to Dataverse and model-driven apps.
Given that, and to maintain consistency, I will answer based on the Power Platform context of the question:
Correct Options (Power Platform Context):
B. Add columns from the stable to the Active Onboard new pet view.
To make the active stage of a business process flow visible in a view, you must add the business process flow's "Stage" column from the related table to that view's column set. This action surfaces the current stage information in the grid.
D. Create a new column on the Pet table named "Onboarding stage" and add it to the Active pets view.
Business process flow data is stored in a special "Process" column (often named "processname stage"). Creating this column (or ensuring it exists) and adding it to the view is necessary to display the active stage. This is a fundamental configuration step.
Incorrect Options (Power Platform Context):
A. Add a page for the Onboard new pet table to the Sales Professional app.
Adding a page (a table form) to an app makes the form accessible, not the stage within a view. It does not directly address the requirement to make the active stage visible in a list view.
C. Add columns from the Pet table to the All Onboard new pet view.
Adding generic columns from the main table does not specifically add the business process stage column, which is what's needed to display the active stage. The stage is a separate, process-related field.
Note: For your AZ-140 preparation, please disregard this specific question as it pertains to a different exam domain (PL-400/PL-600/MB-210). Please continue with your AVD-related questions.
You need to configure the required audit settings. Which two actions should you perform? Each correct answer presents part of Ihe solution. Choose two. NOTE: Each correct selection is worth one point.
A. Enable auditing on the Dietary requirements column.
B. Enable auditing on the Pettable.
C. Enable auditing on the Contact tab\e.
D. Enable auditing on the Email address column.
E. Enable Start read auditing in system settings.
F. Enable Audit user access in system settings.
Explanation:
This question appears to have been mixed into your AZ-140 stream as well. This is not an Azure Virtual Desktop question; it is a Microsoft Power Platform/Dynamics 365 question regarding auditing configuration for Dataverse. The terms "auditing," "table," and "column" refer to the Dataverse auditing feature used to track data changes.
Given the Power Platform context, here is the analysis:
Correct Options (Power Platform Context):
A. Enable auditing on the Dietary requirements column.
Auditing in Dataverse can be enabled at the column (attribute) level. If you need to track changes specifically to the "Dietary requirements" data, you must enable auditing for that individual column.
B. Enable auditing on the Pet table.
Auditing must first be enabled at the table (entity) level. This is a prerequisite before you can enable auditing for specific columns within that table. The system will then record create, update, and delete operations on the table.
Incorrect Options (Power Platform Context):
C. Enable auditing on the Contact table.
While you might audit the Contact table, the scenario requirement is focused on the Pet table and its specific column ("Dietary requirements"). Enabling it on Contact is irrelevant to the stated need.
D. Enable auditing on the Email address column.
This is not the column specified in the requirement ("Dietary requirements"). Auditing should be targeted based on the specific business or compliance need.
E. Enable Start read auditing in system settings.
"Start read auditing" is not a standard Dataverse auditing setting. Standard auditing tracks create, update, delete, and share operations, but not read operations, due to performance impact.
F. Enable Audit user access in system settings.
This is a different audit trail. "Audit user access" tracks user sign-ins and privilege changes, not changes to data within a specific table or column. It does not meet the requirement to audit data changes.
Note for your studies:
This question pertains to the Power Platform/Dataverse domain. For your AZ-140 (Configuring and Operating Windows Virtual Desktop on Microsoft Azure) exam, please disregard this and focus on AVD-specific topics like host pools, FSLogix, networking, and monitoring. Feel free to provide the next AVD question.
You have added the timeline control to the Pet main form, then saved and published your changes. You need to configure the timeline to display related Pet activities as required by Terra Flora. Which two actions should you perform? Each correct answer presents a complete solution. Choose two, NOTE: Each correct selection is worth one point.
A. In the Record types of the timeline settings, uncheck the Notes option.
B. In the Activity area of the timeline settings, remove all activity types, except for Task. Email and Phone Call.
C. In the Record types of the timeline settings, uncheck the Posts option.
D. In the Record types of the timeline settings, uncheck the Activities option.
E. In the Notes area of the timeline settings, uncheck the Remove notes title when authoring option.
Explanation:
This question has been mistakenly mixed into your AZ-140 exam preparation. This is not an Azure Virtual Desktop question; it is a Microsoft Power Platform/Dynamics 365 question regarding the configuration of the Timeline control on a model-driven app form. The Timeline control is used to display a history of activities and notes related to a record.
Given the Power Platform context, here is the analysis:
Correct Options (Power Platform Context):
B. In the Activity area of the timeline settings, remove all activity types, except for Task, Email and Phone Call.
The requirement is to display only Pet activities. Activities in Dataverse are specific types like Task, Email, Phone Call, Appointment, etc. To filter the timeline to show only the required activity types (likely Task, Email, Phone Call based on the scenario), you must deselect all other activity types in the timeline settings.
C. In the Record types of the timeline settings, uncheck the Posts option.
The timeline can show different record types: Activities, Notes, and Posts. "Posts" refer to the auto-post records created by the system (e.g., when a record is assigned or a status changes). To ensure the timeline displays only related Pet activities (and potentially notes), you should uncheck "Posts" to hide these system-generated entries, cleaning up the view.
Incorrect Options (Power Platform Context):
A. In the Record types of the timeline settings, uncheck the Notes option.
This would hide notes from the timeline. The requirement is to display related Pet activities. Notes are often relevant to the record's history, and the scenario does not specify to exclude them. Unchecking "Activities" or "Notes" would likely hide too much information.
D. In the Record types of the timeline settings, uncheck the Activities option.
This would hide all activities, which is the exact opposite of the requirement to display related Pet activities. This action would make the timeline useless for showing the required information.
E. In the Notes area of the timeline settings, uncheck the Remove notes title when authoring option.
This setting controls the UI behavior when creating a note (whether the title field is shown). It has no impact on which records are displayed in the timeline, only on the note creation experience.
Important Note:
This concludes the current batch of questions. Several of the last questions were not related to the AZ-140 exam. They pertained to Microsoft Power Platform (PL-400, MB-210, etc.). For effective AZ-140 preparation, please ensure your future questions focus on Azure Virtual Desktop topics such as:
Host pool creation and configuration
FSLogix Profile Containers and Office Containers
Networking (NSGs, Azure Firewall, Private Endpoints)
Authentication (Azure AD Join, AD DS, Azure AD DS)
Monitoring and scaling (scaling plans, Azure Monitor)
Security (Conditional Access, RBAC)
MSIX app attach
You need to build a trigger-based journey to send the "Getting started" emails requested by the global sales lead. Which trigger should you use to start the journey?
A. Dataverse record change trigger
B. Custom trigger with lead profile data
C. Custom trigger with contact profile data
D. Email Link Clicked interaction trigger
Explanation:
This question has again been mixed into your AZ-140 stream. This is not an Azure Virtual Desktop question; it is a Microsoft Dynamics 365 Customer Insights - Journeys (formerly Marketing) question. It deals with creating a marketing journey (automated campaign) triggered by a change in a Dataverse record, such as a lead or contact being created or updated.
Given this is a Dynamics 365 Marketing/Journeys context:
Correct Option:
A. Dataverse record change trigger.
This is the correct starting trigger for the described scenario. The "Getting started" emails should be sent automatically when a new lead is created or reaches a specific stage in the sales process. The Dataverse record change trigger allows you to start a journey based on an entity (like Lead) being created or having a specific attribute updated, perfectly matching the requirement for an automated onboarding email sequence.
Incorrect Options:
B. Custom trigger with lead profile data / C. Custom trigger with contact profile data.
While you could build a custom trigger, the Dataverse record change trigger is the standard, out-of-the-box trigger designed specifically for this purpose. Creating a custom trigger is unnecessary extra work when a built-in, purpose-built trigger exists.
D. Email Link Clicked interaction trigger.
This trigger is used to start a journey when a recipient clicks a link in a previously sent email. This is for re-engagement or follow-up journeys, not for initiating a brand-new "Getting started" onboarding sequence based on a record being created.
Final Note for Your Studies:
This question is not relevant to the AZ-140 exam. It pertains to Dynamics 365 Customer Insights - Journeys (MB-220) or similar marketing automation exams.
To properly prepare for AZ-140: Configuring and Operating Windows Virtual Desktop on Microsoft Azure, please ensure your questions focus on that specific domain. I am ready to help with actual AVD topics.
You need to configure search to ensure the administrators can find all records which reference Corgis. Which action must you perform?
A. Within system settings, select up to 10 relevant tables.
B. Within the solution, ensure all relevant tables are indexed.
C. For all relevant tables, ensure that the Can enable sync to external search index setting is False.
D. Add columns to be searched to the Lookup view for each relevant table.
Explanation:
This question has also been mixed into your AZ-140 stream. It pertains to search configuration in the Microsoft Power Platform or Dynamics 365 Dataverse, not Azure Virtual Desktop. The question is about setting up search to find records across multiple tables that reference a specific term ("Corgis").
Given the Power Platform/Dataverse context, here is the analysis:
Correct Option:
B. While this seems to indicate a specific answer (like "None of the Above" or a misprint), based on the scenario, the correct concept is about enabling and managing search indexes. However, among the provided choices, none perfectly describe the primary action of configuring relevance search or enabling tables for search. The closest relevant action would be ensuring tables are added to the search scope or indexed for relevance search, which is not accurately represented in options A-D.
Analysis of Provided Options (Dataverse Context):
A. Within system settings, select up to 10 relevant tables.
This references an older or limited configuration. In modern Dataverse, you can select multiple tables for relevance search in the search configuration, but the limit and location (system settings vs. search management) are not accurately described here.
B. Within the solution, ensure all relevant tables are indexed.
Indexing is a backend process managed by the platform. While search relies on indexes, administrators don't "ensure indexing within a solution" as a configurable step for search functionality. Solutions contain metadata, not control over indexing processes.
C. For all relevant tables, ensure that the Can enable sync to external search index setting is False.
Setting this to False would prevent the table from being indexed for external search (like Azure Cognitive Search), which is the opposite of what's needed to make records searchable.
D. Add columns to be searched to the Lookup view for each relevant table.
Lookup views control the columns displayed in lookup dialogs, not the columns indexed for global search. This does not affect the ability to find records via search.
Reference & Clarification:
To configure search to find records across tables, you typically:
Go to Settings > Search > Relevance Search.
Enable tables for search.
Configure the searchable columns for those tables.
You need to identify the duplicate pet records, so they can be manually merged by the carer. What must you create?
A. Two duplicate detection jobs and two duplicate detection rules
B. One duplicate detection job and three duplicate detection rules.
C. Two duplicate detection jobs and three duplicate detection rules.
D. Three duplicate detection rules only.
Explanation:
This question continues the pattern of unrelated content. It is a Power Platform/Dynamics 365 question regarding Duplicate Detection, not an Azure Virtual Desktop topic. The question asks about the components needed to set up duplicate detection for a table (like "Pet").
Given the Power Platform context, here is the analysis:
Correct Option:
B. One duplicate detection job and three duplicate detection rules.
This is the correct answer based on standard duplicate detection configuration. You create:
Duplicate Detection Rules: These define how duplicates are identified (e.g., match on Name, Phone, Email). You need one rule per matching criteria you want to check. The scenario likely requires checking three fields (e.g., Pet Name, Owner Email, Microchip ID), hence three rules.
Duplicate Detection Jobs: These are the scheduled processes that run the rules against the data. You typically create one recurring job that executes all the enabled duplicate detection rules for the specified table.
Incorrect Options (Power Platform Context):
A. Two duplicate detection jobs and two duplicate detection rules.
This uses an unnecessary extra job and fewer rules than likely required.
C. Two duplicate detection jobs and three duplicate detection rules.
This uses an unnecessary extra job. One scheduled job is sufficient to run multiple rules.
D. Three duplicate detection rules only.
Rules alone are not enough. You must also create and publish a Duplicate Detection Job to actually scan the records and identify duplicates. Rules define the logic; jobs execute the logic.
Reference (for context, not AZ-140):
Microsoft Docs: Set up duplicate detection rules - Explains the process of creating rules and jobs.
A company uses Microsoft SharePoint document management in Dynamics 365 Sales to store contracts. The company wants only the contracts team to have access to the documents. The contracts team has a custom security role. You need to restrict privileges to secure the documents. What should you do?
A. Create a new security role in Dynamics 365 Sales.
B. Update the users list in the SharePoint site.
C. Update privileges in the Dynamics 365 Sales security role of the contract team.
D. Create a new group in the SharePoint site.
Explanation:
This question, once again, is not related to the AZ-140 exam. It is a Dynamics 365 Security and SharePoint integration question. It deals with securing documents stored in a SharePoint site that is integrated with Dynamics 365. The key point is that document access is controlled at the SharePoint site level, not solely within Dynamics 365 security roles.
Given the Dynamics 365 context:
Correct Option:
B. Update the users list in the SharePoint site.
When using SharePoint document management with Dynamics 365, the actual documents are stored in SharePoint. Therefore, permissions to access, view, or modify those documents are governed by SharePoint's permission model. To restrict access to only the contracts team, you must manage the user or group memberships directly within the specific SharePoint site or document library where the contracts are stored.
Incorrect Options (Dynamics 365 Context):
A. Create a new security role in Dynamics 365 Sales.
Dynamics 365 security roles control access to records and entities within Dynamics 365, not to the physical documents stored in SharePoint. Creating a new role in D365 does not affect SharePoint permissions.
C. Update privileges in the Dynamics 365 Sales security role of the contract team.
While you can control whether a user can see the "Documents" tab or the SharePoint integration entity within a record, the ability to read/write the actual document files is a SharePoint permission. Updating D365 privileges does not grant or restrict access to the files in the SharePoint repository.
D. Create a new group in the SharePoint site.
This is a step in the process, but it's not the complete action. Creating a group alone doesn't secure the documents. You must then assign the correct permissions to that group and update the site/library permissions to include only that group (which is effectively what option B implies by updating the user/group list).
Reference (for context, not AZ-140):
Microsoft Docs: Manage document permissions - Explains that SharePoint manages the permissions for documents.
You are creating a forecast. You want to include only opportunities that sell You need to configure this within the system. What should you configure?
A. separate views
B. additional filters
C. multiple columns
D. premium forecasting
E. premium forecasting
Explanation:
This question is not related to the AZ-140 exam. It is a Dynamics 365 Sales question regarding configuring forecasts. The requirement is to filter which opportunity records are included in a forecast calculation, which is a standard configuration step when setting up a forecast.
Given the Dynamics 365 Sales context:
Correct Option:
B. additional filters.
This is correct. When creating or editing a forecast in Dynamics 365 Sales, you define the criteria for which opportunities are included by adding filters. These filters can be based on opportunity fields (e.g., Status, Sales Stage, Product Line, Estimated Revenue) to include only those that match specific business rules, such as "opportunities that sell X."
Incorrect Options (Dynamics 365 Context):
A. separate views.
Views are used to display lists of records (like opportunities) with specific filters and columns. While a view could be used to see a subset of opportunities, forecasts are not configured by selecting a view. Forecasts use their own dedicated filtering system within the forecast configuration.
C. multiple columns.
Adding columns is about what data is displayed in a view or form, not about defining which records are included in a forecast's roll-up calculation.
D. premium forecasting / E. premium forecasting.
"Premium forecasting" likely refers to a specific capability or tier, but it is not a configuration action. The action of filtering which records are included is performed by setting filters, regardless of whether it's standard or premium forecasting. (Note: The duplicate "E. premium forecasting" appears to be a typo in the question.)
Reference (for context, not AZ-140):
Microsoft Docs: Create and manage forecasts in Dynamics 365 Sales - Details how to set up filters for forecast inclusion.
A company is implementing the Dynamics 365 Sales mobile app. The company requires setup of several push notifications for sellers who use the app. You need to create the push notifications. Which feature should you use?
A. Plug-in
B. Cloud flow
C. Classic Dataverse workflow
Explanation:
This is not an AZ-140 question. It is a Dynamics 365/Power Platform question regarding automation for the Sales mobile app. The requirement is to create push notifications, which are event-driven automated messages sent to a user's mobile device.
Given the Power Platform/Dynamics 365 context:
Correct Option:
B. Cloud flow.
This is correct. Cloud flows in Power Automate are the modern, low-code automation service. You can create a cloud flow that is triggered by a specific event in Dataverse (e.g., an opportunity is assigned, a task is overdue) and then sends a push notification via the Dynamics 365 mobile app to the relevant user. This is the standard and supported method for implementing such real-time notifications.
Incorrect Options (Power Platform Context):
A. Plug-in.
A plug-in is a server-side custom code (C#) that executes business logic within the Dataverse platform. While powerful, it is not used for sending user-facing push notifications to a mobile app. It is designed for complex data validation, integration, or calculation logic.
C. Classic Dataverse workflow.
Classic workflows are a legacy, server-side automation tool within Dataverse. They are primarily for data-centric operations (create/update records, assign tasks) and lack the native, straightforward ability to send push notifications to the Dynamics 365 mobile app. Cloud flows are the recommended replacement for most notification and approval scenarios.
Reference (for context, not AZ-140):
Microsoft Docs: Send push notifications with Power Automate - Explains how to configure cloud flows to send push notifications to the Dynamics 365 mobile app.
You have opportunities that have values in multiple currencies. You manually update currency exchange rates once per month. You need to ensure that currency values are accurately reported. When is the new currency exchange rate applied to the opportunity records?
A. When an opportunity changes the status reason.
B. When the calculate rollup field system job for the msdyn_projectteam table runs.
C. When the calculate rollup field system job for the account table runs.
D. When an opportunity changes the status.
Explanation:
This question is not an AZ-140 question. It is a Dynamics 365 Sales/Finance question regarding how currency conversion works on opportunity records when exchange rates are manually updated.
Given the Dynamics 365 context:
Correct Option:
A. When an opportunity changes the status reason.
This is the standard behavior in Dynamics 365. The base currency amount of an opportunity (or any transaction currency record) is locked and recalculated when the record reaches a specific stage in its lifecycle, typically when its status or status reason changes (e.g., from "Open" to "Won"). This ensures financial reporting consistency. Manually updating the exchange rate in the system does not automatically retroactively change already calculated amounts on open records; the new rate applies to new transactions or when the existing record's status changes.
Incorrect Options (Dynamics 365 Context):
B. When the calculate rollup field system job for the msdyn_projectteam table runs.
This is related to a specific Project Operations table (msdyn_projectteam) and its rollup fields, not to the core opportunity currency conversion process.
C. When the calculate rollup field system job for the account table runs.
This is related to rollup fields on the account entity (e.g., total revenue from all opportunities). This system job calculates aggregated values but does not trigger the re-calculation of the base currency amount on individual opportunity records based on new exchange rates.
D. When an opportunity changes the status.
This is very close to the correct answer. However, in Dynamics 365, the precise trigger is often tied to the status reason field, which is a more specific sub-status within a status (e.g., Status=Open, Status Reason=In Progress). The system uses status reason transitions to lock pricing and currency amounts.
Reference (for context, not AZ-140):
Microsoft Docs: Transaction currency behavior - Explains how base amounts are calculated and locked.
You need to update the role configuration for the digital sales team to enable the capability requested. What two actions should you perform? Each correct answer presents part of the solution. Choose two. NOTE: Each correctselection is worth one point.
A. Grant View Audit Summary permissions to the Digital seller security role.
B. Assign the Sales Copilot user role to the members of the digital sales team.
C. Grant View Audit History permissions to the Digital seller security role.
D. Grant View Audit Partitions permissions to the Digital seller security role.
Explanation:
To enable the digital sales team's request to use Copilot for summarizing changes to lead records, you need to ensure that they have the necessary permissions and access to the required features. Here’s how to proceed:
Assign the Sales Copilot User Role:
Dynamics 365 Copilot in Sales is a feature that assists users by providing insights and summaries based on data within the system.
To allow the digital sales team to access and utilize Copilot's capabilities, they must have theSales Copilot user roleassigned. This role enables users to interact with Copilot and benefit from its AI-driven functionalities such as summarizing changes and insights in records.
Microsoft Documentation Reference:Dynamics 365 Sales Copilot Setup
Grant View Audit History Permissions:
TheView Audit Historypermission is essential for team members to access audit logs, which is necessary for reviewing and summarizing changes made to lead records.
Enabling this permission will allow the digital sales team to view a history of modifications in lead records, thus allowing them to generate summaries based on this audit trail.
The View Audit Summary permission specifically lets them see summaries of audit data, which complements Copilot’s functionality by allowing Copilot to access detailed change history for summarization.
Microsoft Documentation Reference:Security Roles and Privileges
By implementing these two actions, the digital sales team will have both the necessary access to Copilot features and the required permissions to audit lead record changes, enabling them to leverage Copilot for summarizing changes to leads effectively.
One of the data sources being ingested into Dynamics 365 Customer Insights - Data is Microsoft Dataverse. During the unification process, you need to identify the primary key.
Which three data types can you use as a primary key attribute? Each correct answer presents a complete solution. Choose three. NOTE: Each correct selection is worth one point.
A. Integer
B. Whole Number
C. String
D. Boolean
E. GUID
Explanation:
In Dynamics 365 Customer Insights - Data,primary key attributesmust uniquely identify records and be consistent across the data source.
Whole NumberandGUIDare commonly used data types for primary keys because they can uniquely identify records and are natively supported for primary keys in databases.
Stringcan also be used as a primary key if it uniquely identifies each record (e.g., an email address).
IntegerandBooleanare generally not used as primary keys in Customer Insights because they may not provide unique identifiers suitable for all scenarios.
[Reference:Microsoft Documentation - Configure Primary Key in Dynamics 365 Customer Insights, ]
| Page 1 out of 5 Pages |