A Revenue Cloud Consultant is defining relationships in Constraint Modeling Language (CML) to model a house that must contain rooms. The house must have at least one and at most five rooms, and exactly two bathrooms. The consultant also wants the system to instantiate rooms in a specific order – first a Living Room, then a Bedroom – when rooms are created. Which script correctly defines these relationships in CML?

This script correctly models the specified requirements using Constraint Modeling Language (CML). The relation rooms : Room[1..5] line accurately sets the cardinality to require at least one and at most five rooms. The order (LivingRoom, Bedroom) clause correctly enforces the specified instantiation sequence. The relation bathrooms : Bathroom[2] line correctly constrains the model to have exactly two bathrooms. The type hierarchy, where LivingRoom, Bedroom, and Bathroom inherit from Room, is also correctly defined using the colon (:) notation.

A. This option is incorrect because the cardinality for rooms is [0..5], which allows for zero rooms, violating the "at least one" requirement. Additionally, the order clause is reversed.

1. Salesforce Industries CPQ Developer Guide, "Constraint Modeling Language (CML)": This document outlines the syntax for CML.

Section: Relations and Cardinality: It specifies that cardinality is defined using brackets, e.g., [min..max] or [exactnumber]. The requirement for "at least one and at most five" is correctly written as [1..5], and "exactly two" is [2]. Option A's [0..5] is incorrect.

Section: Order Keyword: This section explains that the order keyword is used within a relation definition to specify the instantiation sequence of related types. The syntax order (Type1, Type2) is shown, which matches the correct implementation in option B.