Question 130 of 977
Describe Dynamics 365 SaleshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to use the existing Competitor entity and add a relationship to opportunity. This is the recommended approach because Dynamics 365 Sales ships with a native Competitor entity designed specifically for tracking rival companies, and you can create a many-to-many relationship linking it directly to the opportunity record. This allows you to associate multiple competitors with a single deal while leveraging the standard win/loss reason fields already present on the opportunity, avoiding unnecessary custom development. On the MB-910 exam, this question tests your understanding of out-of-the-box entity relationships versus custom creation—a common trap is assuming you need to build a new entity when the native one already fits the requirement. Remember, win/loss reasons are a standard opportunity field, so never move them to a custom entity. Memory tip: "Native Competitor + Opportunity link = no custom work."

MB-910 Describe Dynamics 365 Sales Practice Question

This MB-910 practice question tests your understanding of describe dynamics 365 sales. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 company uses Dynamics 365 Sales and has a custom entity 'Competitor'. You want to associate competitors with opportunities and track win/loss reasons. What is the recommended approach?

Question 1hardmultiple 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

Use the existing Competitor entity and add a relationship to opportunity

Option C is correct because the competitor entity is already available in Sales, and you can link it to opportunities. Option A is wrong because the competitor entity exists natively. Option B is wrong because win/loss reasons are captured on the opportunity, not on a custom competitor entity. Option D is wrong because win/loss reasons are standard fields on opportunity.

Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.

Answer analysis

Option-by-option breakdown

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

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

    Why it's wrong here

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

  • Create a custom field on opportunity for win/loss reasons

    Why it's wrong here

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

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

    Why it's wrong here

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

  • Use the existing Competitor entity and add a relationship to opportunity

    Why this is correct

    The Competitor entity is included in Sales and can be related to opportunities.

    Related concept

    Static NAT maps one inside address to one outside address.

Common exam traps

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Detailed technical explanation

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Key takeaway

NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.

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.

Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related MB-910 NAT questions on configuration and troubleshooting.

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 — Static NAT maps one inside address to one outside address..

What is the correct answer to this question?

The correct answer is: Use the existing Competitor entity and add a relationship to opportunity — Option C is correct because the competitor entity is already available in Sales, and you can link it to opportunities. Option A is wrong because the competitor entity exists natively. Option B is wrong because win/loss reasons are captured on the opportunity, not on a custom competitor entity. Option D is wrong because win/loss reasons are standard fields on opportunity.

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

Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related MB-910 NAT questions on configuration and troubleshooting.

What is the key concept behind this question?

Static NAT maps one inside address to one outside address.

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 21, 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.