Which Tableau API should you use to satisfy the following requirements? * Programmatic access to work with content, users, sites, etc. * Updating workbooks or data sources * Automating management of users and groups * Integrating Tableau with a custom app or web portal
Correct Answer: B
Explanation Link to Tableau Server documentation: https://www.tableau.com/developer/automation
Question 72
How can an administrator subscribe a user to a view?
Correct Answer: B
Explanation Link to Tableau Server documentation: https://help.tableau.com/current/online/en-us/subscribe_user.htm
Question 73
Which of the following processes listed are single-threaded? (Select all)
Correct Answer: A,C,D
Explanation Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/processes.htm
Question 74
Which three methods should an administrator use to create a Tableau Server group or project? (Choose three.)
Correct Answer: B,C,D
Tableau Server provides multiple methods to creategroups(collections of users) andprojects(content containers), catering to UI, CLI, and programmatic needs. Let's dissect each option with depth: * Option B (Tableau Server browser interface): Correct. * Groups: Go toUsers > Groups > Add Group, name it, and optionally sync with Active Directory. * Projects: Go toContent > Projects > New Project, set name, description, and permissions. * Details: The web UI is intuitive, requiring server/site administrator rights. It's ideal for manual, ad-hoc creation with immediate visibility. * Permissions: For projects, you can set default permissions or lock them here. * Option C (tabcmd): Correct. * Groups: tabcmd creategroup "GroupName" creates a local group. Add users with tabcmd addusers "GroupName" --users "user1,user2". * Projects: tabcmd createproject -n "ProjectName" -d "Description" creates a project. * Details: tabcmd is a command-line tool for batch operations or scripting (e.g., automating group /project setup). It requires a server admin login (tabcmd login). * Limitation: No AD sync via tabcmd-that's UI or REST API territory. * Option D (REST API): Correct. * Groups: Use the POST /api/api-version/sites/site-id/groups endpoint with a payload (e.g., {"group": {"name": "GroupName"}}). Supports AD import too. * Projects: Use POST /api/api-version/sites/site-id/projects (e.g., {"project": {"name": "ProjectName", "description": "Desc"}}). * Details: The REST API is programmatic, ideal for integration with external systems or bulk automation. Requires authentication via a token and server/site admin rights. * Power: Offers full control, including nested projects and custom permissions. * Option A (tsm customize): Incorrect. * Purpose: tsm customize modifies TSM UI branding (e.g., logos, colors) via commands like tsm customize --logo "path/to/logo.png". * Why Wrong: It's unrelated to creating groups or projects-it's for cosmetic server configuration, not content/user management. Why This Matters: Offering UI, CLI, and API options ensures flexibility-manual for small tasks, automation for scale-critical in enterprise deployments.
Question 75
What two types of users can sign in to Tableau Server and edit the permissions for a workbook in a project, when permissions are NOT set to Locked to the project? (Choose two.)
Correct Answer: C,D
Editing permissions on a workbook in Tableau Server depends on the user's role and the project's permission settings. Since permissions arenot locked(i.e., "Managed by Owner"), let's dissect who can edit them: * Permission Model: * Not Locked: Owners of content (workbooks, data sources) can set permissions, and Project Leaders can override at the project level. * Site Roles: Define maximum capabilities (e.g., Viewer, Explorer, Creator). * Capabilities: "Set Permissions" is explicit-only certain users get it. * Option C (The workbook's owner): Correct. * Details: The owner (typically the publisher) has full control over their workbook when permissions are Managed by Owner: * How: In the UI, go toContent > Workbooks > Actions > Permissions-owners can edit rules (e.g., grant Editor to a group). * Site Role: Minimum of Explorer (can publish) or Creator to publish, ensuring "Set Permissions" capability. * Why: Ownership inherently includes permission management unless locked. * Option D (Users set to Project Leader for the workbook's project): Correct. * Details: Project Leaders are assigned viaContent > Projects > Actions > Permissions > Set Project Leader: * Power: Can edit permissions for all content in the project, even if not the owner. * Site Role: Requires Site Administrator or Server Administrator (Creator/Explorer variants suffice). * Why: Overrides ownership in Managed by Owner mode-ensures project-level governance. * Option A (Users with project and workbook Viewer role): Incorrect. * Why: Viewer role (site-level) limits users to viewing-lacks "Set Permissions" capability, regardless of project/workbook rules. * Option B (Users with workbook Interactor role): Incorrect. * Why: "Interactor" isn't a standard role-likely a misnomer for Explorer or Viewer with interaction permissions (e.g., Filter). No permission-editing rights exist here. Why This Matters: Knowing who can edit permissions prevents access control gaps-crucial for collaborative or regulated environments.
