SCA-C01 Tableau Server Certified Associate Practice Questions

Many tsm commands that alter the server's configuration do not take effect immediately. They are staged as a pending change. The tsm pending-changes apply command is the final step that validates these staged changes and commits them to the server's configuration. This often, but not always, triggers a server restart to make the new configuration active.

This is true. For security best practices, the Run As service account should be a standard domain user with the minimum necessary permissions. It should have 'Log on as a service' rights and specific folder permissions granted by the installer, but it should not be a member of the local Administrators group.

This is the most common reason for this specific message. An author likely edited the published data source, changed its connection type from 'Extract' to 'Live' in Tableau Desktop, and then re-published it. The refresh schedule remains associated with the data source, but when the Backgrounder attempts to run it, it sees the connection is now live and cancels the task because there is no extract to refresh.

This is the first step. The administrator must define the desired baseline permissions at the project level. These permissions will then be inherited by all content within the project.

This is the critical second step. Setting the permissions to 'Locked' (as opposed to 'Customizable' or 'Managed by owner') forces all workbooks and data sources within the project to inherit the permissions set on the project itself. It prevents content owners from changing them.

When a large workbook is published, it is sent as a single large HTTP POST request. The gateway process (or an external load balancer in front of it) often has a maximum request body size limit to prevent denial-of-service attacks. If the workbook file exceeds this limit, the connection will be terminated, often resulting in a timeout error on the client side. The administrator would need to increase this limit via a tsm command.

The tsm security internal-ssl enable command is specifically designed to enable SSL encryption for all communication between the various processes that make up Tableau Server, such as the Repository, VizQL Server, and Data Server. This is a crucial step for environments with high security requirements.

The Backgrounder process is the primary component for running background tasks like extract refreshes, subscriptions, and flows. It is the most critical process for a dedicated backgrounder node.

The Data Server manages connections to Tableau data sources. Placing it with the Backgrounder and Data Engine helps optimize the data flow during extract refreshes, as these processes work closely together.

The Data Engine (which creates extracts and answers queries against them) works in conjunction with the Backgrounder during extract creation and refreshes. Co-locating them on the same node is a best practice for performance.

This is true. The Explorer (can publish) site role is specifically designed for users who need to author new content based on existing data sources but do not need to publish new data sources. This role allows them to create and publish workbooks to projects where they have the necessary publishing rights.

The REST API is the most powerful tool for this task. It allows a script to download the workbook from the Development site, query its connections, update the connection details to point to the Production data source, and then publish the modified workbook to the Production site. This provides the flexibility needed for a true CI/CD (Continuous Integration/Continuous Deployment) workflow.

This plan correctly addresses all requirements. It uses AD authentication and full SSL encryption. It correctly isolates publishing rights in the 'PHI Certified' project to the Data Steward by locking permissions. It gives Clinical Analysts the ability to create/edit workbooks as required, and it properly restricts Hospital Management to view-only access by locking their permissions. This demonstrates a robust, multi-layered permission strategy.