Question 1

If a user already exists as part of a group in Tableau Server, and Active Directory synchronization then applies a minimum site role to the group, what will happen
to the existing user's site role?

Accepted Answer

Correct answer: A

Question 2

What should you do to disable table recommendations for popular data sources and tables to users?

Accepted Answer

Correct answer: A

Question 3

What two events must occur for Tableau Server to recompute queries for a workbook cache after a scheduled refresh? (Choose two.)

Accepted Answer

Tableau Server uses caching to speed up workbook loading by storing query results. After a scheduled extract refresh updates the data, the cache may need
recomputing—let??s dive into the mechanics:
Caching Basics:
VizQL Cache: Stores rendered views and query results for faster access.
Refresh Trigger: A scheduled refresh updates the underlying extract (.hyper), but the cache isn??t automatically invalidated—it??s demand-driven.
Recompute Conditions: Tableau recomputes the cache when the workbook is accessed (viewed) and its data has changed (e.g., via refresh).
Evaluation:
Option B (The workbook has upcoming scheduled refresh tasks): Correct.
Why: An upcoming refresh task indicates the workbook relies on an extract with a schedule. After the refresh runs, the data changes, priming the cache for
recomputation on next view. Without a schedule, no refresh occurs, so this is a prerequisite.
Detail: Schedules are set inSchedules>Tasks—e.g., "Daily at 2 AM."
Option D (The workbook has been viewed recently): Correct.
Why: Viewing triggers cache recomputation if the data has changed (e.g., post-refresh). Tableau uses a "lazy caching" model—cache updates only when a user
loads the workbook, ensuring fresh results.
Detail: "Recently" isn??t strictly defined but implies post-refresh access.
Option A (Published in the last month): Incorrect.
Why: Publish date is irrelevant—cache recomputation ties to data changes and access, not publication timing.
Option C (All Users group has permission rule allowing access): Incorrect.
Why: Permissions enable viewing, but recomputation requires actual access (viewing) and a refresh event, not just potential access.
Why This Matters: Caching balances performance and freshness—understanding triggers prevents stale data surprises.
[Reference: Tableau Server Documentation - "Caching and Performance" (https://help.tableau.com/current/server/en-us/perf_cache.htm)., , ]

Question 4

What should you do to ensure that server tasks associated with a particular schedule run one-at-a-time?

Accepted Answer

Correct answer: A

Question 5

You attempt to delete a user who owns content on a Tableau Server. What is the result of the delete action?

Accepted Answer

Correct answer: D

Question 6

Which Tableau Server process performs the role of a database for metadata?

From SurePassExam
https://www.surepassexam.com/Analytics-Admn-201-exam-dumps.html (0 New Questions)

Accepted Answer

Correct answer: B

Question 7

Your deployment of Tableau Server uses Active Directory authentication. What statement correctly describes the process of importing a group from Active
Directory?

Accepted Answer

Correct answer: D

Question 8

What type of information is stored in the tsm maintenance backup -f <filename>.tsbak command?

Accepted Answer

Correct answer: C

Question 9

What statement correctly describes locking permissions to a project?

Accepted Answer

In Tableau Server,projectsorganize content (workbooks, data sources) and use permissions to control access. "Locking permissions" restricts how permissions are
managed within a project—let??s explore this exhaustively:
Permission Management Modes:
Managed by Owner: Default mode. Content owners (e.g., workbook publishers) can set permissions on their items, inheriting project defaults as a starting point.
Locked to the Project: Project-level permissions are enforced, and content owners cannot modify them. This ensures consistency across all items in the project.
How to Lock:
In the Tableau Server web UI:
Go toContent>Projects.
Select a project, clickActions>Permissions.
In the Permissions dialog, changePermissions Managementfrom "Customizable" (Managed by Owner) to "Locked."
Set the desired permissions (e.g., Viewer, Editor) for users/groups, which then apply uniformly to all content.
Via REST API: Use the updateProject endpoint with "permissionsLocked": true.
Option B (You can lock permissions to a project by changing Customizable to Locked): Correct.
Details: This is the precise action in the UI—switching from "Customizable" to "Locked" locks permissions at the project level.
Impact: Owners lose the ability to override permissions on individual workbooks/data sources, enforcing governance.
Example: Set "All Users" to Viewer (Locked)—all content in the project is view-only, regardless of owner intent.
Option A (Locking permissions must be enabled on the Server Settings page): Incorrect.
Why: Locking is a per-project setting, not a server-wide toggle. The Server Settings page (via TSM) controls global configs (e.g., authentication), not project
permissions.
Option C (Content permissions are locked by default): Incorrect.
Default: New projects are "Managed by Owner" (Customizable), allowing flexibility unless explicitly locked by an admin.
Option D (By setting the appropriate Project permission role): Incorrect.
Confusion: "Project permission role" isn??t a term—permissions are set via rules (e.g., Viewer, Editor), but locking is a separate action (Customizable ?? Locked).
Why This Matters: Locking permissions ensures uniform access control, critical for regulated environments or large teams where consistency trumps flexibility.
[Reference: Tableau Server Documentation - "Lock Project Permissions" (https://help.tableau.com/current/server/en-us/permissions_lock.htm)., , ]

Question 10

Which three types of authentications can be used with user-based licensing? (Choose three.)

Accepted Answer

Tableau Server??suser-based licensing(Creator, Explorer, Viewer) ties licenses to individual users—let??s determine compatible authentication methods:
User-Based Licensing:
Licenses are assigned per user, tracked by username.

From SurePassExam
https://www.surepassexam.com/Analytics-Admn-201-exam-dumps.html (0 New Questions)
Authentication determines how users log in—must integrate with licensing.
Option A (Local authentication): Correct.
Details: Users are managed in Tableau Server??s internal database—username/password set manually or via import.
Why: Directly ties to user accounts, fully compatible with licensing.
Option C (Trusted authentication): Correct.
Details: Allows external apps to authenticate users via tickets (e.g., /trusted/).
Why: Maps to Tableau usernames, integrating with licensing—common for embedded analytics.
Config: Trusted IPs or credentials set in TSM.
Option D (Active Directory): Correct.
Details: Uses AD for authentication (LDAP or Kerberos)—users sync to Tableau Server.
Why: AD usernames align with licensing—supports SSO and user management.
Config: Enable via tsm authentication active-directory configure.
Option B (Reliance authentication): Incorrect.
Why: Not a recognized Tableau authentication method—likely a typo (e.g., for "Resilience" or misheard term). No such feature exists.
Why This Matters: Authentication flexibility ensures user-based licensing fits diverse IT environments—critical for adoption.
[Reference: Tableau Server Documentation - "Authentication" (https://help.tableau.com/current/server/en-us/auth_overview.htm), "Licensing Overview"
(https://help.tableau.com/current/server/en-us/license_usage.htm)., , ]