Passing exam with 1z1-493 latest training materials

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

When defining a new stage of decomposition that decomposes order times by VPN site, you realize that you cannot model each site as an order component because you cannot estimate the number of sites at design time. How would you propose a solution to this situation?

• A. by modeling a decomposition rule with a logic that determines the target order component at run time, based on VPN site information
• B. by defining as many order components as it is needed to accept any possible combination of VPN sites
• C. by modeling as many stages of decomposition as the number of VPN sites that you expect to handle at run time.
• D. by using multi-instance order components with a pivot node that will generate at run time as many order components as the sites present in the order
• E. by defining a single order component with a component ID expression that generates distinct values for distinct sites

Which two OSM components are deployed in Oracle WebLogic Server?

• A. OSM server
• B. Design Studio IDE
• C. runtime database
• D. provisioning framework
• E. web clients

You have a cartridge that defines three stages of decomposition. The first stage contains order components that represent functions, the second stage contains order components that represent target systems, and the third stage contains order components that represent granularities. You want to define decomposition rules that always apply the same granularity to a function, independent of the target system that this function is communicating to. How would you design these decomposition rules such that it is easy to maintain them in the future evolutions of your system topology?

• A. a single decomposition rule with the function as the source order component and the granularity as the target order component
• B. a single decomposition rule that has only the target systems used by the function as source order components and the granularity as the target order component
• C. one decomposition rule for each target system, having this target system as the source order component and the granularity as the target order component
• D. a single decomposition rule that has all target systems as source order components and the granularity as the target order component
• E. one decomposition rule for each target system used by the function, having this target system as the source order component and the granularity as the target order component

An enterprise customer requests a high-speed broadband service at three different office locations, which are indicated in three CustomerAddress structures in the order data. This requires three requests to be submitted to the activation system to activate services at the three locations.
Considering a process-based order, which is the most efficient process modeling approach to send as many requests to the activation system as the CustomerAddress structures present in your order?

• A. Configure an XQuery in a task that sends a request to the activation system to publish as many messages as the CustomerAddress structures present in the order.
• B. Configure a single task that sends a request to the activation system with a Pivot Node based on the CustomerAddress structure.
• C. configure an XQuery in a task that sends a request to the activation system by setting
  CustomerAddress as the multi-instance indicator in the task context.
• D. Configure a counter in your order data and a loop in the process flow, such that the task is executed as many times as the CustomerAddress structures present in the order.
• E. Design the process, including as many tasks that send a request to the activation system as the maximum number of CustomerAddress structures.