MB-280 Practice Questions

BDM2 is a contact of interest for → both the London Office and Toronto Office opportunities.

BDM2 is a sales team member for all Northwind Traders opportunities, meaning they are involved in both the London Office and Toronto Office opportunities.

BDM3 is a contact of interest for → the Toronto Office opportunity.

BDM3 owns all Northwind Traders opportunities except those owned by BDM1. Since BDM1 owns the London Office opportunity, BDM3 is only involved in the Toronto Office opportunity.

Client Contact2 is a contact of interest for → the Toronto Office opportunity.

The Toronto Office opportunity lists Client Contact2 as the primary contact, making them a contact of interest for that opportunity.

Client Contact1 is a contact of interest for → the London Office opportunity.

The London Office opportunity lists Client Contact1 as the primary contact, making them a contact of interest for that opportunity.

Renaming the Omitted Column to Cancelled:

To rename a column in the forecast layout, such as changing Omitted to Cancelled, you should go to Layout column settings. This setting allows you to customize how columns appear in the forecast view, including renaming columns to better match your business terminology.

Renaming within Layout column settings will directly change how this column is labeled in the user interface for clarity and consistency with business terms.

1. Create a Power Automate flow with a Dataverse " When a row is added, modified or deleted " trigger.

This ensures that the flow is triggered when an account ' s client tier changes.

2. Set the table and column conditions for the triggering event.

The trigger should monitor changes to the contoso_clienttier field in the Accounts table.

3. Add a step to call the " Create card for assistant " action.

This step ensures that a custom insight card is created for the assistant in Dynamics 365 Sales.

4. Save and test the flow by manually performing an update.

This verifies that the Power Automate flow is correctly detecting tier changes and triggering the insight card.

5. Update the insight card item to select the flow.

This ensures that the newly created insight card is linked to the correct Power Automate flow.

Enable Auditing on Columns (Options A and D):

Enabling auditing on specific columns like Dietary requirements and Email address ensures that any changes to these fields are tracked. This meets Terra Flora ' s requirement to log changes to these fields along with details of who made the changes and the timestamp.

Enable Auditing on Pet and Contact Tables (Options B and C):

By enabling auditing at the table level for Pet and Contact, you ensure that any updates to these tables, including changes to all associated columns, are recorded. This broad setting ensures full coverage of auditing for both tables.

Enable Audit User Access (Option F):

This option is recommended to track when users access certain data, which can help with compliance and monitoring user interactions with sensitive data.

Option E (Start Read Auditing):

Read auditing tracks when records are read. If compliance requires monitoring every time a record is accessed, enabling this could be necessary; however, the primary focus is on modifications rather than access alone.

References from Microsoft Documentation:

For setting up auditing, see Auditing overview for Dynamics 365.

Start Auditing:

Enabling Start Auditing is the primary step to activate auditing for Dynamics 365. This setting ensures that changes to data, including field updates on records, are tracked and logged.

Without enabling this checkbox, no data changes will be recorded, as it is the fundamental requirement for auditing across all entities and fields.

Requirement: Add the Type of Loss

To track reasons for lost opportunities, including specifics like losses to competitors, you need to provide additional details on why an opportunity was closed as lost.

The Status Reason field can be customized to include specific reasons for the loss. This field is used within the context of the Opportunity entity and allows the addition of options to detail specific loss types.

By modifying the Status Reason option set, you can add various reasons (like " Lost to Competitor " ) which will appear as options when closing an opportunity as lost.