Microsoft MB-240 Exam - Topic 2 Question 92 Discussion

Actual exam question for Microsoft's MB-240 exam

Question #: 92
Topic #: 2

You are a Dynamics 365 for Field Service Administrator.

You have a requirement to make a custom attribute "Contract Status" required and to not allow invalid data to be entered in the attribute.

What are three ways that you can make an attribute required on a form within the Dynamics 365 for Field Service Mobile App and ensure invalid data cannot be entered? Each correct answer presents a complete

solution.

ACreate an OnSave rule, and display a message to the user if the specific field does not meet the required
conditions.

BCreate an OnChange rule, and set a simple validation for a field to check whether the field contains data.

CCreate an Option Set with all possible options for the attribute.

DCreate an OnChange rule to highlight a field when it does not contain correct field data.

ECreate an OnSave rule to check any field's data, but without highlighting the field when the condition is not met.

Show Suggested Answer

Suggested Answer: A, C, E

by Fernanda at Nov 23, 2025, 10:14 AM

Limited Time Offer

25%

Off

Get Premium MB-240 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Precious

1 month ago

I agree with A and C. Combining them could enhance data integrity.

upvoted 0 times

...

Mattie

2 months ago

D could be useful. Highlighting fields helps users notice mistakes.

upvoted 0 times

...

Elza

2 months ago

I’m not sure about E. It checks data but doesn’t highlight issues.

upvoted 0 times

...

Loreta

2 months ago

Option B is good too. Simple checks on change can catch errors early.

upvoted 0 times

...

Paola

2 months ago

I think option A is solid. OnSave rules are crucial for validation.

upvoted 0 times

...

Walton

2 months ago

I disagree, E seems pointless if it doesn't highlight the issue!

upvoted 0 times

...

Ozell

2 months ago

B is a solid option, but I prefer A for better user feedback.

upvoted 0 times

...

Golda

3 months ago

Wait, can you really make it required without highlighting? Sounds odd.

upvoted 0 times

...

Alberto

3 months ago

I think A and D are good choices too.

upvoted 0 times

...

Horace

3 months ago

Option C is definitely the way to go!

upvoted 0 times

...

Mary

4 months ago

Haha, imagine if the options were "Contract Status: Awesome, Meh, or Catastrophic." That would be an interesting choice set!

upvoted 0 times

...

Nichelle

4 months ago

B is a good start, but a simple check for data isn't enough. You need more robust validation.

upvoted 0 times

...

France

4 months ago

D seems a bit overkill. Highlighting the field without preventing the save doesn't really solve the problem.

upvoted 0 times

...

Colton

4 months ago

OnSave rules are always a good choice to validate data before it's saved. Displaying a message to the user is a nice touch.

upvoted 0 times

...

Karol

4 months ago

I like the idea of using an option set to limit the possible values for the attribute. That way, you can ensure data integrity.

upvoted 0 times

...

Lino

4 months ago

I remember that highlighting a field can help users notice errors, so maybe D is useful, but I’m not confident if it actually makes the field required.

upvoted 0 times

...

Clement

5 months ago

I recall practicing something similar where we used OnSave rules to validate data. So, I think A and E might be valid options here.

upvoted 0 times

...

Sylvie

5 months ago

I think option C is definitely a good choice since using an Option Set would limit the data to valid entries.

upvoted 0 times

...

Bernadine

5 months ago

I'm feeling pretty confident about this. The key is to use a combination of the option set and the OnSave rule. The option set will ensure the data is valid, and the OnSave rule will make the field required. I think that should cover all the bases.

upvoted 0 times

...

Lavina

5 months ago

This seems straightforward. I'll create an option set with the valid options, and then use an OnSave rule to check if the field is filled out. If not, I'll display a message to the user letting them know they need to complete that field before saving.

upvoted 0 times

...

Tequila

5 months ago

A, C, and E seem like the best options to make the attribute required and ensure invalid data cannot be entered.

upvoted 0 times

...

Omer

5 months ago

Okay, I've got a strategy. I'll create an option set with the valid options for the "Contract Status" field. Then I'll add an OnChange rule to check if the field has a value, and if not, highlight the field to let the user know they need to fill it out. That should cover both the required and valid data aspects.

upvoted 0 times

...

Rasheeda

6 months ago

I prefer option C. An Option Set limits choices, ensuring valid data.

upvoted 0 times

...

Sheridan

6 months ago

I'm not entirely sure about the OnChange rule options. I feel like both B and D could work, but I can't remember which one is more effective for making a field required.

upvoted 0 times

...

Alpha

6 months ago

Hmm, I'm a bit confused. Do I need to create both an option set and an OnSave rule? Or can I just do one or the other? I want to make sure I fully understand the requirements before attempting to solve this.

upvoted 0 times

...

Laurel

6 months ago

I think I can handle this. Creating an option set with all the valid options seems like a good way to ensure the data is valid. And an OnSave rule to display a message if the field is not filled out properly should do the trick.

upvoted 0 times