IBM Cognos BI Fundamentals

A snowflake schema normalizes dimension tables into multiple related tables to reduce redundancy and save storage space. Unlike star schemas where dimensions are denormalized, snowflake schemas break down dimensions into hierarchical levels (e.g., product → product category → product type). Option A incorrectly suggests facts are normalized (they're not - facts remain denormalized). Option B is wrong because fact and dimension tables are not joined together in 3NF - only dimensions are normalized.

When creating joins in Framework Manager, you must validate the model for loops (circular relationships that create infinite query paths) and fan traps (ambiguous many-to-one relationships through multiple paths). These structural issues cause incorrect query results or performance problems. Option A is wrong - cardinality can and should be specified. Option B is nonsense. Option D is incorrect - dimension tables can be joined.

Dimensions contain descriptive attributes that provide context for facts in the data warehouse. They are subject-oriented (organized around business entities like customer, product, time) and non-volatile (data doesn't change once loaded). Options A and D are wrong because dimensions don't contain facts. Option B is incorrect as dimensions contain their own descriptive data, not primarily data about other dimensions.

A determinant in Framework Manager defines a set of attributes that uniquely determine other attributes, preventing double-counting in query results. When you group by the determinant, Framework Manager knows how to handle the dependent columns correctly. Options B and C are wrong - determinants are not joins or functions; they're metadata about data dependencies that guide query generation.

Cognos functions include mathematical, string manipulation, date/time, and aggregate functions that enable complex calculations within reports and queries. These functions are available across multiple Cognos components, including Report Studio, Query Studio, Analysis Studio, and Framework Manager. Options B, C, and D are incorrect because functions are not limited to any one tool or purpose like bursting.

A chart is a visual/pictorial representation of data that makes patterns and trends easier to identify than raw numbers. Charts in Cognos can be created in Report Studio, Query Studio, and Analysis Studio using data from single or multiple queries. Options A, C, and D are incorrect because charts are not limited to specific tools or data sources - they're a general visualization method.

Report Studio provides multiple explorers for different design tasks: Page Explorer for layout design, Query Explorer for defining data queries, and Conditional Explorer for setting up conditional formatting and variables. These are three core explorers available in Report Studio. Option B is wrong because Internet Explorer is a web browser, not a Report Studio component. Option C is missing Page Explorer.

Cardinality in Framework Manager defines the numerical relationship between two tables (1:1, 1:N, N:1, or N:N) regardless of table type. It can represent relationships between fact and dimension tables (common in star schemas), between dimension tables (when dimensions relate to each other), or between any other tables in the model. Cardinality affects how Framework Manager generates SQL and handles joins. Option D is incorrect because cardinality is defined per relationship, not by data source.

Cognos report scheduling is flexible - you can create recurring schedules, specify multiple output formats (PDF, HTML, Excel, CSV), override outputs to keep version history, and modify or delete existing schedules. All of options A-D are incorrect because they state you cannot do things that are actually possible in Cognos. The correct answer is E because none of the restrictions listed are true.

Cognos Report Studio provides multiple data container types for displaying data: Lists show tabular data, Crosstabs display matrix/pivot tables, Charts create visual representations, and Conditional Blocks show content based on specified conditions. All four listed options are valid data containers in Cognos, making "All the above" the correct answer.

Report Studio includes built-in validation features that allow report authors to check for errors such as missing data items, incorrect calculations, or layout issues before running the report. This validation capability is accessible directly within the Report Studio interface. The other options are incorrect - validation does not require external scripts or macros, and Query Studio does not provide comprehensive validation for complex reports.

Framework Manager supports publishing packages in multiple languages, allowing users to create reports in different languages based on locale preferences. This multi-lingual capability is a standard feature that works with the same package structure. The statement is true because Framework Manager is designed to handle localization and multi-language requirements.

A cardinality of 1...n to 1...n represents a many-to-many relationship where each record in one table can relate to multiple records in the other table, and vice versa. In database modeling, this typically requires a bridging table or junction table to properly implement the relationship. The 'n' notation indicates multiple possible matches on both sides.

OLAP (Online Analytical Processing) structures are designed for fast analysis of multidimensional data from multiple perspectives. While OLAP cubes can aggregate data from various sources for near real-time analysis, option C best describes their core analytical capability. Options A and B describe traditional dimensional modeling, while option D describes table join configuration, not OLAP's defining characteristic.

In Framework Manager, a Namespace serves as a container that groups related objects and provides a unique naming context to prevent naming conflicts. Models, Query Items, and Query Subjects are objects that reside within namespaces. The Namespace is the organizational structure that ensures object names remain unique within their scope.

Report Studio authors access the runtime version (published package) of a Framework Manager model, which contains the query subjects and metadata ready for report creation. This published package is what Report Studio connects to, not the development model directly. The runtime package contains the finalized model structure optimized for querying.

When importing metadata in Framework Manager, non-indexed numeric query items are automatically assigned a Usage property of 'Fact' because numeric values without indexes are typically used for aggregation (sums, averages) in reporting. Indexed numeric values would be 'Identifier', and text values would be 'Attribute'. This default behavior helps modellers quickly organize their model.

Cardinality of 0...n means the relationship is optional (0 or more records may exist) and Framework Manager generates an outer join to preserve all records from the primary table even when no matching records exist in the related table. An inner join would only return matching records, while a union combines result sets. The '0' indicates optionality, which requires an outer join.

The SQL shows a SELECT statement with two tables in the FROM clause but no JOIN condition or WHERE clause linking them together. This syntax produces a Cartesian product (cross join), where every row from the Manager table is combined with every row from the Product table. Cross joins are rarely intentional in reporting and typically indicate missing join conditions.

Query Studio is a simplified ad-hoc reporting tool designed for basic queries without advanced interactivity. The prompt creation functionality is only available in Report Studio, which is the more advanced report authoring tool. Query Studio focuses on simple list and crosstab reports without parameterized prompts.