最新的Oracle Communications BRM Elastic Charging Engine 2017 Implementation Essentials - 1z0-321免費考試真題

A. dm_oracle was started as root. You do not have to start the process as root.

B. Port 12345 is not available for dm_oracle because it is being used by another process when dm_oracle was started.

C. Port 12345 is not available for dm_oracle. This port is always used by the Connection
Manager (CM).

D. dm_oracle is missing its configuration file and, therefore, cannot connect to any port.

A. PCP

B. Radius

C. INAP

D. Diameter

E. CAMEL

A. Ready

B. Redeemed

C. Locked

D. Created

E. Frozen

F. Duplicate

A. Install the new BRM files. Update the BRM database. Redeploy customizations.
Implement new features.

B. Install the new BRM files. Deploy a new BRM schema. Install and run Oracle Data
Integrator (ODI) to extract, transform, and deploy data in the new database schema.
Redeploy customizations. Implement new features.

C. Enable the auto-upgrade function, so that when the new version is detected, it will be downloaded and applied to the current BRM instance automatically. Check log files on a regular basis to detect potential errors to be fixed.

D. Install the new BRM files. Deploy a new BRM schema. Install and run Oracle
GoldenGate to synchronize data between the previous and the new schema. Redeploy customizations. Implement new features.

A. PCM_OP_PYMT_APPLY_FEE calls the PCM_OP_PYMT_POL_APPLY_FEE policy
opcode to perform custom checks before the failed payment fee is applied.

B. PCM_OP_PYMT_APPLY_FEE calls PCM_OP_BILL_REVERSE to reverse suspense
payments.

C. PCM_OP_PYMT_APPLY_FEE calls PCM_OP_BILL_REVERSE_PAYMENT to apply
reversal payments.

D. PCM_OP_PYMT_APPLY_FEE calls PCM_OP_ACT_USAGE to create the payment fee event to be processed.

E. PCM_OP_PYMT_APPLY_FEE calls PCM_OP_PYMT_COLLECT to apply payment fees to customer accounts.

A. In the BRM_Home/sys/data/config directory, update the config_lifecycle_states.xml file, and then run the load_config utility to commit the change in the database.

B. Open the Service Life Cycles application, select New, enter description and name, and then enter your custom transitions state. Save and publish the change to the BRM database.

C. Read the /config/lifecycle object by using the testnap utility, update the generated file with your new states and transitions state, and commit the change to the database by using testnap again.

D. Using Pricing Design Center (PDC), open the Setup tab, click the Service Life Cycles link, select New, enter description and name, and then enter your custom states and transitions state. Save and publish the change to the BRM database.

A. Rated Event Formatter

B. NoSQL

C. Customer Updater

D. Rated Event Publisher

E. BRM Gateway

A. Field Type and Array Identifier

B. Nesting Level and Array Identifier

C. Field Number and Field Length

D. Element Identifier and Nesting Level

E. Nesting Level and Element Identifier