Database Management Systems

The Oracle Inventory module is comprehensive: it defines items (part numbers with attributes), models organization and warehouse structures, and tracks perpetual inventory transactions. Option D correctly encompasses all these functions.

Oracle Inventory supports multiple replenishment methods including Replenishment Counting, Kanban, and Min-Max Planning. MRP is a separate planning methodology, and Safety Stock is a setting, not a replenishment method per se.

Metadata is defined as "data about the data" - information that describes other data's characteristics, structure, or context (like file size, creation date, column names). It is not machine-level data (raw bits), not just characteristics (a subset), and not relationships between data (which would be schema/foreign keys). Option A is the standard definition.

Dimension tables store descriptive attributes about business entities, providing context for facts in the fact table. They contain relatively static data like customer names, product categories, or geographic regions. Option A incorrectly describes measures (not dimensions), while option C describes fact tables which contain numeric additive data.

Fact tables store quantitative numerical measurements (facts) and foreign keys that link to dimension tables. Each row typically represents a business event or transaction. Option A is incorrect because fact tables use foreign keys (not primary keys) to reference dimension tables. Option C describes a variation but doesn't capture the essential structure.

In MicroStrategy schema design, Attributes define descriptive data elements, Facts contain numerical metrics for analysis, and Functions/Operators provide calculation capabilities for data manipulation. These three are fundamental schema objects. Filters are report-level objects used to restrict data display, not schema objects.

A complete MicroStrategy BI architecture requires source systems (operational databases), data warehouse (central repository), metadata (definitions and mappings), and MicroStrategy applications (reporting interface). All four components are essential for the full architecture.

View Filters are applied at the report level after data retrieval, allowing filtering without affecting the warehouse query. Report Filters apply at the warehouse level (in the WHERE clause), Prompts enable user selection, and the question specifically asks for report-level filtering.

MicroStrategy OLAP Services provides three key capabilities: adding objects to report definition without displaying them (option A), drag-and-drop without new SQL queries (option B), and support for derived metrics with View Filters (option C). All three are features of OLAP Services.

VLDB properties in MicroStrategy are performance optimization settings that allow customization of generated SQL, can be applied at database, report, or metric levels, and help improve report performance by controlling how queries are executed against large databases.

Pega automatically maintains history tables for work items (History-Work-), configurations or data instances (History-Data-), and rule modifications (History-Rule-). Therefore, history records are created across all of these categories, making the options specifying individual classes too narrow and All of the Above correct.

The Rule Instance Cache is an in-memory cache that stores the XML representation of frequently accessed rules to improve performance. It caches the rule definition (XML), not the generated code or instantiated objects. This is distinct from First Use Assembly cache which caches generated Java code.

Pega stores the serialized XML or JSON representation of a rule or work instance in a binary large object (BLOB) column named pzPVStream. Other options like pzInsStream, pzObjStream, and pzRefStream are incorrect column names that do not store the main instance BLOB payload.

Object-level locks are higher-level constructs that persist longer than database locks, specifically designed to prevent concurrent modifications by multiple users. Database locks are lower-level, shorter-duration mechanisms for maintaining data integrity at the storage level.

The Aggregator stage performs all three functions: it classifies incoming data into groups based on key specifications, computes aggregate functions (sums, counts, averages, etc.) for each group, and applies various summary functions to the grouped data.