Salesforce Analytics-Admn-201 Exam Dumps

In Tableau Server, projects are containers for organizing and securing content. They help manage permissions and structure content hierarchically. Let's define what can be contained:

Workbooks: Visualizations and dashboards published to the Server.

Data Sources: Published connections or extracts reusable across workbooks.

Nested Projects: Sub-projects within a parent project, introduced in later versions (e.g., 2018.2) for deeper organization.

Option B (Workbooks): Correct. Workbooks are the primary content type in projects, containing views and dashboards.

Option C (Nested Projects): Correct. Nested projects allow hierarchical structuring (e.g., a 'Sales' project with 'Q1' and 'Q2' sub-projects), with inherited or custom permissions.

Option D (Data Sources): Correct. Published data sources reside in projects, providing reusable data connections.

Option A (Groups): Incorrect. Groups are collections of users managed at the site or server level, not stored within projects. Projects contain content, not user entities.

Why This Matters: Projects are key to content governance---knowing what they hold helps administrators organize and secure assets effectively.

Comments on Tableau Server visualizations facilitate collaboration. Let's explore what's supported:

Comments Feature: Enabled per site (Settings > General > Allow Comments). Users with 'Add Comment' permission can post on views.

Option B (Text): Correct.

Details: The primary content type---users type free-form text in the comment box.

Use: Notes, questions, or feedback (e.g., 'Sales spiked here---why?').

Option C (@mentions): Correct.

Details: Typing @username notifies the mentioned user via email or the UI (if notifications are enabled).

Use: Directs comments to specific people (e.g., '@John, check this trend').

Option A (Interactive snapshots of a view): Incorrect.

Details: Snapshots (static images) aren't supported in comments---users must take screenshots externally and can't embed them interactively.

Option D (Images - jpg, png): Incorrect.

Details: No attachment or image embedding in comments---text and mentions only. Workaround: Link to an image hosted elsewhere.

Why This Matters: Comments enhance teamwork, but their simplicity (text + mentions) keeps the interface lightweight and focused.

Tableau Server's installer configures process instances based on hardware and deployment type (single-node vs. multi-node). For a single-node installation with 4 cores, we need to consider the default process topology. Let's break this down exhaustively:

Key Processes:

Gateway: Handles incoming requests (1 instance).

Application Server (VizPortal): Manages UI and sessions (1 instance).

VizQL Server: Renders visualizations (2 instances).

Backgrounder: Runs extract refreshes, subscriptions (1 instance).

Data Server: Manages data connections (1 instance).

File Store: Stores extracts (1 instance).

Repository: Metadata database (1 instance, active).

Cluster Controller, Cache Server, etc.: Supporting processes (typically 1 each).

Default Configuration:

On a single-node install, Tableau sets 1 instance per process unless specified otherwise, except for VizQL, which defaults to 2.

The installer doesn't scale instances linearly with cores (e.g., 4 cores 4 instances). Post-install, TSM can adjust this (e.g., tsm topology set-process), but the question asks for the installed default.

Minimum hardware (8 cores, 32 GB RAM) suggests higher defaults, but 4 cores still triggers a minimal setup.

Option B (1): Correct with Caveat.

Most processes (e.g., Backgrounder, Gateway, Data Server) default to 1 instance on install, regardless of 4 cores.

VizQL defaults to 2, but the question's phrasing ('each process') implies a general rule. Historically (and per docs), 1 is the baseline for most, with VizQL as the exception.

Interpretation: Assuming 'each' means the typical case, 1 fits most processes on a 4-core single-node setup.

Option A (2): Incorrect. Only VizQL defaults to 2; others don't.

Option C (8): Incorrect. Far exceeds defaults---8 cores might justify more, but not 4.

Option D (4): Incorrect. Not tied to core count by default; manual config would be needed.

Why This Matters: Understanding defaults aids capacity planning---4 cores is below production minimum (8), so performance tuning may be needed post-install.

In Tableau Server, schedules manage tasks such as extract refreshes and subscriptions. The execution mode of a schedule determines how tasks within that schedule are processed by the Backgrounder process:

Parallel: Tasks run simultaneously (up to the Backgrounder's capacity), which is the default setting.

Serial: Tasks run one-at-a-time in sequence, ensuring that one task completes before the next begins.

To ensure tasks associated with a particular schedule run one-at-a-time, you must configure the schedule's execution mode to Serial. This is done in the Tableau Server web interface:

Go to Schedules.

Select the schedule, click Actions > Edit Schedule.

Under Execution, choose Serial instead of Parallel.

Option A (Set Execution to Serial): Correct. This directly addresses the requirement by forcing tasks to execute sequentially.

Option B (Set Default priority to 0): Incorrect. Priority (1--100) determines the order of task execution across all schedules, not whether tasks run one-at-a-time within a single schedule. Also, 0 is not a valid priority value (minimum is 1).

Option C (Set Frequency to Hourly): Incorrect. Frequency (e.g., hourly, daily) controls when the schedule runs, not how tasks within it are executed.

Option D (Set Execution to Parallel): Incorrect. Parallel execution allows tasks to run simultaneously, which contradicts the requirement.