When automating and repeating data processing tasks, what challenges might be encountered in managing and sharing Snowsight dashboards effectively?

Question

Options

• AEnsuring real-time data updates
• BLimited user access control
• CIncompatibility with other BI tools
• DDifficulty in embedding external content

• A
  2% (1)
• B
  93% (51)
• C
  5% (3)

Explanation

Managing and sharing Snowsight dashboards presents real friction around access control and embedding. Snowsight's sharing model is relatively coarse-grained - you can share with roles or specific users, but fine-tuned, row-level or feature-level permissions within a dashboard are limited, making it hard to safely share dashboards across teams with different data visibility requirements. Similarly, Snowsight does not natively support embedding external content (e.g., iframes, third-party widgets) within dashboards, and embedding Snowsight dashboards themselves into external portals is restricted, which complicates enterprise reporting workflows.

A is wrong because Snowflake handles data freshness well - dashboards support auto-refresh and query results update on demand, so real-time updates are not a meaningful barrier. C is wrong because Snowflake data is widely accessible to external BI tools (Tableau, Power BI, Looker) via standard connectors; the issue isn't cross-tool incompatibility. C and A describe things Snowflake actually does well.

Memory tip: Think of the two "sharing pain points" as Barriers + Doors - you can't easily control who gets in (B = access barriers) or embed content through the door (D = closed embedding). If a challenge sounds like something Snowflake solved with its core architecture (speed, connectivity), it's a distractor.

No community discussion yet for this question.