Microsoft MB-280 Practice Test - Questions Answers, Page 5

Since the company uses Microsoft SharePoint for document storage, access to documents is controlled through SharePoint permissions rather than Dynamics 365 security roles.

To restrict document access to only the contracts team, you should update the users list in the SharePoint site where the documents are stored. This involves configuring SharePoint permissions to ensure that only the contracts team (or a specific SharePoint group associated with them) has access to the document library where contracts are stored.

By following these steps, you enable the sellers to edit Account records in Copilot for Sales while restricting access to the 'Revenue Forecast' field, ensuring both productivity and compliance with organizational policies.

Enable Copilot for Sales in Dynamics 365:

To make Copilot features available, you must enable Copilot for Sales within Dynamics 365. This involves setting up the environment so that Copilot can access and utilize the sales data effectively.

Verify Server-Side Synchronization and Security Roles:

Copilot for Sales relies on server-side synchronization to ensure data flow between Dynamics 365 and other services, such as Teams. Ensure that server-side synchronization is enabled and that users have the necessary security roles in Dynamics 365 to access and use Copilot.

Assign Privileges for Copilot in Teams:

Ensure that users have the correct privileges within Teams to access Copilot. This might involve configuring access policies and permissions so that eligible users can utilize Copilot features during their interactions within Teams.

Manager on System User Record:

Suggested contacts in Teams can include users directly linked to the individual starting the chat. The manager assigned on the user's system record can be a suggested contact, as this is a common relationship that suggests frequent communication.

Record Owner of the Initiating Record:

The owner of the record being discussed or acted upon is also likely to be a suggested contact. This is because the owner has primary responsibility for the record and would commonly need to be consulted or informed about actions related to it.

Created By of the Initiating Record:

If the user is the Created By for a record, they are associated with its initial setup or creation. As a result, they may be suggested when actions on that record are taken since they are familiar with its origins.

These selections align with the rules typically used for suggesting contacts in integrated Teams chats, ensuring relevant parties are automatically suggested based on record associations and user relationships.

Understanding the Statuscode and Statecode Columns:

In Dynamics 365 Sales, opportunities have two primary columns related to their status: statecode and statuscode.

The statecode defines the primary state of an opportunity (e.g., Open, Won, Lost).

The statuscode provides more granular reasons associated with each primary state. For example, within the 'Open' state, you can have various reasons such as 'In Progress,' 'On Hold,' etc.

Modifying Status Reasons for Open Opportunities:

The construction company wants to indicate when opportunities are delayed due to specific external factors. To accommodate this, they need specific status reasons like 'Pending Permits' and 'Asbestos Removal.'

By adding these as status reasons under the 'Open' state, you enable sales team members to select these options directly from their current status options.

Steps to Add New Status Reasons to Open Opportunities:

Navigate to Solution: Go to the Dynamics 365 Sales app, then to Settings > Customizations > Customize the System.

Locate the Opportunity Entity: In the default solution, find and expand the 'Entities' list, then select 'Opportunity.'

Edit Statuscode Values: Within the 'Opportunity' entity, select 'Fields,' then find and edit the statuscode field. Here, you can add new options under the 'Open' status. Add 'Pending Permits' and 'Asbestos Removal.'

Publish the Changes: After adding and saving the new status reasons, publish the changes so that they are available to users.

Verifying Custom Status Reason Visibility:

Ensure the new options are available on the Opportunity form for selection.

Test by opening an Opportunity and confirming that the 'Pending Permits' and 'Asbestos Removal' options are available under the Open status reasons.

By following these steps, the sales team can now use specific status reasons to indicate why certain opportunities are delayed, providing clearer visibility into the sales pipeline's status.

Steps to Configure the Quality Lead Experience Setting:

Navigate to Settings > Administration > System Settings.

Go to the Sales tab.

Set Qualify lead experience to 'Yes' to allow flexibility in lead conversion.

Requirement #2 Explanation:

The requirement states that sellers need different options for specifying the final status of deals.

The Customize close opportunity form setting allows customization of the form where users specify the status reason when closing an opportunity.

By enabling this, you can provide multiple status options, helping sellers specify various outcomes for closed deals (e.g., different statuses for won or lost deals).

Steps to Configure the Customize Close Opportunity Form Setting:

Navigate to Settings > Administration > System Settings.

Go to the Sales tab.

Set Customize close opportunity form to 'Yes' to allow adding specific status options when an opportunity is closed.

By setting these configurations, Dynamics 365 Sales will support both the need for flexible lead qualification and provide detailed status options for opportunity closures, aligning with the organization's requirements.

Steps to Create a Product Property:

Go to Sales > Product Catalog > Products.

Open the existing product (bread) and navigate to Product Properties.

Add a new property (flavor) and define the possible values (e.g., new flavors).

Save and publish the product with the updated properties.

Scenario 2: Changing an Order to a New Bread Flavor in an Opportunity

When a customer wants to change their order to a new flavor within an existing opportunity, the selected product in the opportunity can be updated to reflect the new flavor.

Since flavors are configured as product properties, you can select the specific flavor for the opportunity product directly without needing to recreate or delete the product from the opportunity.

This approach leverages product properties, ensuring that the change is streamlined and does not require re-adding or modifying the core product.

Steps to Select a New Flavor in the Opportunity Product:

Open the specific opportunity record in Dynamics 365.

Navigate to the product line items and select the bread product.

In the product properties, update the flavor to the new option as required.

Save the changes to ensure the opportunity reflects the new flavor selection.

These actions allow the bakery to manage new flavors flexibly within their product catalog and seamlessly adjust opportunities to accommodate flavor changes, enhancing customer satisfaction and operational efficiency.

Steps to Modify the Status Reason Option Set:

Go to Settings > Customizations > Customize the System.

Locate the Opportunity entity and open its Fields section.

Find and select the statuscode (Status Reason) field.

Add new options to represent specific loss types and save the changes.

Publish the customization to make the new Status Reason options available for users.

Requirement: Record the Loss for Forecasting

Sales managers need to include lost opportunities and their reasons in forecasting. To ensure that this information is captured accurately, modifying the Opportunity Close form will allow users to specify details when marking an opportunity as closed (won or lost).

By customizing the Opportunity Close form, you can include fields that capture detailed information required for forecasting, such as the type of loss and any competitor information. This ensures that loss details are available for analysis and forecasting without needing custom code.

Steps to Modify the Opportunity Close Form:

In the Sales Hub, navigate to App Settings > Close Opportunity Experience.

Customize the Opportunity Close form to include fields that are relevant to capturing loss information, such as adding fields for competitors or reasons.

Save and publish the form to reflect the changes.

By modifying the Status Reason option set and customizing the Opportunity Close form, you enable the sales team to record detailed reasons for lost opportunities, which will support accurate forecasting and analysis, all without using custom code.

To assign salespeople to sales territories, the user needs permissions to manage territory assignments, which is typically a higher-level responsibility.

The Vice president of sales role includes privileges related to managing sales territories, unlike the Sales team member or Salesperson roles, which are more focused on direct sales tasks.

The System customizer role does not specifically grant territory management permissions and is more focused on customization and configuration tasks.