Important Salesforce Analytics-Admn-201 Exam Questions

Answer: C, D

Explanation:

TSM commands manage Tableau Server maintenance---let's validate their syntax:

Command Requirements:

Some need arguments (e.g., file paths); others are standalone.

Valid and Complete: Must work as-is without errors.

Option C (tsm maintenance cleanup): Correct.

Details: Removes temporary files and old logs---no arguments required (optional flags like -l exist).

Use: tsm maintenance cleanup---runs fully.

Option D (tsm maintenance ziplogs): Correct.

Details: Creates a zip of logs (e.g., tsm-logs.zip)---no arguments needed (optional -d for date range).

Use: tsm maintenance ziplogs---complete and valid.

Option A (tsm maintenance backup): Incorrect.

Why: Requires -f <filename>.tsbak (e.g., tsm maintenance backup -f backup.tsbak)---incomplete without it.

Option B (tsm maintenance restore): Incorrect.

Why: Needs -f <filename>.tsbak (e.g., tsm maintenance restore -f backup.tsbak)---not standalone.

Why This Matters: Correct syntax ensures maintenance tasks execute without errors---critical for server health.

Answer: C

Explanation:

Data-driven alerts in Tableau Server allow users to receive notifications when data in a view meets certain conditions (e.g., a sales metric exceeds a threshold). By default, this feature is disabled for a site unless explicitly enabled by an administrator.

Option C (Change the data-driven alerts setting on the new site's Settings page): This is the correct answer. In the Tableau Server web interface, a site administrator can navigate to the site's Settings > General page and enable the option 'Let users create data-driven alerts.' This must be done manually because the default setting for a new site is disabled. Once enabled, users with appropriate permissions (e.g., Viewer, Explorer, or Creator roles) can create alerts on views they have access to.

Option A (Enable data-driven alerts on the TSM Configuration page): This is incorrect because the TSM Configuration page (accessed via the TSM web UI or CLI) manages server-wide settings like ports, authentication, and processes, not site-specific features like data-driven alerts.

Option B (Run the tsm configuration set -k dataAlerts.checkIntervalInMinutes -v 60 command): This is incorrect. The dataAlerts.checkIntervalInMinutes key controls how frequently Tableau Server checks alert conditions (default is 60 minutes), but it does not enable the feature itself. The feature must first be turned on at the site level.

Option D (No action is necessary): This is incorrect because the default setting for data-driven alerts is off for new sites, requiring explicit action to enable it.

Answer: B, D

Explanation:

Comments on visualizations foster collaboration in Tableau Server---let's break down the requirements:

Commenting Prerequisites:

Site-Level Enablement: Comments must be activated for the site.

Permission: Users need the 'Add Comment' capability on the content.

Site Role: Minimum role of Viewer allows commenting if permissions are set.

Option B (Add Comments must be allowed in permissions): Correct.

Details: In the Permissions dialog (e.g., for a workbook), set 'Add Comment' to 'Allowed' for users/groups. Default is 'Denied' unless explicitly enabled.

How: Content > Workbooks > Actions > Permissions > Edit Rule.

Why: Permissions are granular---site enablement alone isn't enough.

Option D (Comments must be enabled on the site Settings page): Correct.

Details: Go to Site > Settings > General > Allow Comments---check the box.

Why: This is a site-wide toggle (default: off). Without it, no one can comment, regardless of permissions.

Option A (Minimum site role of Explorer - can publish): Incorrect.

Why: Viewer role suffices if permissions allow---Explorer (can publish) isn't required (it adds publishing, not commenting).

Option C (Server Settings page): Incorrect.

Why: Comments are a site-level feature, not server-wide---no such toggle exists in TSM's Server Settings.

Why This Matters: Enabling comments at both site and content levels ensures controlled collaboration---key for team insights.

Answer: C

Explanation:

Registering Tableau Server from the command line involves providing configuration details (e.g., identity store, license) via the tsm register command. Let's explore this fully:

Registration Process:

Run during initial setup or to update settings (e.g., after changing AD/LDAP config).

Uses a configuration file to pass parameters to TSM.

Command: tsm register --file .

File Format:

Tableau Server uses JSON for configuration files in TSM commands like tsm register.

Example:

json

CollapseWrapCopy

{

'identityStore': {

'type': 'local',

'domain': 'example.com'

}

}

JSON is structured, machine-readable, and aligns with Tableau's modern CLI design.

Option C (JSON): Correct.

Official format for tsm register, per documentation and practical use.

Option A (YML): Incorrect.

While tabsvc.yml exists internally, it's not for registration---tsm register uses JSON.

Option B (XML): Incorrect.

Older Tableau configs used XML (e.g., workgroup.yml pre-TSM), but TSM standardized on JSON.

Option D (HTTP): Incorrect.

HTTP is a protocol, not a file format---irrelevant here.

Why This Matters: Correct file format ensures seamless registration, avoiding CLI errors in setup or migrations.

Answer: A, D

Explanation:

Data-driven alerts notify users when data meets conditions (e.g., sales > $10K). Let's examine when Tableau checks these:

Alert Mechanics:

Enabled per site (Settings > General > Data-Driven Alerts).

Backgrounder evaluates conditions against extract data.

Check Intervals: Configurable via tsm configuration set -k dataAlerts.checkIntervalInMinutes (default: 60 minutes).

Refresh Trigger: Also checks post-extract refresh for immediate updates.

Option A (Every 60 minutes): Correct.

Details: Default interval---Backgrounder polls every hour to evaluate alert conditions.

Config: Adjustable (e.g., -v 30 for 30 minutes).

Option D (Whenever extracts in the related workbook are refreshed): Correct.

Details: An extract refresh updates the data, triggering an immediate alert check to catch changes promptly.

Why: Ensures timely notifications without waiting for the next poll.

Option B (Every 10 minutes): Incorrect.

Why: Not the default---possible via config, but not standard.

Option C (Whenever a new extract is published): Incorrect.

Why: Publishing creates the extract; alerts trigger on refreshes or polling, not initial publication.

Why This Matters: Timing affects alert responsiveness---balancing frequency and server load is key.