Database Management Systems

AWR (Automatic Workload Repository) data is stored in the SYSAUX tablespace in Oracle 10g and later. SYSAUX was introduced specifically to relieve the SYSTEM tablespace of auxiliary data like AWR statistics, making option C correct. SYSTEM is for core dictionary data, USERS for user objects.

Transparent tables in ABAP Dictionary have a 1:1 relationship with database tables - same name, same fields, same structure. Pooled and Cluster tables store multiple logical tables in fewer database tables. Views are virtual tables based on queries, not physical 1:1 mappings.

In ABAP Dictionary, standard data classes are Master Data (master records), Transaction Data (transactional documents), Organization Data (customizing/organizational units), and System Data (system configuration). 'Project Data' is not a standard data class, making option C the correct answer to the negative question.

In SAP ABAP, transparent tables are physically created in the underlying database when you activate them in the ABAP Dictionary. The activation process generates and executes the DDL statements that create the actual database table structure. Simply creating the table definition without activation does not create the physical table.

IMS databases have specific structural limits: maximum 15 levels in the hierarchy, 255 segment types, and 1000 fields per segment. These constraints ensure database performance and manageability. Option C correctly states these limits, while other options incorrectly mix up the numbers.

PROCOPT L loads new databases, I inserts segments, and R replaces existing segments. The LS option combines Insert and Replace capabilities, allowing both adding new data and updating existing records. This dual functionality makes LS the correct choice when you need both insert and replace operations.

Android stores SQLite databases in the app-specific directory /data/data//databases/. This path includes the package name to ensure each app's databases are isolated and secure. The databases directory is automatically created by the Android system for each app's private data storage.

Android security model dictates that application data, including SQLite databases, is stored in the application's private internal storage directory and is inaccessible to other apps by default.

While SQLiteOpenHelper is the recommended way to manage database creation and versioning, you can directly call openOrCreateDatabase() method available on the Context class to create or open a database without using SQLiteOpenHelper. However, this approach lacks automatic version management and upgrade helpers.

SQLite3 in Android is implemented as a compact C library that's included as part of the Android software stack. This is correct - SQLite is written in C and embedded into Android through JNI (Java Native Interface). It's not a Java library or C++ library.

When data doesn't need to be shared between applications, you can use SQLite database directly without implementing a ContentProvider. ContentProviders add overhead and are only necessary for cross-app data sharing.

Android provides multiple mechanisms for sharing persistent data between processes: Files (shared via file system or FileProvider), SQLite databases (via ContentProvider), and Android Properties (SharedPreferences - though primarily intra-app, can be made accessible). All three represent valid persistent data storage mechanisms.

Content providers support multiple modification operations: insert() for adding new records, bulkInsert() for batch insertion, update() for modifying existing records (including batch updates), and delete() for removal. The statement correctly identifies that content providers can be modified by adding records, adding values to existing records, and batch updating.

PCTFREE specifies the percentage of space reserved in each block for row expansion. Specifying a large PCTFREE prevents row migration by ensuring sufficient space remains for updates that increase row size. PCTUSED controls when blocks return to free list, INITTRANS controls concurrent transaction slots, and storage sizes affect allocation not migration.