When sending customer orders from a CRM application, a customer sales representative (CSR) reports that order requests are returning an error: "No matching Order Recognition rule found." After analyzing the error, you decide that a catch-all recognition rule should be configured, so that these orders are still created in OSM. Which three actions would you take to configure your new catch-all recognition rule?

• A. setting relevancy to a number lower than other recognition rules
• B. defining an Input Message format based on the CRM message
• C. implementing the Recognition Rule with an expression such as "fn:true()"
• D. selecting the Fail Order check box
• E. defining an empty namespace

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 a data change notification
• B. defining a Wait Delay in the dependency, which is configured with a fixed time duration
• C. defining a Wait Delay in the dependency, which is configured with a duration expression
• D. defining a Wait For Condition in the dependency, which is configured with the task state "Completed"
• E. defining a Wait Condition in the dependency, which is configured with the task state "Received"
• F. defining a Wait Condition in the dependency, which is configured with no delay duration

Identify the sequence of high-level activities that are performed in a typical telecommunications service provider environment where Order Management is implemented.

• A. Order Entry and Validation in the CRM system; Order Decomposition and Orchestration in the Order Management system -> Resource Allocation in the Inventory system;
  Resource Activation in the Activation system; Resource Billing in the Billing Management system
• B. Order Entry and Validation in the CRM system; Order Decomposition and Orchestration in the Order Management system -> Resource Billing in the Billing Management system;
  Resource Activation in the Activation system; Resource Allocation in the Inventory system
• C. Order Entry and Validation in the CRM system; Order Decomposition and Orchestration in the Order Management system -> Resource Activation in the Activation system;
  Resource Allocation in the Inventory system; Resource Billing in the Billing Management system
• D. Order Entry, Validation, Decomposition, and Orchestration in the Order Management system; Resource Allocation in the Inventory system -> Resource Activation in the
  Activation system; Resource Billing in the Billing Management system
• E. Order Entry, Validation, Decomposition, and Orchestration in the Order Management system; Resource Billing in the Billing Management system -> Resource Activation in the
  Activation system; Resource Allocation in the Inventory system

Identify two perspectives in Design Studio and Eclipse that can be used to model cartridge entities and develop XQueries.

• A. Java Perspective
• B. Cartridge Perspective
• C. Studio Design Perspective
• D. Debug Perspective
• E. Studio Environment Perspective