A retail company's reporting performance is degrading due to a complex snowflake schema for its product dimension, which involves four separate tables (Product, Sub-Category, Category, Department). Report authors find it difficult to navigate and joins are inefficient. As the metadata modeler, what is the most effective approach in Framework Manager to resolve this for business users?
A data modeler observes that a report showing Sales Revenue by Salesperson and Branch is producing inflated revenue figures. The model joins Salespersons to a Sales Fact table and also joins Salespersons to a Branch dimension. Each Branch has multiple salespersons, and each salesperson can have multiple sales. This structure represents a classic fan trap. Which is the most appropriate method to resolve this trap within Framework Manager?
A BI architect is designing a new Framework Manager project that will source data from two distinct systems: a corporate Oracle data warehouse for sales information and a departmental SQL Server database for marketing campaign data. To ensure model clarity, maintainability, and security, which of the following are considered best practices for organizing the project? (Select TWO)
A healthcare provider needs to build a Framework Manager model for analyzing patient outcomes. The security requirements are stringent and complex, based on a user's role and their assigned medical facilities. **Data Structure:** - A `PatientEncounters` fact table contains sensitive patient data and a `FacilityID`. - A `Doctors` dimension table includes `DoctorID` and `DoctorName`. - A security table named `DoctorFacilityAccess` maps `DoctorID` to the multiple `FacilityID`s they are authorized to access. **Security Requirements:** 1. A logged-in user, who is a doctor, should only see patient data for the facilities they are assigned to in the `DoctorFacilityAccess` table. 2. The user's `DoctorID` is available via a session parameter `loggedInDoctorID` populated from the authentication source. 3. The solution must be scalable and avoid hard-coding values. It should be applied centrally to a security group named `DoctorGroup`. Which of the following represents the most robust and maintainable implementation of this row-level security requirement?
True or False: In Framework Manager, changing a query item's 'Usage' property from 'Attribute' to 'Fact' will automatically change its 'Regular Aggregate' property to 'Sum'.
A model contains a time dimension with keys for Day, Month, and Year. This dimension joins to a Sales fact table with a `Day_Key` and a Sales Forecast fact table with a `Month_Key`. Without proper configuration, queries combining sales and forecast data will cause the monthly forecast values to be repeated for every day of the month, leading to incorrect summaries. Which feature must be configured on the time dimension query subject to prevent this?
A report that joins the 'Customer' and 'Sales' query subjects is unexpectedly generating a cross-product (Cartesian join) instead of the expected inner join, causing extremely long query times and incorrect results. What is the most likely cause of this issue within the Framework Manager model?
A BI team needs to implement dynamic filtering based on a user's region and also support multi-lingual report titles. For example, a filter should be `[Region] = 'USA'` for one user, and a report title should be 'Sales Report' for English users and 'Rapport des Ventes' for French users. Which Framework Manager features are best suited to manage these lists of values centrally? (Select TWO)
A logistics company is modeling shipment data. The model contains a `Shipments` fact table (at the package level) and dimension tables for `Origin Port` and `Destination Port`. Analysts need to report on the number of shipments between any two ports. However, the `Origin Port` and `Destination Port` dimensions are structurally identical, based on the same `Ports` database table. This is a classic role-playing dimension scenario. What is the recommended modeling technique in Framework Manager to handle this?
What is the primary advantage of creating a stand-alone calculation in Framework Manager's business view, as opposed to embedding the calculation logic directly within a model query subject?