SCA-C01 Sample Questions & Answers

When connecting to file-based data sources like CSV or Excel that are local to the author's machine, Tableau automatically creates an extract and embeds it within the workbook (.twbx) upon publishing. The server has no way to access the original file, so it packages a snapshot of the data.

The correct value is simply the integer representing the new port number. The tsm topology set-ports command is used to modify the ports for various Tableau Server processes.

This is a common and often overlooked issue. If workbooks were published with credentials embedded before they were set to use the published data source connection, they might retain the old, stale credentials. Even if the published data source is updated, the workbook's embedded credentials can override it during a refresh. The solution is to edit the workbooks' connections to remove the embedded credentials and use the published data source's credentials.

This is the correct behavior. The Project Leader role grants the ability to manage the project itself, including its default permission rules. However, when the project is 'Locked', it enforces those default rules on all content within it, and no one, not even the Project Leader, can override them on a per-workbook or per-data-source basis. The lock must be removed first.

The Explorer (can publish) role is specifically for users who need to publish new workbooks from Tableau Desktop but are restricted to using existing published data sources. They cannot publish new data sources.

The Creator role has the highest level of content permissions. Creators can connect to new data, create and publish new data sources, and create and publish new workbooks from Tableau Desktop.

The Guest user feature, which allows for unauthenticated access to views, is only available on Tableau Servers that are licensed on a per-core basis. A user-based license requires every user, including those viewing embedded content, to be a named, licensed user. The fundamental step is to acquire and apply a core-based license.

The tsm maintenance cleanup --http-requests-table command is the specific and correct tool for this task. It purges historical data from the http_requests table in the repository, which is used for administrative monitoring. This is the recommended procedure to reclaim disk space consumed by this table.

This is the ideal solution. Sites in Tableau Server are designed for multi-tenancy, providing a complete wall between content, users, and permissions. Each site can have its own administrator who only has permissions within that site, and users are partitioned by site. This meets all stated requirements for isolation and delegated administration on a single server instance.

This is the core benefit of published data sources. It promotes data governance by creating a reusable, certified data asset. If a database password changes or a calculation is updated, the change only needs to be made once on the published data source, and all connected workbooks will inherit the update. This reduces maintenance overhead and ensures consistency.

The initial server administrator account created during the tabadmin initialuser or web UI setup process is always a local account. This account is necessary to bootstrap the server and log in for the first time to configure the identity store (e.g., to switch to Active Directory). Even if the server is later configured to use AD, this initial local admin account remains.