Database Management Systems

WorkPool in PEGA is a logical grouping mechanism that collects similar Work Objects together based on shared characteristics or criteria. This organization helps in managing and tracking related work items efficiently. WorkGroups and ClassGroups are different organizational structures in PEGA.

Report purge in BusinessObjects refers to the deletion of data retrieved by the query. When a report is purged, the data rows are removed but the report structure (layout, formatting, formulas) remains intact. This is different from deleting the entire report structure or refreshing it with new data. Option B correctly describes this.

All three methods (A, B, C) represent valid ways to apply restrictions in database and Business Intelligence contexts. Conditional selects with database functions (A), where clauses on object properties (B), and restriction sets forcing row-level where clauses (C) are all standard techniques for data restriction. Option E correctly identifies that all these approaches are valid.

Detail objects in Business Objects universe design are always attached to dimensions and provide additional descriptive information about those dimensions. They cannot exist as standalone objects (Option C) or attach to measures (Option A). This is fundamental - dimensions are the core objects, and details elaborate on them with extra context.

SQL Server 2000 was codenamed Shiloh during its development. Yukon was the codename for SQL Server 2005, Mantis was unrelated to SQL Server, and Aurum was not associated with any Microsoft SQL Server release.

Views are virtual tables that hide underlying table structure while presenting data in a customized way. They support abstraction and can be updatable, making them ideal for allowing controlled data access without exposing base tables.

Performance monitoring is an ongoing operational activity in database administration, continuously tracking query performance, resource usage, and system health. The other options are one-time setup or design activities.

Security review occurs during the design phase when defining access controls, user permissions, and data security policies. The structure and storage phases focus on technical implementation, not security planning.

Metadata is data about data - it describes the structure, schema, and data dictionary but does not include actual user data values. Options A, B, C, and E all describe legitimate characteristics of metadata.

RDBMS procedural SQL extensions (PL/SQL, T-SQL) add programming constructs like conditionals and loops for procedural logic. Encryption, GUI widgets, threading, and network sockets are systems-level features outside SQL scope.

A mandatory 1:1 relationship often indicates insufficient attribute analysis - additional attributes may reveal why entities are separate or show they should be merged. This is a modeling smell suggesting incomplete analysis.

HTML tables are used to organize and display data in rows and columns, helping maintain proper formatting and structure on web pages. They were historically also misused for page layout before CSS became widely adopted. Option C describes this formatting purpose, though somewhat vaguely.

Business Intelligence encompasses all these aspects: the skills and technologies for decision-making (A), the architecture for decision support systems (B), and providing multi-temporal views of business operations (C). BI is a comprehensive discipline that integrates all these elements to support data-driven decision making.

A data warehouse has four key characteristics: it is subject-oriented (organized by major subject areas), integrated (consistent data standards), time-variant/temporal (captures historical changes over time), and non-volatile (data is read-only, not updated or deleted). Option D correctly lists all four properties.

An Operational Data Store (ODS) is subject-oriented (organized by business subjects), integrated (consistent data), current-valued (contains real-time or near-real-time data), and volatile (data is updated frequently). Unlike data warehouses, ODS systems support operational decision-making with current rather than historical data.