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

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

A. Multiple nodes with the same role can be defined in the topology file.

B. You need to define a JMX port in the topology file for each ECE node.

C. You cannot add a new node to the ECE cluster without first defining it in the topology file.

D. In the topology file, you define on which server a given ECE node will run.

E. You can define a specific tuning profile in the topology file for each ECE node.

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. Check the ECE Coherence cache using Coherence query language.

B. Check the /config/event_map object using Developer Center.

C. Check for confirmation in the Customer Updater log files.

D. Check for confirmation in the ECS log files.

E. Check for confirmation in the Pricing Updater log files.

A. Export the required pricing profile by using the ImportExportPricing utility. Remove the
Zone Modelling and Time Modelling capability entries from the exported file. Re-import the modified pricing profile by using the ImportExportPricing utility.

B. Export the required pricing profile by using the ImportExportPricing utility. Remove the
Zone Modelling and Time Modelling capability entries from the exported file. Re-import the modified pricing profile using Pricing Loader.

C. Log in to the PDC WebLogic server instance and modify the Time- and Zone-based configuration settings.

D. Export the required pricing profile by using the ImportExportPricing utility. Remove the
Zone Modelling and Time Modelling capability entries from the exported file. Re-import the modified pricing profile using Pricing Updater.

E. Remove the Zone Modelling and Time Modelling capability by using the Set-Up objectsconfiguration window in the PDC UI.

A. You need to extract pricing data from PDC into XML files so that it can be read by the Pricing Updater process at startup.

B. The Pricing Updater process reads the pricing data from the Pricing Design Center (PDC) database at startup.

C. The pricing data is loaded into ECE automatically.

D. You need to run ImportExportPricing to trigger PDC to send all pricing data to ECE.

E. You need to extract pricing data from PDC into ASCII flat files so that they can be read by the Pricing Updater process at startup.

A. Metadata

B. Setup Objects

C. Subscriber Data

D. Billing Data

E. Integration Data

A. pin_inv_accts generates the invoice data in XML format in the BRM database, then pin_inv_doc_gen calls the BI Publisher API to retrieve the XML data from the BRM and generates the invoice document.

B. pin_inv_accts calls the BI Publisher API directly and generates the invoice document.

C. pin_inv_accts generates the invoice data in HTML format in the BRM database, then pin_inv_doc_gen calls the BI Publisher API to retrieve the XML data from the BRM and generate the invoice document.

D. pin_inv_accts generates the invoice data in XML format in the BI Publisher database, then pin_inv_doc_gen calls the BI Publisher API to generate the invoice document.

E. pin_inv_doc_gen retrieves all the required information from the BRM database and generates the invoice document. pin_inv_accts does not need to be run when using BI
Publisher.