Oracle Communications Billing and Revenue Management System Administrator Set 2

Loglevel ✘ Path and filenames of FM libraries ✘ Database, hostname, and port number for the DM ✘ File path and name ofpinlog file ✔ Port number for the CMMP ✔

Path and filename of Translation Manager shared libraries ✘ Username and password for accessing external systems ✘ Queuing manager parameters ✘ Hostname and port number of the CM connecting to this DM ✔ Database number for the DM ✔

A valid order for starting the cm, dm_oracle and eai_js processes is to first start the eai_js, then the cm, and

finally the dm_oracle ✘ Portal processes must all be started before you can run any Portal applications ✘ For Portal running on a Windows platform, checkserv can be used to determine if a service is up andrunning ✘ The database needs to be up and running prior to starting any Portal processes ✔ Process ID for the running process is noted in the .pid file ✔

One cannot extend the set of fields for an existing class; a new class has to be created ✘ Fields in a storable class can span more than one database table ✘ Every storable class has a unique POID ✘ All storable classes are defined with a backslash (\) ✔ None of the above ✔

AnFlist is an instance of a storable class in the database ✘ Portal CM and DM can only interpret data inFlist format ✘ When using PortalOpcodes, all input and output data must be in Flist format ✘ A and B ✔ B and C ✔

1 PIN_FLD_ADDRESS STR [0]123 Main Street ✘ 1 PIN_FLD_ADDRESS STR123 Main Street ✘ 1 STR PIN_FLD_ADDRESS [0] 123 Main Street ✘ 1 STR PIN_FLD_ADDRESS123 Main Street ✔ None of the above ✔

PIN_FLDT_ENUM ✘ PIN_FLDT_POID ✘ PIN_FLDT_CHAR ✘ PIN_FLDT_ARRAY ✔ PIN_FLDT_DECIMAL ✔

revision level, object type, object ID, database number ✘ Object type, database number, object ID, revision level ✘ Object type, object ID, database number, revision level ✘ database number, object type, object ID, revision level ✔ revision level, database number, object ID, object type ✔

Every element of an array can contain multiple fields ✘ Element IDs for an array do not have to be incremental values ✘ For performance reasons, nesting level for asubstruct should be limited ✘ An array can be described as a collection ofsubstructs ✔ None of the above ✔

Any field can be encrypted ✘ Encrypted fields will not be automatically decrypted when they are retrieved ✘ A field with the permission Prohibited implies that the field cannot be edited after a storable object has beencreated ✘ When auditing is enabled for a field, shadow objects are created and stored in the audit tables ✔ An example of a field with the Prohibited permission is PIN_FLD_POID ✔