Explore the core capabilities of customer engagement apps in Dynamics 365 →hardMultiple ChoiceObjective-mapped

MB-910 Practice Question: Explore the core capabilities of customer engagement apps in Dynamics 365

Exhibit

Refer to the exhibit.

{
  "entity": "account",
  "attribute": "telephone1",
  "format": "phone",
  "maxLength": 50,
  "minLength": 10
}

A Dynamics 365 administrator configures the above field definition. What is the most likely effect?

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

✓

The field enforces a phone number format

The format is set to 'phone', which enforces a phone number input mask. Option A is wrong because the format is not 'email'. Option B is wrong because minLength and maxLength are set. Option C is wrong because the format is phone, not URL.

Answer analysis

Option-by-option breakdown

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

✗
The field only accepts email addresses
Why it's wrong here
The format is 'phone', not 'email'.
✗
The field accepts a URL
Why it's wrong here
The format is 'phone', not 'url'.
✗
The field accepts any text up to 50 characters
Why it's wrong here
The format enforces a phone number pattern.
✓
The field enforces a phone number format
Why this is correct
Setting format to 'phone' applies phone number validation.

Go deeper

MB-910 Practice Question: Explore the core capabilities of customer engagement apps in Dynamics 365

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question