1z1-493 試験問題を無料オンラインアクセス

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 Activation in the Activation system;
  Resource Allocation in the Inventory 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, 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
• D.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
• E.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

You have a product specification that has an order component called Provisioning. You are now required to select order items to be included in this order component by implementing a condition that is based on order item properties. Consider that you do not want to impact other product specifications that also use the Provisioning function, that the decomposition rules apply to all product specifications, and that you do not want your logic to be dependent on the product specification name.
Given this scenario, where would you define the condition logic?

• A.in the product specification order component condition
• B.in the existing decomposition rule condition
• C.in the order item specification orchestration condition
• D.in the orchestration plan dependencies condition
• E.in the orchestration stage order component condition

While upgrading an existing cartridge to fit new requirements, you decide to change the task data of an existing task. Which two considerations should you take into account when performing this activity?

• A.Changing your task data will impact the order recognition rule even if you are not changing a creation task.
• B.To change the behavior of a task element, you will have to change the corresponding behavior at the order template level.
• C.Some of the elements in your task data must be edited in another task because they are inherited.
• D.Changing the task data could also change the task data of other tasks due to inheritance configurations.
• E.Adding new elements to your task data will add the same elements to its parent task data.

Why would you create a new composite cartridge?

• A.Because the composite cartridge feature is not included in OSM. It includes only compound or classic cartridges.
• B.to assemble a single solution in OSM from a collection of component cartridges
• C.to create multiple solutions in OSM for all composite cartridges
• D.to create a solution that always includes all the component cartridges present in the workspace
• E.to assemble a solution in OSM from a complete collection of all composite cartridges

You have the following process and subprocess configured in your OSM cartridge. The compensation strategy when a task needs to be re-evaluated is set to "Undo then Redo" for
TaskB and "Redo" for all other tasks. On the other hand, the compensation strategy when a task is no longer required is set to "Undo" for all tasks. OSM has just completed the execution of TaskD when a revision is submitted, which causes all tasks to be re- evaluated. Which two tasks will be executed with the Undo execution mode?

• A.TaskA
• B.TaskC
• C.TaskE
• D.TaskB
• E.TaskD