[Oct 05, 2025] Get New SCA-C01 Certification – Valid Exam Dumps Questions
100% Passing Guarantee - Brilliant SCA-C01 Exam Questions PDF
Tableau SCA-C01 (Tableau Server Certified Associate) Exam is an industry-recognized professional certification exam that validates the skills and knowledge of individuals in managing, administering, and deploying Tableau Server. SCA-C01 exam is designed to test the candidate's competency in Tableau Server architecture, deployment, security, and administration.
NEW QUESTION # 64
For all Active Directory scenarios, which Run As Service Account type should be used?
- A. Domain User Account
- B. Network Service
Answer: A
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/runas.htm
NEW QUESTION # 65
Which of the following is the correct statement about running TSM commands?
- A. You must run TSM commands using Command Prompt, and not PowerShell
- B. You must run TSM commands using PowerShell, and not Command Prompt
Answer: A
Explanation:
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/tsm.htm
NEW QUESTION # 66
Which of the following IS NOT a correct strategy to maximize backup efficiency in Tableau Server?
- A. Co-locating the repository (pgsql) with the Administration Controller node
- B. Co-locating File Store on the same node as the Administration Controller
- C. Co-locating the Data Server with the Administration Controller node
Answer: C
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/db.htm
NEW QUESTION # 67
Which two commands should you run to clear the initial admin user so that you can create a new one?
- A. First: tsm restart; Second: tabcmd initialuser
- B. First: tsm reset; Second: tabcmd adminreset
- C. First: tsm restart; Second: tabcmd adminconfig
- D. First: tsm reset; Second: tabcmd initialuser
Answer: D
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/cli_reset_tsm.htm
NEW QUESTION # 68
When revision history is turned on and then off in Tableau Server, saved revisions are still retained, and new versions overwrite the latest version. What happens when revision history is turned on once again?
- A. Version numbering starts from the earliest, saved version
- B. Version numbering starts from the last, most recent saved revision
Answer: B
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/pro/desktop/en-us/qs_revision_history.htm#more-notes
NEW QUESTION # 69
Which of the following Tableau products are available for an end-user to use with a Creator license?
- A. Tableau Desktop
- B. Tableau Public
- C. Tableau Server
- D. Tableau Prep Builder
Answer: A,B,C,D
Explanation:
Explanation
Link to Tableau Server documentation: https://www.tableau.com/pricing/individual
NEW QUESTION # 70
What should you do to configure the view URL and enable recording for a site that has recording workbook performance metrics enabled?
- A. Type :record_performance=yes& at the end of the view URL, immediately after the session ID
- B. Delete the session ID in the URL and reload the view
- C. Click the Performance link in the toolbar at the top of the view
- D. Type :record_performance=yes& at the end of the view URL, immediately before the session ID
Answer: A
Explanation:
Tableau Server can record performance metrics for workbooks to troubleshoot slow-loading views. This feature must be enabled at the site level (viaSettings > General > Allow Performance Recording). Once enabled, you can trigger recording for a specific view by modifying its URL.
The correct syntax is to append :record_performance=yes& to the view URL, immediatelyafter the session ID
. For example:
* Original
URL: http://server/#/site/my-site/views/workbook/view?:iid=1
* Modified
URL: http://server/#/site/my-site/views/workbook/view?:iid=1:record_performance=yes
&
After loading the view with this parameter, a performance recording is generated and accessible via the Performanceoption in the toolbar.
* Option B (Type :record_performance=yes& at the end of the view URL, immediately after the session ID): Correct. This follows Tableau's documented method for enabling performance recording.
* Option A (Click the Performance link in the toolbar): Incorrect. The Performance link appears only after recording is triggered via the URL; it's not the method to enable it.
* Option C (Type :record_performance=yes& immediately before the session ID): Incorrect. The parameter must follow the session ID (e.g., :iid=1) to function correctly.
* Option D (Delete the session ID in the URL and reload the view): Incorrect. The session ID is required for the view to load properly; removing it breaks the URL.
NEW QUESTION # 71
What statement correctly describes locking permissions to a project?
- A. You can lock permissions to a project by changing Customizable to Locked
- B. You can lock permissions to a project by setting the appropriate Project permission role
- C. Locking permissions to projects must be enabled on the Tableau Server Settings page
- D. Content permissions are locked to a project by default
Answer: A
Explanation:
In Tableau Server,projectsorganize content (workbooks, data sources) and use permissions to control access.
"Locking permissions" restricts how permissions are managed within a project-let's explore this exhaustively:
* Permission Management Modes:
* Managed by Owner: Default mode. Content owners (e.g., workbook publishers) can set permissions on their items, inheriting project defaults as a starting point.
* Locked to the Project: Project-level permissions are enforced, and content owners cannot modify them. This ensures consistency across all items in the project.
* How to Lock:
* In the Tableau Server web UI:
* Go toContent > Projects.
* Select a project, clickActions > Permissions.
* In the Permissions dialog, changePermissions Managementfrom "Customizable" (Managed by Owner) to "Locked."
* Set the desired permissions (e.g., Viewer, Editor) for users/groups, which then apply uniformly to all content.
* Via REST API: Use the updateProject endpoint with "permissionsLocked": true.
* Option B (You can lock permissions to a project by changing Customizable to Locked): Correct.
* Details: This is the precise action in the UI-switching from "Customizable" to "Locked" locks permissions at the project level.
* Impact: Owners lose the ability to override permissions on individual workbooks/data sources, enforcing governance.
* Example: Set "All Users" to Viewer (Locked)-all content in the project is view-only, regardless of owner intent.
* Option A (Locking permissions must be enabled on the Server Settings page): Incorrect.
* Why: Locking is a per-project setting, not a server-wide toggle. The Server Settings page (via TSM) controls global configs (e.g., authentication), not project permissions.
* Option C (Content permissions are locked by default): Incorrect.
* Default: New projects are "Managed by Owner" (Customizable), allowing flexibility unless explicitly locked by an admin.
* Option D (By setting the appropriate Project permission role): Incorrect.
* Confusion: "Project permission role" isn't a term-permissions are set via rules (e.g., Viewer, Editor), but locking is a separate action (Customizable # Locked).
Why This Matters: Locking permissions ensures uniform access control, critical for regulated environments or large teams where consistency trumps flexibility.
NEW QUESTION # 72
Fill in the blanks: If you are adding Tableau Prep Conductor to your Tableau Server installation, it is recommended that you add a second node and dedicate this to running Tableau Server Prep Conductor. This node should have a minimum of ___ cores (8 vCPUs), and ___ GB of RAM
- A. 8 cores and 64 GB of RAM
- B. 4 cores and 32 GB of RAM
- C. 8 cores and 32 GB of RAM
- D. 4 cores and 16 GB of RAM
Answer: D
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/server_hardware_min.htm
NEW QUESTION # 73
An admin came across this error in Windows Event Viewer: "Error sending email. Can't send command to SMTP host." - what is a potential solution to this problem?
- A. Configure your SMTP server to use encrypted (SSL) sessions
- B. Change your SMTP connections setting to unencrypted
- C. Upgrade the users to an Explorer license so that they can receive notifications
Answer: B
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/subscribe_trouble.htm
NEW QUESTION # 74
If you later decide that you want to disable remote access to the Tableau Server repository, which command should you run?
- A. tsm data-access repository-access close
- B. tsm data-access repository-access disable
- C. tsm postgres-repository disable
Answer: B
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/perf_collect_server_repo.htm
NEW QUESTION # 75
You attempt to delete a user who owns content on a Tableau Server. What is the result of the delete action?
- A. The user is deleted, and the user's content is reassigned to the server administrator
- B. The user is deleted, and the user's content is reassigned to the project leader
- C. The user and all of the user's content is deleted
- D. The user is switched to an Unlicensed site role and is NOT deleted
Answer: D
Explanation:
Deleting a user in Tableau Server involves handling their owned content (workbooks, data sources)-let's analyze the process:
* Deletion Rules:
* Ownership Check: Tableau prevents deletion if the user owns content to avoid orphaning it.
* Action: Instead of deleting, the user's site role is set toUnlicensed, retaining their account and content ownership.
* Resolution: An admin must reassign ownership (e.g., viaUsers > Actions > Change Owner) before deletion.
* Option D (User switched to Unlicensed and NOT deleted): Correct.
* Details: Attempting deletion (e.g.,Users > Select User > Actions > Delete) triggers a check. If content exists, the user becomes Unlicensed-still in the system but unable to log in.
* Why: Protects data integrity-content remains accessible for reassignment.
* Option A (Deleted, content to server admin): Incorrect.
* Why: No automatic reassignment to the server admin-manual action is required first.
* Option B (Deleted, content to project leader): Incorrect.
* Why: Project leaders don't automatically inherit content-no such mechanism exists.
* Option C (User and content deleted): Incorrect.
* Why: Tableau avoids deleting content with the user-too destructive without explicit intent.
Why This Matters: This safeguard prevents accidental data loss, ensuring admins manage ownership transitions deliberately.
NEW QUESTION # 76
Which of the following statements below accurately describe the effect of Anti-Virus software on Tableau Server?
- A. Excluding Tableau Server folders and sub-folders in ant-virus scanning will improve server performance
- B. Scanning the Tableau Server log files only will improve performance
- C. Including Tableau Server folders and sub-folders in ant-virus scanning will improve server performance
Answer: A
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/requ.htm
NEW QUESTION # 77
Which TSM command should you run to rebuild the search index and reset the search server back to a clean slate?
- A. tsm maintenance rebuild-index
- B. tsm maintenance reset-searchserver
- C. tsm maintenance reset-searchindex
- D. tsm maintenance rebuild-search
Answer: B
Explanation:
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/cli_maintenance_tsm.htm#tsm_maint_reset_searchsvr
NEW QUESTION # 78
Which three types of authentications can you use to implement single-sign-on (SSO) authentication to Tableau Server? (Choose three.)
- A. Local Authentication
- B. Kerberos with Active Directory
- C. Security Assertion Markup Language (SAML)
- D. OpenID Connect
Answer: B,C,D
Explanation:
Single Sign-On (SSO) allows users to authenticate once (e.g., via a corporate identity provider) and access Tableau Server without re-entering credentials. Tableau Server supports several SSO methods:
* OpenID Connect (OIDC): An OAuth 2.0-based protocol for SSO, configured via Tableau's SAML settings with an OIDC-compatible IdP (e.g., Google, Okta).
* Kerberos with Active Directory: A ticket-based SSO protocol, widely used in Windows environments with AD integration.
* SAML: A flexible SSO standard using XML assertions, supporting various IdPs (e.g., ADFS, PingFederate).
Let's evaluate:
* Option A (OpenID Connect): Correct. OIDC is an SSO method, implemented as a SAML variant in Tableau Server, enabling seamless login.
* Option C (Kerberos with Active Directory): Correct. Kerberos provides SSO in AD environments, delegating authentication to the domain controller.
* Option D (Security Assertion Markup Language - SAML): Correct. SAML is a core SSO method in Tableau, widely adopted for enterprise integrations.
* Option B (Local Authentication): Incorrect. Local Authentication uses Tableau's internal user database, requiring manual credential entry-no SSO support.
Why This Matters: SSO enhances user experience and security by leveraging existing identity systems, reducing password fatigue.
NEW QUESTION # 79
True or False: Server administrators do not count against site role limits
- A. TRUE
- B. FALSE
Answer: A
Explanation:
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/site_role_limit.htm
NEW QUESTION # 80
Several Tableau Server users published workbooks that have large extracts. After several weeks of use, the users abandoned the workbooks. What should you do to identify the abandoned workbooks?
- A. Examine the extract files in ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract
- B. Use the Stale Content administrative view
- C. View all workbooks, and sort by the Modified date
- D. Delete all extracts and allow them to be re-generated automatically if they are still in use
Answer: B
Explanation:
Abandoned workbooks-those no longer actively used-can clutter Tableau Server and consume resources (e.
g., disk space for extracts). Identifying them efficiently requires leveraging built-in administrative tools rather than manual or destructive methods. Let's explore this in depth:
* Tableau Server Admin Views: Tableau provides pre-built administrative views to monitor server health, usage, and content. TheStale Contentview, accessible underServer > Status > Administrative Views, is specifically designed to identify content (workbooks, data sources) that hasn't been viewed or modified recently. It shows:
* Content name, owner, and project.
* Last viewed date and last modified date.
* View count over a period.This view uses Repository data to track usage metrics, making it ideal for spotting abandoned workbooks.
* Option A (Use the Stale Content administrative view): Correct. This is the most efficient and non- invasive method. You can filter by last viewed date (e.g., >30 days ago) to identify workbooks with large extracts that users have stopped accessing. From there, you can contact owners or delete the content if policy allows. It's a server administrator's go-to tool for content management.
* Option B (Examine extract files in ProgramData/.../extract): Incorrect and impractical. The ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract directory stores .hyper extract files, but:
* File names are cryptic (e.g., GUIDs), not tied directly to workbook names.
* It doesn't indicate usage or abandonment-only file presence and size.
* Manual inspection is time-consuming and error-prone compared to the Stale Content view.
* Option C (Delete all extracts and allow them to be re-generated): Incorrect and risky. Deleting extracts (e.g., via tsm maintenance cleanup) removes them without identifying usage. Regeneration only occurs if a schedule or user triggers it, potentially disrupting active users and losing historical data unnecessarily.
* Option D (View all workbooks, and sort by the Modified date): Partially effective but inefficient. In the Tableau Server UI (e.g., underContent > Workbooks), you can sort by "Last Modified," but:
* It doesn't show viewership (a workbook might be modified recently but unused).
* It's manual and doesn't scale for large deployments compared to the Stale Content view.
Why This Matters: The Stale Content view leverages Tableau's metadata to provide actionable insights, saving time and reducing risk compared to manual or destructive alternatives. It's part of Tableau's governance toolkit.
NEW QUESTION # 81
......
Free SCA-C01 braindumps download: https://examtorrent.actualtests4sure.com/SCA-C01-practice-quiz.html
