Database Management Systems

PLPIFSC is the database used to view inforce scorecard changes to policies. This database stores historical scorecard data and changes, allowing users to track modifications made to inforce policies over time. The other options (PLPDATA and PLPINFSCA) are related databases but PLPIFSC is specifically designated for scorecard change tracking.

Android's built-in platform database engine is SQLite, which is lightweight and embedded directly within the OS. Other relational databases like MySQL, Oracle, DB2, and SQL Server are typically enterprise database engines used on servers, not locally embedded in standard Android environments.

The correct answer is A because in BlackBerry Java development, SQLite database classes are located in the net.rim.device.api.database package. Option B is incorrect because 'sqlite' in lowercase is not part of the official package name. Options C and D are wrong because storage is a different API and SQLite in uppercase is not the correct package naming convention.

The correct answer is C because BlackBerry Device Software 6.0 specifically uses SQLite version 3.6.21. This version was integrated into the BlackBerry OS at that particular release. Options A, B, and D represent different SQLite versions that were not used in this specific BlackBerry OS version.

The correct answer is A because RMS (Record Management System) is the MIDP (Mobile Information Device Profile) API for persistent data storage in Java ME applications, and it stores data in record stores. Option B is wrong because RMS uses a proprietary record-based format, not traditional file systems. Option C is incorrect because RMS is not a relational database system. Option D is wrong because runtime stores are a different BlackBerry persistence mechanism.

The correct answer is B because SQLite databases are stored as a single relational database file on disk. This is SQLite's defining characteristic - it's a serverless, zero-configuration database that stores the entire database (tables, indexes, data) in one file. Option A is incorrect because SQLite doesn't store Java objects directly. Option C is wrong because while serialization is used internally, the external format is a database file. Option D is incorrect because 'dbms file' is not a standard term.

The correct answer is True because I/O operations on data warehouses are computationally expensive due to the massive volume of data involved. Data warehouses typically store terabytes to petabytes of historical data, and reading or writing this much data requires significant time and resources. The expense comes from disk I/O, network transfer, and processing overhead.

Oracle Enterprise scheduling includes CONTROL-M (external enterprise scheduler), DBMS_JOB (legacy package), and DBMS_SCHEDULER (modern package introduced in 10g). All three can be used for scheduling in EIP (Enterprise Integration/Oracle) databases.

Oracle SQL performance tuning can leverage hints to direct the optimizer, stored outlines to stabilize execution plans, and dynamic parallelism to speed up execution. Because all three techniques are valid methods to optimize simple or complex SQL statements, the choice containing all options is correct.

In a RAC environment, proper SQL logging requires instance number, SID, and serial# to uniquely identify the session and instance generating the log. RAC has multiple instances, so all three identifiers are necessary to trace logs to the exact source. Missing any identifier makes it impossible to determine which instance or session generated a particular log entry.

EIP database supports multiple scheduling tools: CONTROL M (external enterprise scheduler), DBMS_JOB (legacy Oracle package), and DBMS_SCHEDULER (modern Oracle scheduler). The choice depends on specific requirements, but all three are valid options for scheduling jobs in the EIP environment.

Simple SQL performance can be optimized using multiple techniques: dynamic parallelism (parallel execution), hints (directives to optimizer), and stored outlines (preserving execution plans). The effectiveness depends on the specific SQL statement and environment. All three methods are valid optimization strategies.

The PRIMARY goal of logging is debugging and troubleshooting during development and testing, not production performance monitoring. In production, you use tools like AWR, ASH, and SQL Trace for performance issues. The statement incorrectly claims production performance identification is the PRIMARY goal of logging.