To set pv!dealershipName using a dealership lookup, which approach should you implement?

To set pv!dealershipName using a dealership lookup, which approach should you implement?

• A. Add another output variable defined as rule!VIM_getDealershipName(pv!vehicle.dealershipName) that saves into pv!dealershipName.
• B. Modify pv!vehicle to contain dealershipName directly.
• C. Create a new data store variable.
• D. Change the function to accept a dealershipName field from input.

Answer: (A)

The main idea being tested is how to obtain a user-friendly display value from a data item using a reusable lookup rule and then store that result in a local display variable. In this approach, you create or use an existing rule that takes the dealership identifier ( pv!vehicle.dealershipName, or whatever ID it is) and returns the actual dealership name. You then wire the result of that rule into the local output pv!dealershipName by defining an output variable for the rule invocation, and assign rule!VIM_getDealershipName(pv!vehicle.dealershipName) into pv!dealershipName. This keeps the original vehicle data structure intact, promotes reuse of the lookup logic, and ensures the UI shows the correct, human-readable name even if the underlying data changes. This pattern is preferable over altering the vehicle object to include the name directly, which would couple the display data to the data model; over creating a new data store variable just for this derived value, which adds unnecessary persistence; or over changing a function to pull the name from input fields, which can complicate the function’s responsibilities.

The main idea being tested is how to obtain a user-friendly display value from a data item using a reusable lookup rule and then store that result in a local display variable. In this approach, you create or use an existing rule that takes the dealership identifier ( pv!vehicle.dealershipName, or whatever ID it is) and returns the actual dealership name. You then wire the result of that rule into the local output pv!dealershipName by defining an output variable for the rule invocation, and assign rule!VIM_getDealershipName(pv!vehicle.dealershipName) into pv!dealershipName. This keeps the original vehicle data structure intact, promotes reuse of the lookup logic, and ensures the UI shows the correct, human-readable name even if the underlying data changes.

This pattern is preferable over altering the vehicle object to include the name directly, which would couple the display data to the data model; over creating a new data store variable just for this derived value, which adds unnecessary persistence; or over changing a function to pull the name from input fields, which can complicate the function’s responsibilities.