Free Analytics-Admn-201 sample questions

Correct answer: Backgrounder

The Backgrounder process runs server tasks including extract refreshes, subscriptions, and data-driven alerts. It consumes significant CPU resources, which is why it is often isolated on a specific node in a distributed cluster to avoid impacting user interactivity handled by the VizQL Server.

Correct answer: When using Active Directory as the identity store, Tableau Server does not manage credentials and cannot modify the external directory.

When configured with an external identity store like Active Directory (or LDAP), Tableau Server delegates authentication to that store. Tableau treats the external directory as read-only regarding credentials. Users must change their passwords through Windows or their corporate identity management tools, not within Tableau Server.

Correct answer: PEM (Privacy Enhanced Mail)

Tableau Server requires SSL certificates to be in PEM-encoded x509 format. The certificate file usually has a .crt extension, and the key file is a .key extension. If you have a PFX file, it must be converted to PEM format before it can be used in TSM configuration.

Correct answer: Denied, because a Deny permission always overrides an Allow permission.

In the Tableau security model, a specific 'Deny' always takes precedence over an 'Allow'. Even though Group B grants John access, the explicit Deny on Group A (of which he is a member) overrides the Allow, resulting in John being unable to view the workbook. This is a critical security feature to ensure restrictions are enforced.

Correct answer: tsm maintenance backup -f

The `tsm maintenance backup` command is used to create a backup of the repository and file store data. The `-f` flag specifies the filename. Note that to perform a full disaster recovery, you should also export the configuration settings using `tsm settings export`, as the backup file contains data but not all server configuration topology.

Correct answer: Balanced

The 'Balanced' caching configuration is designed to remove items from the cache after a specified number of minutes. This provides a middle ground where data is cached for performance but refreshed periodically to ensure data freshness. 'Refresh Less Often' caches data for up to 12 hours (or longer depending on config), which causes the issue described. 'Always Refresh' hits the database every time, hurting performance.