You are requested to design a solution to handle a fallout scenario while communicating with an inventory system for resource allocation because there are no available ports for a product that was purchased. Identify a solution that would address this condition.

• A. reallocating the reserved ports in the inventory system and activating the requested ports in the activation system manually
• B. designing OSM to update the CRM system about the failure, so that the customer service representative (CSR) can decide whether to cancel the in-flight order or issue a new revision order to allocate new ports
• C. using the Task Web client to edit the order, manually changing the data received from the CRM system, and retrying the failed task for proper allocation of new ports
• D. cancelling the order in OSM and informing the customer that the request cannot be processed
• E. suspending the in-flight order in OSM and manually creating a new order to create new ports in the inventory system

Consider an order recognition rule where the validation rule XQuery expression contains the following lines of code. When a CRM application tries to create orders that would be processed by this recognition rule by using the CreateOrder web service, which are two possible responses it could receive depending on the output of the validation expression?

• A. a "Fault" message with the description containing "No matching Order Recognition rule found"
• B. a "Fault" message with the description containing "Error in validation expression. See order for details"
• C. a "Fault" message with a description containing "Transaction not allowed"
• D. a "CreateOrderResponse" message with the created "Order Id"
• E. a "Fault" message with a description containing "Order Id is missing in the request"

A requirement indicates that OSM should send a message to an upstream system when a manual task in your provisioning process reaches the Received state. How would you model this functionality in your cartridge?

• A. with Jeopardy Notifications implemented at the Order level
• B. with Data Change Notifications implemented at the Order level
• C. with Jeopardy Notifications implemented at the Task level
• D. with Task-State Event Notifications implemented at the Task level
• E. with Data Change Notifications implemented at the Task level
• F. with Milestone Event Notifications implemented at the Order level

Which three pieces of advice would you offer a developer who is responsible for configuring the CRM and Middleware systems that submit revisions to OSM?

• A. Use a unique identifier for each order and the same identifier for its revisions.
• B. Always use the same interface when submitting either an order or a revision.
• C. Revisions should have a distinct message schema from the original order.
• D. Have a numeric field that increases its value with every new revision.
• E. Always submit changes to services already provisioned by using revisions.

You must implement a dependency between two order components within a product specification, where the dependent order component will wait the amount of time defined in an order item property after the blocking order component finishes its execution and before starting its own execution.
What are the two tasks required to configure this behavior?

• A. defining a Wait For Condition in the dependency, which is configured with the task state "Completed"
• B. defining a Wait For Condition in the dependency, which is configured with a data change notification
• C. defining a Wait Condition in the dependency, which is configured with the task state "Received"
• D. defining a Wait Delay in the dependency, which is configured with a duration expression
• E. defining a Wait Delay in the dependency, which is configured with a fixed time duration
• F. defining a Wait Condition in the dependency, which is configured with no delay duration