Analytics-Con-202 Exam Questions & Answers

The correct security mechanism is the Einstein Trust Layer's PII masking capability. Salesforce guidance for AI-assisted calculated-field creation states that the agent may use information from the semantic model, including its schema and metadata, and that personally identifiable information is masked by the Einstein Trust Layer before information is sent to the LLM.

This allows Tableau Next's generative functionality to receive the semantic context required to construct useful calculated fields while applying Salesforce's enterprise AI security controls.

Option A describes a whole-model encryption/decryption workflow that is not the documented Tableau Next processing model. Option C is also incorrect because the system does not simply prohibit every field that could potentially contain PII. Instead, the Trust Layer applies masking and other controls to protect sensitive information while retaining useful analytical context.

More broadly, Salesforce states that Tableau Agent and Agentforce inherit the Einstein Trust Layer's security, governance, and trust mechanisms, including protections designed to prevent customer data from being retained by external LLMs for model training.

Reference/Topics: Agentic Experiences -> Einstein Trust Layer -> PII Masking -> Generative AI Calculated Fields.

Row-level security for this scenario should be defined in the semantic model so the governed analytical layer determines which records each user is allowed to retrieve. By applying RLS at the semantic-model level, the access rule travels with the analytical definitions used by metrics, visualizations, dashboards, and agentic experiences instead of depending on a particular dashboard layout.

Dashboard filters and visualization properties are presentation controls. They can alter what appears on a given screen, but they are not an appropriate substitute for a security rule because a user could potentially access the same underlying semantic content through another approved analytical surface. The restriction therefore belongs in the model that governs how analytical queries resolve against the sensitive HR dataset.

For an HR scenario, the RLS rule can be based on attributes such as employee, manager, department, region, or another authorized access dimension. The objective is to ensure that every downstream analytical experience receives only the rows permitted for the signed-in user. This centralizes security behavior and reduces the risk of inconsistent filtering across dashboards.

Reference/Topics: Data Setup -> Semantic Models -> Row-Level Security -> Governed HR Data.

Tableau Next applies a deterministic precedence model for conditional formatting. When multiple conditions overlap, Tableau Next attempts to combine their formatting. When the formatting definitions actually conflict---for example, two matching rules specify incompatible formatting for the same property---the most recently created rule takes precedence. Therefore, B precisely matches documented Tableau Next behavior.

The conditions are not discarded simply because they overlap, so A is incorrect. Likewise, Tableau Next does not give permanent precedence to the earliest rule, making C incorrect.

This behavior is important when designing KPI text components or executive dashboards containing several threshold-based rules. Rule ordering can materially affect what users see when a measure simultaneously satisfies multiple business conditions. Consultants should therefore inspect overlapping ranges and understand which formatting attributes can coexist versus which produce a direct conflict.

Salesforce specifically documents two applicable principles: overlapping conditions have their formats combined, and conflicting rules resolve in favor of the most recently created rule.

Reference/Topics: Visualizations and Dashboards -> Analyze and Share Data -> Create Effective Dashboards -> Conditional Formatting.

A Personal Org is specifically designed for self-service analysis where an analyst needs to combine governed corporate information with personal or specialized data without introducing that experimental dataset into the managed production governance environment.

Salesforce states that Personal Org enables analysts to combine production data with local or specialized datasets, create semantic models and visualizations, and iterate independently without affecting governed production content. Production assets can also be reused inside Personal Org while their existing production governance remains intact.

Once the analysis is ready, the Personal Org owner can share the relevant workspace with another eligible analyst and grant Viewer or Editor access. Salesforce explicitly documents sharing Personal Org workspaces with Tableau Next Analyst users.

Option B does not provide the isolated self-service environment intended for ungoverned analytical experimentation. Option C unnecessarily moves the analytical workflow into an external MCP client and does not represent the native Tableau Next solution for this use case.

Reference/Topics: Managing Workspaces and Orgs -> Personal Org -> Combine Governed and Personal Data -> Workspace Sharing.

This is a textbook use case for Business Preferences. Salesforce defines Business Preferences as business-specific instructions stored within the semantic model that tell Analytics Q&A how to interpret an organization's terminology, defaults, jargon, and business logic.

The expression ''top-performing'' is ambiguous in ordinary language. The organization has explicitly defined it to mean performance ranked by Annual Contract Value. A Business Preference such as ''When users ask about top-performing AEs, use ACV to determine performance'' supplies precisely that missing business context.

Renaming ACV to Performance would reduce semantic clarity and distort the actual meaning of the field. ACV should retain its authoritative business name.

A Verified Question can help calibrate frequently asked questions and improve responses to semantically similar queries, but the underlying issue here is a reusable business-language interpretation rule, not merely one incorrect Q&A example. Business Preferences are therefore the more appropriate semantic mechanism.

Salesforce also recommends keeping Business Preferences concise and using them for contextual interpretation rather than structured calculations that belong in calculated fields or metrics.

Reference/Topics: Agentic Experiences -> Business Preferences -> Business Terminology -> Analytics Q&A Accuracy.