Database Management Systems

Dimension tables must be loaded first because fact tables contain foreign keys that reference dimension tables. Loading dimensions before facts ensures referential integrity - you can't reference a dimension record that doesn't exist yet.

Informatica, DataStage, and Ab Initio are all ETL (Extract, Transform, Load) tools used for data integration. BusinessObjects and Cognos are BI tools, Hyperion is planning software, Oracle Builder isn't a standard ETL tool, and MicroStrategy is a BI platform.

Business Objects provides additional join types beyond standard SQL joins. The shortcut join is a BO-specific optimization that bypasses intermediate tables. Equi joins and theta joins (based on non-equality conditions) are standard, but the inclusion of shortcut join makes option B correct as it uniquely identifies BO's contribution.

Business Objects is classified as ROLAP (Relational OLAP) because it works directly with relational databases rather than pre-aggregated multidimensional cubes. MOLAP uses specialized multidimensional structures, while HOLAP combines both approaches. BO's universe-based queries against RDBMS place it in the ROLAP category.

In Business Objects, a repository is a centralized storage location that contains all the BO environment's assets including universes, reports, users, and security settings. It is not merely a data type or data structure, but the complete persistent storage system. Options A and B are incomplete definitions.

Degrafa is a declarative graphical framework for Flex and AIR applications that allows developers to create graphics using MXML or ActionScript. It provides a way to define vector graphics, shapes, and complex visual elements programmatically. Data visualization is just one application of Degrafa, not its fundamental definition.

All three factors are crucial when designing information visualization: the nature of the task determines visualization type, the workflow affects user interaction patterns, and data volume impacts performance and rendering choices. Ignoring any of these can lead to ineffective visualizations.

A WorkPool in PEGA is a collection of similar Work Objects that share common characteristics and are processed together. WorkGroups are organizational groupings, not collections of work objects. The WorkPool helps in managing and routing similar types of work items efficiently.

A WorkPool in Pega is a collection of similar Work Objects grouped together for organizational and routing purposes. It allows related work items to be managed collectively. WorkGroups are collections of users, not work objects. ClassGroup refers to Pega class groups, which is a different concept entirely.

This question asks which statement is FALSE. Statement C is false because a Work Pool is not a storage entity - it is a logical grouping mechanism. Work objects are stored in the database, not in the Work Pool itself. Statements A, B, and D are true: Work baskets ARE instances of Data-Admin-WorkBasket, Work lists relate to operators, and Access roles should be isolated per application.

In the Work Object Model, the correct hierarchy is Folder (highest level container), Cover (groups related work objects), and Basic (individual work items). This hierarchy supports efficient organization and management of related work.

The statement is false. Process Commander uses a proprietary database architecture, not an open one. While it does support Microsoft SQL Server, Oracle, and IBM DB2, the architecture itself is not 'open' - it uses Pega-specific storage mechanisms and schemas.

A class group causes PRPC to store instances from multiple concrete classes sharing a common key format in a single database table. This is a database optimization technique that reduces table proliferation while maintaining logical separation at the application level.

Database Management System (DMS) implementations like DMS 1100 and DMS II are based on the network database model. They do not conform to relational or hierarchical models.

A Data Item is the basic unit of a record, representing the smallest individual field or attribute within a database structure. Data items are the atomic building blocks that define what specific pieces of information can be stored - like a name field, date field, or numeric value. This contrasts with Record Type (the structure definition) or Record Occurrence (the actual instance with values).