Database Management Systems

RDBMS is a system of tables and relationships (A). It uses SQL for retrieval and manipulation (C), and translates SQL queries into data operations (E). RDBMS doesn't automatically write efficient queries - the user must write them (B is false). Memory structures and processes describe instance architecture, not the RDBMS concept (D is false).

SQL indeed stands for Structured Query Language, which is the standard language used for managing and manipulating relational databases. The other options - Stable Query Language, Synchronous Query Language, and System Query Language - are incorrect acronyms that do not represent what SQL means.

In Entity Relationship Modeling, entities are represented by rectangles or boxes in ER diagrams. The term 'soft box' refers to this rectangular shape convention used to denote entities visually. Relationships are typically shown as diamonds, and attributes as ovals.

DATAFILEs are the physical operating system files that actually store the data on disk - they are tangible physical components of the database architecture. Logical structures like tables and segments ultimately map to these physical DATAFILEs for storage.

Oracle data dictionary views have three standard prefixes: USER_ (objects owned by current user), ALL_ (objects accessible to current user), and DBA_ (all objects in database - requires DBA privilege). ORACLE_ and SCHEMA_ are not valid prefixes for data dictionary views.

HASH partitioning distributes rows uniformly across partitions using a hash algorithm on the partitioning key. It's ideal when access patterns are unknown or when even data distribution is desired. RANGE requires logical ranges and LIST requires known discrete values.

A reference characteristic in SAP BW does not have its own SID or master data tables. Instead, it uses the SID table and master data tables of the characteristic it refers to. This design avoids data redundancy and maintains referential integrity.

Navigational attributes cannot be made navigational if the attribute-only flag is set, they can be used for aggregates, and cannot be converted back to display attributes without deleting data. Option D correctly states that once data is deleted, the attribute can be reverted to display status.

Compounded info objects require all component objects to be present in the cube. An attribute-only object cannot be used for compounding. An object cannot simultaneously be an attribute and compounding object. The total length is capped at 60 characters for database efficiency.

Every characteristic must be assigned to at least one dimension for proper organization. A characteristic can only belong to one dimension at a time. However, a single dimension can contain multiple characteristics. Line item dimensions are exceptions to normal dimension rules.

An ODS can be created with zero data fields (just key fields). Both characteristics and key figures are valid key field types. The 16-key-field limit is incorrect (ODS has no such fixed limit). Export data sources must be created manually, not automatically.

Documentum Content Server requires a three-layer foundation: the Operating System (Windows/Linux/Unix), a File System for content storage, and a Relational Database Management System (RDBMS) for metadata and object management. All three components are essential - Content Server cannot run without any of them.

In Documentum terminology, a Docbase (better known as a Repository) is where all Documentum objects are stored. The Repository uses both the RDBMS (for metadata/object definitions) and file storage (for actual content files), but the term 'Docbase' or 'Repository' refers to the complete logical storage unit.

In Documentum architecture, the Docbase Config object stores configuration and operational parameters for servers accessing the repository. This includes connection settings, server preferences, and runtime information.

A Documentum repository contains three core components: object type tables (defining custom types), type indexes (for querying), and content files (actual stored content). All are essential for repository operation.