exam questions

Exam MB-200 All Questions

View all questions & answers for the MB-200 exam

Exam MB-200 topic 6 question 16 discussion

Actual exam question from Microsoft's MB-200
Question #: 16
Topic #: 6
[All MB-200 Questions]

DRAG DROP -
You manage a Dynamics 365 environment. You create a global option set for a custom solution.
You observe the following issues with the global option set:
✑ The default prefix is incorrect.
✑ The option set value is too long.
You need to change the option set value and ensure the correct prefix is used.
Which actions should you perform? To answer, drag the appropriate actions to the correct options. Each action may be used once, more than once, or not at all.
You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:

Show Suggested Answer Hide Answer
Suggested Answer: Explanation
References:
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/change-solution-publisher-prefix

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Dimmzi
Highly Voted 5 years, 8 months ago
Modify the published in the custom solution Modify the global option set in the custom
upvoted 25 times
mgharably
5 years, 8 months ago
correct
upvoted 1 times
Arki
5 years, 7 months ago
In Real-Life, both answers ("modify .. in Custom" und modify .. in Default) are working, but "Modify .. in Default" should be "more correct" - because its written in the Microsoft Documentation: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-edit-global-option-sets
upvoted 7 times
...
...
SoMuchConfusion
5 years, 4 months ago
I don't see a list of options for this question, but your second suggestion appears to be incorrect. You cannot modify the schema name (which includes the publisher prefix as it was at the time the field was first created) after creating a field. Without knowing the options presented, I can't say what the right answer is, but in general it would be to modify the publisher prefix on the solution's publisher record, then delete the global option set and create it again from scratch with the new prefix.
upvoted 5 times
SoMuchConfusion
5 years, 4 months ago
Forgot to mention: option set values *can* be changed after the fact. For those, I would still modify the default in the publisher profile to affect future options, but you can go back and modify the options in the existing global option set and change the values associated with each. However, since you need to recreate the option set from scratch to fix the prefix, editing the existing option set options is a moot point and a pointless exercise.
upvoted 3 times
...
...
...
jpthomas
Highly Voted 5 years, 2 months ago
ANSWER CHOICES (-Modify the publisher of the custom solution -Modify the global option set of the custom -Modify the publisher of the default solution -Modify the global option set of the default)
upvoted 17 times
...
NikunjKalyani
Most Recent 4 years, 5 months ago
Answer: https://drive.google.com/file/d/1oVytBUnzhOUkR0WC20UxlSVQ3aaF235u/view
upvoted 6 times
...
ExamDoug
4 years, 11 months ago
You can change a solution publisher (so also for the default solution) https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/change-solution-publisher-prefix
upvoted 1 times
...
vblord
4 years, 11 months ago
How do you modify the publisher of the default solution?
upvoted 2 times
...
amnajalal
4 years, 11 months ago
why not Modify the publisher of the default solution for (a) Modify the global option set of the custom solution for (b) ??
upvoted 1 times
...
GaiaBx
5 years, 1 month ago
Modify the publisher of the default solution, for both
upvoted 2 times
khanbaba
5 years, 1 month ago
Question is about "You create a global option set for a custom solution"
upvoted 2 times
...
...
ned
5 years, 4 months ago
1) Modify the publisher of Custom Solution 2) Modify the global option set in the custom
upvoted 7 times
...
Fyrus
5 years, 6 months ago
In the real live, once created the option set you can't "modify" the prefix. And modifying the published will not change the option set value. You have to do those things and then delete the option set and create it again. I even have to say that it's better to create with another schema name since a couple of times I had problems with deleted and recreated fields on Dynamics CRM when importing it into production
upvoted 8 times
SoMuchConfusion
5 years, 4 months ago
You said "I even have to say that it's better to create with another schema name since a couple of times I had problems with deleted and recreated fields on Dynamics CRM when importing it into production". What causes this is if you recreate a field with the same schema name but a different data type (even down to things like changing Date Only to Date and Time, simple to calculated, etc--not just the actual data type). However, for this scenario, you're right that you'd have to delete and recreate the field after changing the solution publisher profile's prefix to the correct value. At that point, you would have no choice but to give it a new schema name, since the prefix is now different than the original version of the option set!
upvoted 2 times
...
...
spokoloko
5 years, 8 months ago
Makes little sense. Once an option set is created you cannot change it's schema name (prefix).
upvoted 10 times
mgharably
5 years, 8 months ago
delete it and recreate ;)
upvoted 12 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago