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 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.

C. 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.

D. 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.

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

A. Debit 10 dollars for the monthly recurring fee and credit 5 cents per SMS message.

B. Implement a counter that tracks the number of SMS messages sent and then credit this counter back to the usage charge.

C. Credit 10 dollars for the monthly recurring fee and debit 5 cents per SMS message.

D. Credit the included balance of SMS messages and debit the usage charge.

E. Debit the included balance of SMS messages and credit the usage charge.

A. pin_bi11_accts needs to be restarted in order to bill all accounts including those billed previously.

B. pin_bi11_accts needs to be restarted with the -retry option.

C. pin_bi11_accts needs to be restarted in order to bill any remaining unbilled accounts.

D. You need to identify which accounts have not been billed and bill them manually by providing a file with the account POID by using the -from_file option.

A. If your system has multiple configuration les for event notification, you must mergeconfiguration files every time even if only one file has changed.

B. You must merge configuration files for event notification if you are enabling event notification for the first time and your system has multiple configuration files for event notification.

C. If your system has multiple configuration les for event notification, you do not need to merge the configuration files if only one file has changed.

D. Instead of merging the configuration files every time, you can use load_pin_notify to extract the current configuration from the database.

E. You must merge configuration files for event notification if you want to execute multiple opcodes when an event occurs.

A. The event will not trigger any autobilling because autobilling is enabled only in the last
10 days of the cycle.

B. The event will be included in the previous cycle because billing has not been run.

C. The event triggers partial billing for the account and final billing will be performed by the scheduled bill run.

D. The event triggers final billing for the account because delayed billing is not enabled.

E. Elastic Charging Engine (ECE) will not rate the event until either partial or final billing has been completed.

A. ECS sends the Diameter RAR message directly to the network element.

B. ECS puts a message in the notification queue. The Diameter Gateway reads the message and converts it to a Diameter RAR message.

C. ECS sends the Diameter RAR message to the Diameter Gateway, which forwards it to the network element.

D. The re-authorization request is sent to the network element as part of the next Diameter
CCR-Update message.

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

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

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

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

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

A. The CM will report the average latency of PCM_OP_CUST_COMMIT_CUSTOMER opcode calls every 10 opcode calls, every 20 minutes, or every 30 CM connections whichever occurs first.

B. The CM will report the average latency of PCM_OP_CUST_COMMIT_CUSTOMER opcode calls every 10 minutes, every 20 opcode calls, or every 30 CM connections whichever occurs first.

C. The CM will report the number of times the latency of a successful
PCM_OP_CUST_COMMIT_CUSTOMER opcode calls for each of the following four buckets: <10 ms, 10 to 20 ms, 20 to 30 ms, >30 ms at the end of each CM connection.

D. The CM will report the number of times the latency of a successful
PCM_OP_CUST_COMMIT_CUSTOMER opcode calls for each of the following three buckets: <20 ms, 20to 30 ms, >30 ms every 10 minutes.