To optimize the user experience for dashboards and explorations. Framework Manager packages must be enriched. Which statement is true about enriching Framework Manager packages?

Question

Options

• AA developer can't enrich a package that includes dimensionally modeled (DMR) relational objects.
• BFramework Manager packages are automatically enriched when published to Cognos Analytics.
• CTo access the enrich package functionality, you need read/execute/traverse permissions for the
• DIn order to have enough data to support the Al-functions in your dashboards and explorations, the

• A
  2% (1)
• B
  12% (5)
• C
  7% (3)
• D
  78% (32)

Explanation

Option D is correct because enriching a Framework Manager package profiles the data and generates the statistical metadata (value distributions, data types, relationships) that Cognos Analytics AI-powered features - such as smart suggestions, natural language queries, and automatic visualizations - rely on to function effectively in dashboards and explorations. Without enrichment, the AI engine lacks the context needed to make intelligent recommendations.

Why the distractors are wrong:

• A is false - DMR (Dimensionally Modeled Relational) packages can be enriched; there is no restriction blocking enrichment based on the modeling approach used.
• B is false - enrichment is not automatic upon publishing; it must be explicitly triggered by a developer or administrator after the package is published.
• C is misleading/incomplete - while permissions are relevant to many Cognos tasks, simply having read/execute/traverse permissions is not the defining statement about why enrichment matters or what it enables.

Memory tip: Think of enrichment as "feeding the AI its training data about your model." Just as an AI assistant needs information to give smart answers, Cognos AI features need enrichment metadata to give smart dashboard suggestions - no enrichment, no AI fuel.

No community discussion yet for this question.