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.