I85PREP
⌘ K
MicroStrategy Developer study materials
MicroStrategy Developer study resources

MicroStrategy Developer practice questions

One question at a time. Build your MicroStrategy Developer understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Semantic Layer Modeling and Governed Definitions

In a MicroStrategy project, which object stores the business definition of a metric, including its aggregation function and formula, so that every report reuses the same logic?

  1. The metric object in the schema Correct answer.
  2. The warehouse fact table definition
  3. The user's personal My Reports folder
  4. The report filter of each dossier

Explanation

A metric is a schema-level object that holds the aggregation and formula definition, so all reports referencing it inherit the same governed logic. Report filters and personal folders are per-report or per-user artifacts and do not define metric behavior. The warehouse table only stores data, not the business aggregation rule.

Question 2Semantic Layer Modeling and Governed Definitions

A developer wants one attribute to be shared across several fact tables so that reports can drill consistently. Where should the attribute be created?

  1. As a filter qualification on each report
  2. Inside a single dataset in the dossier editor
  3. In the project schema, independent of any dataset Correct answer.
  4. As a derived column in each report's SQL

Explanation

Attributes created in the schema become reusable project objects that many reports and fact tables can reference, which keeps drill paths and element browsing consistent. Dataset-level or report-level definitions fragment the semantics and cause inconsistent results. Filters restrict data rather than define reusable entities.

Question 3Semantic Layer Modeling and Governed Definitions

Which schema object is used to define the hierarchical relationship between a parent attribute and a child attribute for drilling and aggregation?

  1. A custom group
  2. A consolidation
  3. An attribute relationship Correct answer.
  4. A prompt

Explanation

Attribute relationships define parent-child hierarchies in the schema and control how attributes drill and aggregate relative to one another. Consolidations group attribute elements into bands, custom groups filter elements, and prompts collect runtime input. None of those establish the parent-child hierarchy.

Question 4Semantic Layer Modeling and Governed Definitions

A report must display revenue at the region level even though the fact table is stored at the store level. What does the schema need so MicroStrategy aggregates correctly?

  1. A relationship from Store to Region with the appropriate attribute forms Correct answer.
  2. A filter that removes store-level rows
  3. A new metric that hard-codes region names
  4. A dossier selector on the store attribute

Explanation

Aggregation from store to region depends on the schema relationship that tells the engine how stores roll up to regions, together with the forms used to join and display. Without that relationship the engine cannot resolve the level correctly. Filters and selectors change what is displayed, not how roll-up is computed.

Question 5Semantic Layer Modeling and Governed Definitions

What distinguishes a fact object from an attribute in the MicroStrategy schema?

  1. Facts can only be numeric, while attributes can be numeric or text
  2. Facts must belong to a hierarchy, while attributes cannot belong to a hierarchy
  3. Facts are measurable data used in metrics, while attributes describe the context of those measurements Correct answer.
  4. Facts are stored only in the metadata, while attributes are stored only in the warehouse

Explanation

Facts represent measurable values that metrics aggregate, whereas attributes provide the descriptive context such as product, customer, or time. This separation is the core of the semantic model. The other statements misstate where objects live or which object supports hierarchies.

Question 6Semantic Layer Modeling and Governed Definitions

A developer needs a metric that returns the running total of revenue across the report's rows. Which metric feature should be configured?

  1. An OLAP function such as running sum Correct answer.
  2. A filter qualification on the metric
  3. A transformation applied to the metric
  4. A level (dimensionality) setting of Report level

Explanation

OLAP functions like running sum, rank, and percent-to-total operate across the result set and are configured on the metric itself. Level settings control the dimensionality of aggregation, transformations shift time, and filter qualifications restrict rows. None of those produce a running cumulative value.

Question 7Semantic Layer Modeling and Governed Definitions

A metric should always be calculated at the Customer level regardless of what attributes appear on the report. Which metric setting enforces this?

  1. The metric's subtotal set to enabled
  2. The metric's drill setting set to enabled
  3. The metric's dimensionality (level) set to the Customer attribute Correct answer.
  4. The metric's format set to a currency

Explanation

Setting the metric level to a specific attribute forces aggregation at that dimensionality, independent of the report's other attributes. Formatting, subtotals, and drill options affect presentation and navigation rather than the aggregation grain. This is how governed metrics guarantee consistent numbers across reports.

Question 8Semantic Layer Modeling and Governed Definitions

A developer wants to reuse a set of report filter conditions across many reports and update them in one place. What is the appropriate object?

  1. A metric filter qualification
  2. A dossier selector
  3. A standalone report filter saved as a schema object Correct answer.
  4. A custom group

Explanation

A report filter saved as a reusable schema object can be attached to many reports, and editing it updates all dependents. Metric filter qualifications are scoped to a metric, selectors are presentation controls, and custom groups define element sets rather than reusable filter logic.

Question 9Semantic Layer Modeling and Governed Definitions

What is the purpose of a consolidation in the schema?

  1. To merge two fact tables into one physical table
  2. To consolidate multiple projects into one metadata repository
  3. To group attribute elements into new bands that can be used like an attribute Correct answer.
  4. To combine two metrics into a single metric formula

Explanation

A consolidation creates a new attribute-like object by grouping existing attribute elements into bands, such as grouping regions into territories. It does not touch physical tables, merge metric formulas, or combine projects. It is a schema-level modeling object for reporting groupings.

Question 10Semantic Layer Modeling and Governed Definitions

A developer needs a reusable set of attribute elements defined by a saved condition, such as customers meeting a revenue threshold, to use across reports. Which object fits?

  1. A custom group Correct answer.
  2. A transformation
  3. A consolidation
  4. A fact

Explanation

A custom group defines a named set of attribute elements using conditions or banding and can be reused across reports. Consolidations group existing elements into bands without a condition on data, transformations shift time, and facts are measured values. Only the custom group expresses a reusable element set.

Question 11Semantic Layer Modeling and Governed Definitions

What does a transformation object enable in a MicroStrategy project?

  1. Translating attribute forms into another language
  2. Converting a metric to a different data type
  3. Changing the warehouse connection at run time
  4. Calculating metrics as of a different time period, such as year-to-date or same period last year Correct answer.

Explanation

Transformations define offset relationships in time, allowing metrics to be computed for periods like prior year or year-to-date. They do not change data types, translate forms, or switch warehouse connections. They are applied to metrics to produce time-shifted values.

Question 12Semantic Layer Modeling and Governed Definitions

A developer must ensure that a metric always returns the year-to-date value alongside the current value in the same report. What is the correct approach?

  1. Create a second metric that applies a year-to-date transformation Correct answer.
  2. Change the report's page-by to year
  3. Create a consolidation of the month attribute
  4. Add a filter that removes months after the current month

Explanation

Applying a year-to-date transformation to a metric produces the cumulative value, and placing both the base metric and the transformed metric on the report shows them side by side. Filters or page-by change what is shown rather than computing the cumulative value, and a consolidation groups elements.

Question 13Semantic Layer Modeling and Governed Definitions

Which object allows a developer to define a named, reusable subset of data rows that can be applied to reports, similar to a saved WHERE clause?

  1. A report filter saved as a schema object Correct answer.
  2. An attribute form
  3. A hierarchy
  4. A metric level

Explanation

A report filter saved in the schema acts as a reusable qualification applied to multiple reports, functioning like a governed WHERE clause. Metric levels control aggregation grain, attribute forms control display and joins, and hierarchies organize drill paths. Only the saved report filter restricts rows.

Question 14Semantic Layer Modeling and Governed Definitions

A developer creates a metric with the formula Sum(Revenue) and sets its level to the Region attribute. What happens when the metric is placed on a report that also includes Store?

  1. The metric aggregates at store level and ignores the region setting
  2. The metric returns only one row for the entire report
  3. The metric fails to execute because Store is not in the level
  4. The metric repeats the region-level value for every store in that region Correct answer.

Explanation

A metric fixed at the Region level aggregates at region and repeats that value for each store row in the region, which is the expected behavior of dimensionality settings. It does not fail, silently switch to store grain, or collapse the report to one row. This behavior is used to compare detail rows against a higher-level total.

Question 15Semantic Layer Modeling and Governed Definitions

What is the role of a hierarchy object in the MicroStrategy schema?

  1. To store the physical join between fact tables
  2. To set the aggregation function of metrics
  3. To translate attribute elements into multiple languages
  4. To define the drill path among related attributes Correct answer.

Explanation

A hierarchy organizes related attributes into a drill path, such as Country to Region to Store, so users can navigate levels consistently. It does not define physical joins, perform translation, or set metric aggregation. Those tasks belong to other schema objects.

Question 16Semantic Layer Modeling and Governed Definitions

A developer needs the same attribute to display a short description in reports while joining on a numeric ID. How should attribute forms be configured?

  1. Use a single form that concatenates ID and description
  2. Use a DESC form for display and an ID form as the key Correct answer.
  3. Disable all forms and rely on the warehouse column name
  4. Use only the ID form and let the engine display it

Explanation

Attribute forms separate the display value from the key used for joins and grouping, so a DESC form can display text while the ID form drives the relationship. Using only the ID would display numbers, concatenation breaks grouping, and disabling forms removes needed metadata.

Question 17Semantic Layer Modeling and Governed Definitions

Which statement best describes the metadata repository in a MicroStrategy project?

  1. It stores only user login credentials
  2. It stores the aggregated report results for fast retrieval
  3. It stores the raw fact data before aggregation
  4. It stores the schema objects and their definitions that reports reference Correct answer.

Explanation

The metadata repository holds the object definitions, such as attributes, metrics, and filters, that make up the semantic model. It does not hold raw fact data or pre-aggregated results, which live in the warehouse or caches, and it is not limited to credentials. The metadata is the source of governed definitions.

Question 18Semantic Layer Modeling and Governed Definitions

A report shows a metric value that is unexpectedly high because the same fact is counted twice across two fact tables. What schema issue is most likely?

  1. A missing or incorrect attribute relationship causing a fan-out join Correct answer.
  2. A prompt that defaults to all elements
  3. A metric format set to two decimal places
  4. A page-by on a low-cardinality attribute

Explanation

Double counting across fact tables usually stems from a join path that fans out rows, often because the relationship between attributes and fact tables is not modeled correctly. Formatting, page-by, and prompt defaults affect presentation or filtering, not row multiplication. Correct attribute relationships keep aggregation consistent.

Question 19Semantic Layer Modeling and Governed Definitions

What is the purpose of a derived metric in MicroStrategy?

  1. A metric that can only be used in one report
  2. A metric defined on the fly from other metrics without saving a new schema object Correct answer.
  3. A metric that is always stored in the warehouse as a column
  4. A metric that replaces the need for attributes

Explanation

A derived metric is created from existing metrics at the report or dossier level, allowing quick calculations without adding a permanent schema object. It is not a warehouse column, is not limited to one report by definition, and does not replace attributes. Governed metrics should still be used when reuse and consistency matter.

Question 20Semantic Layer Modeling and Governed Definitions

A developer wants a prompt that lets users choose which attribute to group by at run time. Which prompt type is appropriate?

  1. An attribute prompt Correct answer.
  2. A metric prompt
  3. A hierarchy prompt
  4. A value prompt

Explanation

An attribute prompt lets users select an attribute for grouping or filtering at run time. Value prompts collect literal values, hierarchy prompts select hierarchy elements for drill, and metric prompts select metrics. The attribute prompt is the one that changes the grouping attribute.

Question 21Semantic Layer Modeling and Governed Definitions

Why should a developer prefer a schema metric over a report-level calculation for a key business measure like gross margin?

  1. Schema metrics always run faster than report calculations
  2. Schema metrics are governed and reused, so every report applies the same definition Correct answer.
  3. Schema metrics bypass the warehouse entirely
  4. Report-level calculations cannot use arithmetic

Explanation

Placing a key measure in the schema makes it a governed definition that all reports reuse, preventing inconsistent calculations across teams. Performance and arithmetic capability are not the deciding factors, and schema metrics still query the warehouse. Consistency of business logic is the primary reason.

Question 22Semantic Layer Modeling and Governed Definitions

A dossier must let users switch between two governed metric definitions without editing the dossier. What modeling approach supports this?

  1. Create a custom group for each metric
  2. Create both metrics in the schema and expose them through a metric selector Correct answer.
  3. Create a single metric with a hard-coded value
  4. Add both metrics to the report filter

Explanation

Defining both metrics in the schema keeps them governed, and a metric selector lets users switch between them interactively. Hard-coding removes flexibility, filters restrict rows rather than choosing metrics, and custom groups define element sets. The selector is the presentation mechanism for choosing among governed metrics.

Question 23Semantic Layer Modeling and Governed Definitions

What does an attribute relationship's parent-child direction determine?

  1. How the child attribute aggregates up to the parent Correct answer.
  2. The display color of the attribute in reports
  3. The number of forms an attribute can have
  4. The warehouse connection used for the attribute

Explanation

The direction of the relationship tells the engine which attribute is the parent and how the child rolls up for aggregation and drilling. It does not control display color, form count, or connections. Correct direction is essential for accurate roll-up totals.

Question 24Semantic Layer Modeling and Governed Definitions

A developer notices that a metric returns null for some rows where data exists. Which modeling cause is most plausible?

  1. The metric format is set to a currency symbol
  2. The metric uses a Sum function
  3. The report has a page-by on the metric
  4. The metric's level references an attribute that is not related to the fact table Correct answer.

Explanation

If the metric level names an attribute that has no relationship to the fact table, the engine cannot resolve the value and returns null. Formatting, page-by placement, and using Sum are normal and do not cause nulls. The fix is to correct the relationship or level definition.

Question 25Semantic Layer Modeling and Governed Definitions

Which object would a developer use to define a reusable list of the top ten products by revenue that can be dropped onto multiple reports?

  1. A custom group Correct answer.
  2. A transformation
  3. A fact
  4. A database instance

Explanation

A custom group can define a set of attribute elements based on a condition such as top ten by revenue, and it can be reused across reports. Transformations shift time, facts are measures, and database instances define connections. The custom group is the reusable element-set object.

Question 26Semantic Layer Modeling and Governed Definitions

In a MicroStrategy project, which object type is used to define a reusable business calculation such as gross margin that report authors can place on any report without rewriting the formula?

  1. A report-level derived metric created inside a single report
  2. A schema metric object stored in the project metadata Correct answer.
  3. A filter qualification applied at run time
  4. A custom group defined on an attribute

Explanation

Schema metrics are stored in project metadata and are available to every report and dossier in the project, so the formula is defined once and governed centrally. Derived metrics exist only inside the report where they are created and cannot be reused elsewhere. Filters and custom groups restrict rows rather than define calculated values.

Question 27Semantic Layer Modeling and Governed Definitions

A developer is defining a fact and must decide the data type. Which consideration is most important for a fact that will be summed into a revenue metric?

  1. The fact should be numeric with sufficient precision to avoid rounding loss in aggregation Correct answer.
  2. The fact should be stored as text so formatting can be applied at display time
  3. The fact data type has no effect because metrics convert values at run time
  4. The fact should be an integer so that division operations truncate cleanly

Explanation

Facts feed metric aggregation, so a numeric type with adequate precision preserves accuracy when values are summed across many rows. Storing numeric measures as text prevents arithmetic aggregation, and integer-only storage discards fractional currency amounts. Metric formulas do not repair a poorly chosen fact type at run time.

Question 28Semantic Layer Modeling and Governed Definitions

A developer wants a single attribute named Customer to expose both a numeric customer ID for joins and a customer name for display. Which attribute form configuration accomplishes this?

  1. Define one form containing a concatenation of the ID and the name
  2. Define the attribute twice in the schema, once for ID and once for name
  3. Define a single form and let the report choose the column at run time
  4. Define two forms, one ID form used as the lookup key and one description form used as the display form Correct answer.

Explanation

Attribute forms let one attribute carry multiple columns, with one form designated as the ID form for lookup and join purposes and another as the display form shown to users. Concatenating values corrupts the join key, and duplicating the attribute creates conflicting definitions. Form selection is a design decision, not an automatic run-time choice.

Question 29Semantic Layer Modeling and Governed Definitions

Which statement describes the role of an attribute relationship in the MicroStrategy schema?

  1. It defines the security access a user has to attribute elements
  2. It specifies the physical table that stores the attribute's lookup values
  3. It records that one attribute determines another, which lets the engine aggregate metrics at the correct level Correct answer.
  4. It controls the order in which attributes appear in a report template

Explanation

Attribute relationships encode the functional dependencies between attributes and drive how the SQL engine chooses the level of aggregation for metrics. Report display order is a template property, security is handled by security filters, and physical storage is defined by the lookup table mapping. Relationships are about analytical grain, not presentation or access.

Question 30Semantic Layer Modeling and Governed Definitions

What is the primary purpose of a conformed dimension such as a shared Date or Customer attribute across multiple fact tables in a MicroStrategy project?

  1. To eliminate the need for attribute relationships in the schema
  2. To force every report to include the same set of attributes
  3. To reduce the number of tables in the warehouse by merging fact tables
  4. To allow metrics from different fact tables to be combined in one report at a consistent grain Correct answer.

Explanation

Conformed dimensions give multiple fact tables a common attribute, so the engine can join facts through that attribute and report them together at a consistent level. They do not merge physical fact tables, do not dictate report contents, and do not replace attribute relationships.

Question 31Semantic Layer Modeling and Governed Definitions

A developer wants to give report authors a business-friendly label such as 'Net Sales' while keeping the underlying formula hidden from modification. Which metric property setting supports this?

  1. Set the metric description and lock the metric so users cannot edit its definition Correct answer.
  2. Rename the underlying fact column in the warehouse
  3. Create a separate report-level metric with the friendly name
  4. Add the friendly name as a filter qualification

Explanation

A schema metric carries a description for author guidance and can be locked so its definition cannot be altered by report designers. A report-level metric would not be reusable or centrally governed, renaming warehouse columns does not affect the metric object, and filters do not rename measures.

Question 32Semantic Layer Modeling and Governed Definitions

Which object should a developer create to group attribute elements into named buckets, such as grouping products into 'Premium' and 'Standard' tiers, for use on reports?

  1. A filter
  2. A metric level
  3. A custom group Correct answer.
  4. A transformation

Explanation

A custom group defines named buckets of attribute elements and can be placed on reports as an independent grouping. A filter qualifies rows but does not create named element groupings, metric levels control aggregation grain, and transformations shift time references.

Question 33Semantic Layer Modeling and Governed Definitions

A developer is building a schema and needs to connect an attribute to its lookup table. Which schema object mapping accomplishes this?

  1. Create a metric with the attribute as its level
  2. Map the attribute to the lookup table and its forms to the corresponding lookup columns Correct answer.
  3. Map the attribute directly to the fact table's foreign key column
  4. Add the attribute to a hierarchy object

Explanation

An attribute is mapped to its lookup table, and each attribute form is mapped to the specific column that supplies its value. Fact table foreign keys are used for relationships, not as the attribute's lookup source. Metric levels and hierarchies reference attributes but do not provide lookup storage for them.

Question 34Semantic Layer Modeling and Governed Definitions

A metric formula is defined as Sum(Cost) and the developer sets the metric's level to the Product attribute. Which behavior results when the metric appears on a report that also includes Region?

  1. The metric returns the grand total across all Products and Regions
  2. The metric cannot be placed on the report because the levels conflict
  3. The metric aggregates at the Product level and repeats the same value across Regions for each Product Correct answer.
  4. The metric aggregates at the Region level instead of the Product level

Explanation

Setting a metric level fixes the aggregation grain to the specified attribute, so values are computed per Product and then repeated for every Region shown alongside that Product. The level overrides the report grain rather than deferring to Region, and the metric remains usable on the report. It does not collapse to a grand total.

Question 35Semantic Layer Modeling and Governed Definitions

A developer must ensure that a metric always reflects the latest data by using a transformation that maps today's date to the current period. Which object should be configured?

  1. A transformation with an offset expression that maps the current date to the period attribute Correct answer.
  2. A custom group on the Date attribute
  3. A metric level set to the Date attribute
  4. A filter qualification on the Date attribute

Explanation

Transformations apply an offset expression that maps one time period to another, which is how relative-period metrics such as current period or prior year are built. A filter selects dates but does not create a reusable period offset, a metric level controls grain rather than time shifting, and a custom group buckets elements.

Question 36Semantic Layer Modeling and Governed Definitions

A developer defines a metric with the formula Sum(Revenue) / Sum(Units) and wants the result to be computed after aggregation rather than row by row. Which metric setting controls this?

  1. Set the metric to use the compound smart metric behavior so the division occurs at the report level Correct answer.
  2. Set the metric level to the transaction attribute
  3. Set the metric to use a running total
  4. Set the metric to be a derived metric inside the report

Explanation

Compound smart metrics compute each component at the report level and then combine the results, which yields a correct ratio of aggregated totals. A derived metric is a report-scoped object, not the setting that controls aggregation order. Setting the level to the transaction grain forces row-level computation, and running totals accumulate values rather than compute a ratio.

Question 37Semantic Layer Modeling and Governed Definitions

A report joins two fact tables that share the Customer attribute but store sales and returns separately. What must the developer verify to prevent incorrect metric results?

  1. That the report uses a single filter for both facts
  2. That the attribute relationships and fact-level settings allow the engine to join the facts at the correct grain Correct answer.
  3. That both fact tables use identical column names
  4. That the Customer attribute has only one form

Explanation

When multiple fact tables are combined, the engine relies on attribute relationships and fact-level settings to determine the correct join grain and avoid fan-out. Matching column names are not required, a single form is not a prerequisite, and a shared filter does not resolve grain mismatches.

Question 38Semantic Layer Modeling and Governed Definitions

A developer needs a prompt that filters a report by selecting one or more attribute elements at run time. Which prompt type is appropriate?

  1. An attribute element list prompt Correct answer.
  2. A hierarchy prompt on a report
  3. An object prompt on a metric
  4. A value prompt on a metric

Explanation

An attribute element list prompt presents elements of an attribute for selection and supplies them to a filter. Value prompts collect typed metric values, object prompts select metadata objects, and hierarchy prompts select hierarchies rather than elements for filtering.

Question 39Semantic Layer Modeling and Governed Definitions

A developer wants a metric to display the value for the prior year alongside the current year on the same report row. Which modeling approach is appropriate?

  1. Create a custom group on the Year attribute
  2. Create a filter that excludes the current year
  3. Create a second metric that uses a year transformation in its formula Correct answer.
  4. Create a derived metric inside the report without a transformation

Explanation

Applying a year transformation to a second metric shifts the calculation to the prior period, so both current and prior values appear on the same row. A filter removes data rather than shifting it, a custom group buckets years without offsetting, and a derived metric without a transformation still computes for the current period.

Question 40Semantic Layer Modeling and Governed Definitions

A developer is deciding whether to model a business rule as a filter object or as a metric. Which criterion best guides the choice?

  1. Use a metric when the rule must be applied to every report and a filter otherwise
  2. Use a filter when the rule must be reusable and a metric when it is one-time
  3. Use a filter when the rule restricts which rows qualify, and a metric when the rule computes a value Correct answer.
  4. Use a filter when the rule involves arithmetic and a metric when it involves text

Explanation

Filters and metrics serve different purposes: filters determine which data rows participate, while metrics compute values from those rows. Both can be reusable, and neither is chosen based on text versus arithmetic. The deciding factor is whether the rule restricts rows or calculates a measure.

Question 41Semantic Layer Modeling and Governed Definitions

A developer defines a metric with a level of Country and places it on a report that includes City. What is the expected result?

  1. The metric returns the grand total for all Countries
  2. The metric automatically aggregates at the City level
  3. The metric returns null because City is below Country
  4. The Country-level value repeats for each City within that Country Correct answer.

Explanation

When a metric level is set to a higher attribute than the report grain, the engine computes at that level and repeats the value for each lower-level row. It does not return null, does not silently change to the lower grain, and does not collapse to a grand total.

Question 42Semantic Layer Modeling and Governed Definitions

A developer wants to restrict a metric so it only considers rows where the order status is 'Shipped', without changing which orders appear on the report. Which metric feature should be used?

  1. A metric filter that applies the condition inside the metric calculation Correct answer.
  2. A security filter on the Order attribute
  3. A custom group on order status
  4. A report filter on order status

Explanation

A metric filter conditions the rows used in the metric's own calculation while leaving the report's row set unchanged. A report filter would remove orders from the report entirely, a security filter restricts user access, and a custom group organizes elements rather than conditioning a metric.

Question 43Semantic Layer Modeling and Governed Definitions

A developer needs to compare a store's sales against the average sales of all stores in its region on the same report row. Which modeling technique is most appropriate?

  1. Use a custom group that groups stores by region
  2. Use a report filter that keeps only the region average row
  3. Use a level metric at the Region level combined with the store-level metric in a compound calculation Correct answer.
  4. Use a transformation that maps stores to regions

Explanation

A metric leveled at Region computes the regional aggregate, which can then be combined with the store-level value to produce the comparison on each row. Filters remove rows, custom groups bucket elements without calculating averages, and transformations shift time periods rather than attribute levels.

Question 44Semantic Layer Modeling and Governed Definitions

A developer observes that a metric returns a value at the Region level but null when the report is drilled to City. Which schema issue is the most plausible cause?

  1. The metric has a transformation applied
  2. The attribute relationship between City and Region is missing or incorrectly defined Correct answer.
  3. The report filter excludes City elements
  4. The metric formula uses Sum instead of Count

Explanation

Aggregation depends on attribute relationships; if City is not properly related to Region, the engine cannot resolve the metric at the City grain and may return null. The choice of Sum versus Count affects the value but not the grain resolution, a filter would remove rows rather than null the measure, and a transformation shifts periods rather than breaking relationships.

Question 45Semantic Layer Modeling and Governed Definitions

A developer must expose a governed 'Revenue' measure that behaves differently for two business units, using one metric object that switches logic at run time. Which approach is most appropriate?

  1. Create a custom group on the business unit attribute
  2. Build a compound metric that branches on a prompt or attribute-driven condition Correct answer.
  3. Create a report-level derived metric in each dossier
  4. Create two separate schema metrics and ask users to choose the right one

Explanation

A compound metric can incorporate conditional logic so one governed object returns the appropriate calculation per business unit, keeping the definition centralized. Separate metrics push the choice to users and risk inconsistency, report-level metrics escape governance, and custom groups do not compute measures.

Question 46Semantic Layer Modeling and Governed Definitions

A developer is designing a schema where a single fact table must support metrics at both the order-line grain and the order grain. Which design consideration is most important?

  1. Remove the order-line attribute from the schema
  2. Define attribute relationships so Order is recognized as the parent of order line, allowing correct aggregation Correct answer.
  3. Set every metric level to the order line
  4. Add a duplicate fact table at the order grain

Explanation

When one fact table holds order-line detail, the engine can roll up to the order grain only if the attribute relationships correctly express that Order determines the order line. Duplicating fact tables adds maintenance burden, removing the detail attribute loses analysis capability, and forcing every metric to the line grain prevents order-level reporting.

Question 47Semantic Layer Modeling and Governed Definitions

A developer needs a metric that returns the count of distinct customers who purchased, regardless of how many orders appear on the report. Which metric definition is appropriate?

  1. Sum(Order Quantity)
  2. Average(Revenue)
  3. Count(Distinct Customer) with the level set to Customer Correct answer.
  4. Count(Order ID)

Explanation

A distinct count of the Customer attribute, leveled at Customer, returns the number of unique purchasing customers independent of order count. Summing quantity and counting order IDs both scale with the number of orders, and averaging revenue produces a monetary value rather than a customer count.

Question 48Semantic Layer Modeling and Governed Definitions

A developer wants to ensure that a metric's definition is used consistently across all dossiers in a project rather than recreated in each. Which practice best supports this?

  1. Define the measure as a report filter in each dossier
  2. Define the measure as a custom group in each dossier
  3. Define the measure as a schema metric in the project metadata and reference it from dossiers Correct answer.
  4. Define the measure as a derived metric in each dossier

Explanation

Schema metrics live in project metadata, so every dossier references the same governed definition and a change propagates consistently. Derived metrics, filters, and custom groups either are report-scoped or serve different purposes and cannot enforce a single measure definition.

Question 49Semantic Layer Modeling and Governed Definitions

Which schema object allows a developer to define a reusable named set of attribute elements that can be applied as a filter to many reports?

  1. A fact extension
  2. A filter object saved in the project metadata Correct answer.
  3. A metric level
  4. A transformation

Explanation

A filter object stores a reusable qualification in project metadata and can be applied to any report needing that row restriction. Metric levels control aggregation grain, transformations shift time periods, and fact extensions add columns to existing fact tables rather than filtering rows.

Question 50Semantic Layer Modeling and Governed Definitions

A developer must decide whether to store a business rule as an attribute form or as a separate attribute. Which consideration is most relevant?

  1. Use a separate attribute when the value is text
  2. Use a form when the value describes the same entity, and a separate attribute when the value participates in relationships or grouping Correct answer.
  3. Use a form when the value changes frequently
  4. Use a form when the value must be aggregated with Sum

Explanation

Forms describe different aspects of the same entity, such as ID and name, while a separate attribute is warranted when the value must relate to other attributes or be used for grouping and drilling. Aggregation, data type, and change frequency do not determine the choice.