Question 522 of 977
Describe Dynamics 365 SalesmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to create a 1:N relationship between the custom Partnership entity and the Opportunity entity. This configuration is correct because a one-to-many (1:N) relationship in Dynamics 365 allows a single Partnership record to be linked to multiple Opportunity records, enabling your sales team to track revenue from partner deals separately without altering core system entities. On the MB-910 exam, this scenario tests your understanding of custom entity relationships and how they support business process tracking—a common trap is confusing this with a many-to-many (N:N) relationship, which would be overkill for simple deal attribution. Remember the memory tip: "One partner, many deals" directly maps to the 1:N structure, keeping partner revenue neatly tied to each opportunity.

MB-910 Describe Dynamics 365 Sales Practice Question

This MB-910 practice question tests your understanding of describe dynamics 365 sales. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Your sales team uses a custom entity called 'Partnership' that stores partner details. They want to track revenue from partner deals separately. What should you configure?

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Create a 1:N relationship between Partnership and Opportunity

A 1:N relationship between Partnership (custom entity) and Opportunity allows each partnership to be associated with multiple opportunities, enabling separate tracking of revenue from partner deals. This leverages Dynamics 365's relational data model to link partner details directly to sales opportunities without modifying core entities.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Create a 1:N relationship between Partnership and Opportunity

    Why this is correct

    This allows linking multiple opportunities to a partnership and tracking revenue.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Add a custom field 'Partner Name' to the Opportunity entity

    Why it's wrong here

    A single field cannot capture detailed partner information.

  • Create a Goal entity tied to Partnership

    Why it's wrong here

    Goals track targets, not actual revenue from deals.

  • Use the Connection entity to link Partnership and Opportunity

    Why it's wrong here

    Connections are for ad-hoc relationships, not for structured revenue tracking.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse the Connection entity (which is for ad-hoc, non-hierarchical links) with the structured 1:N relationship required for parent-child data modeling, leading them to choose option D.

Detailed technical explanation

How to think about this question

Under the hood, a 1:N relationship in Dynamics 365 creates a lookup field on the child entity (Opportunity) that stores the parent entity's (Partnership) GUID, enabling efficient queries and rollup calculations. In a real-world scenario, this allows sales managers to use calculated fields or Power BI to aggregate revenue from all opportunities linked to a specific partnership, supporting partner commission calculations and pipeline analysis without custom development.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related MB-910 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free MB-910 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this MB-910 question test?

Describe Dynamics 365 Sales — This question tests Describe Dynamics 365 Sales — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Create a 1:N relationship between Partnership and Opportunity — A 1:N relationship between Partnership (custom entity) and Opportunity allows each partnership to be associated with multiple opportunities, enabling separate tracking of revenue from partner deals. This leverages Dynamics 365's relational data model to link partner details directly to sales opportunities without modifying core entities.

What should I do if I get this MB-910 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This MB-910 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MB-910 exam.