Analytics-Admn-201 Exam Dumps - Salesforce Certified Tableau Server Administrator

Trusted Tickets is an authentication method in Tableau Server for embedding views in external applications (e.g., portals) without requiring users to log in manually. Here’s how it works:

A trusted application (e.g., a web server) authenticates with Tableau Server using a trusted IP or username/password.

Tableau Server issues a temporary ticket (a unique string).

The ticket is embedded in a view URL (e.g., /trusted//views/...), granting access to the view for a short period (configurable, default 5 minutes).

Option A (Access embedded views without being prompted for credentials): Correct. Trusted tickets enable SSO-like behavior for embedded content, bypassing the login prompt if the ticket is valid. This is ideal for seamless integration into external systems.

Option B (Encrypt database connections): Incorrect. Encryption is handled by data source configurations (e.g., SSL), not trusted tickets, which focus on user authentication.

Option C (Save and edit workbooks): Incorrect. Trusted tickets grant view access, not edit permissions—those depend on the user’s site role and permissions.

Option D (Embed database credentials): Incorrect. Trusted tickets authenticate users to Tableau Server, not databases—database credentials are managed separately in the data source.

Why This Matters: Trusted tickets simplify embedding Tableau content securely in custom applications, enhancing user experience.

TSM is Tableau Server’s management layer, accessible via CLI or web UI (port 8850). HTTPS secures this access—let’s identify the responsible process:

TSM Architecture:

Administration Controller: Core TSM process, running on the initial node, handling configuration, UI, and CLI commands.

HTTPS: Enabled by default on port 8850 with a self-signed certificate (configurable to custom certs).

Option B (Administration Controller): Correct.

Details: Hosts the TSM web UI (https:// :8850) and processes CLI requests. It manages the HTTPS listener, serving the interface securely.

Why: It’s the central hub for TSM operations, including secure access.

Option A (License Manager): Incorrect.

Why: Validates licenses, not responsible for HTTPS or UI access.

Option C (Administration Agent): Incorrect.

Why: Runs on additional nodes in multi-node setups to relay commands to the Controller—no direct HTTPS role.

Option D (Coordination Service): Incorrect.

Why: ZooKeeper manages cluster state, not TSM’s web interface or HTTPS.

Why This Matters: Secure TSM access protects server administration—Administration Controller is the linchpin.

Tableau Server can record performance metrics for workbooks to troubleshoot slow-loading views. This feature must be enabled at the site level (via Settings > General > Allow Performance Recording). Once enabled, you can trigger recording for a specific view by modifying its URL.

The correct syntax is to append :record_performance=yes& to the view URL, immediately after the session ID. For example:

Original URL: http://server/#/site/my-site/views/workbook/view?:iid=1

Modified URL: http://server/#/site/my-site/views/workbook/view?:iid=1:record_performance=yes &

After loading the view with this parameter, a performance recording is generated and accessible via the Performance option in the toolbar.

Option B (Type :record_performance=yes& at the end of the view URL, immediately after the session ID): Correct. This follows Tableau’s documented method for enabling performance recording.

Option A (Click the Performance link in the toolbar): Incorrect. The Performance link appears only after recording is triggered via the URL; it’s not the method to enable it.

Option C (Type :record_performance=yes& immediately before the session ID): Incorrect. The parameter must follow the session ID (e.g., :iid=1) to function correctly.

Option D (Delete the session ID in the URL and reload the view): Incorrect. The session ID is required for the view to load properly; removing it breaks the URL.

Tableau Server relies on several processes to function, each with a specific role. The Repository process (powered by PostgreSQL) serves as the database for metadata, storing critical information such as:

User and group details.

Permissions and site configurations.

Workbook and data source metadata (e.g., schedules, subscriptions).

Option B (Repository): Correct. The Repository is the centralized database that holds all metadata, making it the backbone of Tableau Server’s content management. There are typically two instances in an HA setup (one active, one passive), monitored by the Cluster Controller.

Option A (Data Engine): Incorrect. The Data Engine manages in-memory data processing and extract storage (e.g., .hyper files), not metadata. It’s separate from the Repository.

Option C (Backgrounder): Incorrect. The Backgrounder handles background tasks like extract refreshes and subscriptions, but it doesn’t store metadata—it interacts with the Repository to retrieve task details.

Option D (File Store): Incorrect. The File Store manages physical extract files and workbook assets, not metadata, which is stored in the Repository.

In Tableau Server, roles and permissions dictate who can perform specific administrative tasks. A "server administrator" has full control over the entire Tableau Server deployment, while site administrators manage specific sites. Some tasks are restricted to server administrators due to their server-wide impact.

Option B (Adding a site): Creating a new site in a multi-site Tableau Server environment is a server-level task that only a server administrator can perform. Sites are logical partitions within the server, and adding a site affects the overall server structure. Site administrators cannot create new sites; they can only manage existing ones.

Option D (Adding users): Adding users to Tableau Server (e.g., via the TSM interface or tabcmd) is a server administrator task when it involves adding users at the server level or assigning them to the default site. While site administrators can add users to their specific site in a multi-site environment, the initial addition of users to the server requires server administrator privileges. The question’s phrasing (“always require”) suggests a server-wide context, making this a correct choice.

Option A (Creating a schedule): This is incorrect because both server administrators and site administrators can create schedules for tasks like extract refreshes or subscriptions within their scope. It’s not exclusive to server administrators.

Option C (Locking project permissions): This is incorrect because locking project permissions can be done by a site administrator or project leader with appropriate permissions. It’s a project-level action, not a server-level task requiring a server administrator.