Describe Dynamics 365 Sales practice questions

Add a multi-select field for win/loss reasons on the Competitor entity

Why wrong: Win/loss reasons are typically captured on the opportunity, not on the competitor.

Create a custom field on opportunity for win/loss reasons

Why wrong: The opportunity entity already has a standard win/loss reason field.

Create a new custom entity 'Competitor' and add a lookup to opportunity

Why wrong: A Competitor entity already exists in Sales; no need to create a new one.

Sequence

Why wrong: Sequence provides a predefined set of steps for sales reps to follow, but it does not automatically suggest next actions based on past deals.

Relationship analytics

Why wrong: Relationship analytics provides insights on communication patterns and best practices, but it does not directly suggest next actions. That is the role of Relationship Assistant, which is part of Sales Insights.

Predictive lead scoring

Why wrong: Predictive lead scoring scores leads and opportunities based on likelihood to convert, but it does not suggest next actions.

Contact

Why wrong: Contact is also created typically, but in the context of this question, it is not one of the two record types required; the correct pair is Account and Opportunity.

Invoice

Why wrong: Invoice is not created during lead qualification; it is created after an order is fulfilled.

Quote

Why wrong: Quote is not created during lead qualification; it is created during the opportunity stage.

Configure a Power Automate flow that sends an email to the sales manager when an opportunity is not updated for 14 days.

Why wrong: This notifies after a longer period and still requires manual follow-up.

Use a business process flow to require mandatory fields on opportunity creation.

Why wrong: This helps with data entry but not with updates over time.

Set up a recurring email notification to the sales manager to manually remind reps.

Why wrong: This still relies on manual action and does not enforce updates.

Use a team-based security model where all sales reps are in one team.

Why wrong: Team access would give reps access to other team members' records.

Give all users the same security role with Deep access.

Why wrong: Deep access allows access to all records in the hierarchy.

Create a security role with User level access and assign it to all users.

Why wrong: User level limits to own records, but managers would also be limited.

The Relationship Assistant.

Why wrong: This provides insights but not a direct chronological activity list.

The Notes section on the opportunity form.

Why wrong: Notes are for free-form text, not for tracking meetings and tasks.

The Associated View for the opportunity.

Why wrong: This is a grid view of related records, not a chronological activity list.

Create a custom field for probability and use a workflow to update it.

Why wrong: Creating a custom field and workflow would require manual maintenance and lacks the native integration with sales stage progression that Dynamics 365 Sales’ built-in predictive scoring provides. This option is tempting because custom fields and workflows are a flexible way to automate many business processes, and they would be correct if the company needed to set a fixed probability value based on a specific trigger unrelated to the sales stage.

Use the predictive scoring model to calculate probability.

Why wrong: Predictive scoring is different and uses machine learning, not stage-based.

Enable the 'Auto-update Probability' setting in the opportunity entity.

Why wrong: This setting does not exist; probability is tied to the sales stage.

Sales Manager Goal dashboard.

Why wrong: This tracks progress against goals, not pipeline risk.

Sales Activity dashboard.

Why wrong: This shows activities, not pipeline risk.

Lead Generation dashboard.

Why wrong: This focuses on leads, not opportunities.

Enforce that all fields in the opportunity form are required.

Why wrong: Business process flows can make fields required only within the flow, but not for the entire entity.

Automatically send an email when an opportunity is won.

Why wrong: Automation is done by workflows or Power Automate.

Control which users can view or edit opportunities.

Why wrong: Security roles control access, not business process flows.

Automatically creating a quote from an opportunity.

Why wrong: Quote creation is manual or via workflow.

Analyzing the sentiment of email threads.

Why wrong: Sentiment analysis is separate, in Conversation Intelligence.

Enable the custom field in the opportunity form

Why wrong: Custom fields need to be mapped in forecasting configuration, not just enabled on forms.

Add the custom field to the lead entity

Why wrong: Forecasting is based on opportunities, not leads.

Configure sales acceleration rules to include the custom field

Why wrong: Sales acceleration deals with lead assignment, not revenue mapping for forecasting.

Modify the business process flow to include a task step

Why wrong: Business process flows include stages and steps, but they do not automatically create tasks without additional customization.

Configure an email template to be sent when the stage changes

Why wrong: Email templates send emails, not create tasks.

Use a stage-specific form to display a task subgrid

Why wrong: Subgrids display existing records, they do not create tasks automatically.

Sales Insights dashboard

Why wrong: The dashboard provides analytics, not a chronological list of activities.

Associated View for activities

Why wrong: Associated View shows related records but is not a chronological timeline.

Activity entity in Advanced Find

Why wrong: Advanced Find shows all activities across the system, not filtered to the specific opportunity.

Sales team configuration with assignment rules

Why wrong: Sales teams define groups but assignment is done with routing rules.

Business process flow automation

Why wrong: Business process flows define stages, not assignment.

Automatic record creation and update rules

Why wrong: These rules create records from email, they do not assign leads.

Access to all custom entities and fields without limitations

Why wrong: Some customizations may not be available in the mobile app due to design constraints.

Automatic data synchronization with external CRM systems

Why wrong: The app syncs with Dynamics 365, not external systems.

Full administrative capabilities for system configuration

Why wrong: Administrative tasks are not supported in the mobile app.

Enable lead scoring to qualify leads faster, use seller cards to display tasks, and configure automatic record creation rules for tasks.

Why wrong: Lead scoring and seller cards do not automate task creation or price list assignment.

Implement Sales Insights for activity tracking, use lead scoring to prioritize leads, and configure personal dashboards for overdue tasks.

Why wrong: Sales Insights provides analytics, not task automation. Lead scoring does not assign price lists.

Configure business process flows for opportunities, set up sales teams with assignment rules, and use the Sales Hub app for dashboards.

Why wrong: Business process flows define stages but do not create tasks automatically. Sales teams do not manage price lists.

Enable LinkedIn Sales Navigator integration to view customer activity and use Power Automate to send follow-up emails.

Why wrong: LinkedIn Sales Navigator provides social insights, not engagement scoring from website/email.

Use Power Automate to monitor customer interactions and create custom workflows to send alert emails to sales representatives.

Why wrong: Power Automate can send alerts but lacks built-in engagement scoring and email sequence capabilities.

Implement the Sales Hub app and configure offline sync to track customer activities in real-time.

Why wrong: Sales Hub app does not provide real-time engagement scoring or automated nurture sequences.

Send bulk email campaigns to all contacts associated with an opportunity

Why wrong: Bulk email campaigns are not a direct feature of the opportunity entity; they are part of marketing.

Create quotes directly from an opportunity without any manual data entry

Why wrong: Quotes can be generated from opportunities, but some manual review is usually needed.

Automatically generate invoices for closed won opportunities

Why wrong: Invoice generation is typically handled by the Finance module, not directly by the opportunity entity.

The pricelevelid is specified at both opportunity and line item levels

Why wrong: This is allowed and not the cause of failure.

The totalamount field is inconsistent with the line items total

Why wrong: While the total might be off, the API does not enforce this at creation, and it would not cause line items to fail to be added.

The product numbers 'PR-001' and 'PR-002' do not exist in the system

Why wrong: If the products did not exist, the error would be about invalid product IDs, not about line items not being added.

Configure the campaign entity to automatically update the source field on all associated leads

Why wrong: Campaigns do not have a direct relationship to leads' source fields; this is not a standard feature.

Modify the lead form to make the source field read-only and set its default value to 'Campaign'

Why wrong: This would set the default for all leads, not just those from campaigns.

Use a business process flow to require the user to select 'Campaign' as the source when creating a lead from a campaign

Why wrong: Business process flows do not set default values; they guide users through stages.