Exam PL-600 topic 8 question 1 discussion

B. Lookup is the best choice, the meal choice can change and then be re-used else where, other wise A Global option set would be the next best answer - because they want the ability to store the Customer Preference for future flights.

Meal types can be temporarily available - Lookup (with a flag)

you could use a javascript to hide one of the choices unavailable, but maybe this is not a good idea.

There are some... personal decisions I guess in this. My Answer is LookUp and here is why, I am not going with Option set 1. You could set an option set value to inactive and then filter and only show the active. But this would require that you do a deployment every single time to change this or manually go into production and change it (not a chance this should ever happen, although I am certain it does) Lookup is the best because you can simply have the flag or use the status column to set it to custom value/inactive and filter casted on that. You could then easily have some simple admin form (Canvas or Model) that would allow you to add / remote / set inactive/unavailable Best solution: LookUp

A lookup makes the most sense in this case. "The company offers two types of meals: standard and vegetarian. Meal types can be temporarily unavailable. The airline is considering offering other meal types, such as gluten-free and low-sodium options." This statement tells you the options can and most likely will change depending on availability. Therefore, the only flexible option would be a LookUp.

B: you can temporarily hide options and add new options

Certainly C would do the job. However, A is from an architectural point of view a better choice. B does not meet the requirement. What is the benefit of a table which contains two rows: vegetarian and regular?

B is the best choice. They want to grow this list.

Lookup as there needs to be a way to mark meals as unavailable

The needs : "Meal types can be temporarily unavailable. The airline is considering offering other meal types, such as gluten-free and low-sodium options" So meals have to be in a custom table with a status : Available or not. And it's much easier to add new types of meals.

This question was on the exam.

The best choice is B. Lookup. Because of this one : and can save the meal choices as a customer preference. If we need to save all meal choices, we neet to create N-N relationship with meal entity (customer preference)

B, if it's unavailable you'd want to hide/filter the data. List could grow

Looks like the meal options are not a sure thing. So would go with B