SCA-C01のPDF問題集リアル2025最近更新された問題
リリースTableau SCA-C01更新された問題PDF
質問 # 111
A user is trying to access an embedded dashboard on a web portal, but the visualization is not showing up.
Which of the following options is the most plausible root cause for this?
- A. VizQL is down and cannot render the visualization properly
- B. The Gateway process in Tableau Server is down
- C. The user's browser is set to block first-party cookies
- D. The user's browser is set to block third-party cookies
- E. The user's browser is set to block second-party cookies
正解：D
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server-linux/en-us/trusted_auth_trouble_cookie.htm
質問 # 112
Select the correct Tableau Server monitoring tool that is being described:
* A "point-and-run" load and performance testing tool specifically designed to work easily with Tableau Server
* Used to inform scalability and capacity needs for Tableau Server
* Used to establish a baseline for server performance and test deployments before pushing them to production environments
- A. Scout
- B. Replayer
- C. TabJolt
- D. TabMon
正解：C
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/perf_resources.htm
質問 # 113
Backward Compatibility Scenario (True or False):
* Suppose Linus publishes a workbook from Tableau Desktop 2018.2 to Tableau Server 2020.1
* Steph downloads the workbook from Tableau Server to Tableau Desktop 2020.1 - she does some edits and republishes the workbook back to the server
* Charles and Raina, who are both using Tableau Desktop 2018.2, can download the workbook, but cannot open the workbook
- A. TRUE
- B. FALSE
正解：A
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/desktopdeploy/en-us/desktop_deploy_compatibility.htm#downloading-workboo
質問 # 114
Which three types of authentications can be used with user-based licensing? (Choose three.)
- A. Trusted authentication
- B. Reliance authentication
- C. Active Directory
- D. Local authentication
正解：A、C、D
解説：
Tableau Server'suser-based licensing(Creator, Explorer, Viewer) ties licenses to individual users-let's determine compatible authentication methods:
* User-Based Licensing:
* Licenses are assigned per user, tracked by username.
* Authentication determines how users log in-must integrate with licensing.
* Option A (Local authentication): Correct.
* Details: Users are managed in Tableau Server's internal database-username/password set manually or via import.
* Why: Directly ties to user accounts, fully compatible with licensing.
* Option C (Trusted authentication): Correct.
* Details: Allows external apps to authenticate users via tickets (e.g., /trusted/<ticket>).
* Why: Maps to Tableau usernames, integrating with licensing-common for embedded analytics.
* Config: Trusted IPs or credentials set in TSM.
* Option D (Active Directory): Correct.
* Details: Uses AD for authentication (LDAP or Kerberos)-users sync to Tableau Server.
* Why: AD usernames align with licensing-supports SSO and user management.
* Config: Enable via tsm authentication active-directory configure.
* Option B (Reliance authentication): Incorrect.
* Why: Not a recognized Tableau authentication method-likely a typo (e.g., for "Resilience" or misheard term). No such feature exists.
Why This Matters: Authentication flexibility ensures user-based licensing fits diverse IT environments- critical for adoption.
質問 # 115
The Tableau Server repository is a PostgreSQL database that stores data about all user interactions, extract refreshes, and more.
You can use Tableau Desktop to connect to and query the Tableau Server repository using two built-in users.
Select the two user types that allow you to access the database tables and views:
- A. readonly
- B. tableau
- C. viewonly
- D. tabserver
正解：A、B
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/perf_collect_server_repo.htm
質問 # 116
Which of the following statements is correct about where you can configure site role limits?
- A. You can configure site role limits through the Settings page in the web UI, or through the TSM web UI
- B. You can configure site role limits through the Settings page in the web UI, or through the REST API.
正解：B
解説：
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/site_role_limit.htm
質問 # 117
Which two commands are valid and complete commands? (Choose two.)
- A. tsm maintenance ziplogs
- B. tsm maintenance cleanup
- C. tsm maintenance restore
- D. tsm maintenance backup
正解：A、B
解説：
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.
質問 # 118
How many types of backup data does Tableau Server generate?
- A. 0
- B. 1
- C. 2
- D. 3
正解：B
解説：
Link to Tableau Server documentation:
https://help.tableau.com/current/server-linux/en-us/backup_restore.htm
質問 # 119
Which two statements are advantages of published data sources in comparison to embedded data sources?
(Choose two.)
- A. Drivers are automatically installed on each client's machine
- B. Storage space is conserved and resource usage during data refreshes is optimized
- C. Centralized data management is easier
- D. Data is protected so that it is only available in one workbook
正解：B、C
解説：
In Tableau, data sources can beembedded(stored within a workbook) orpublished(stored separately on Tableau Server). Let's define these and analyze the advantages:
* Embedded Data Source: The connection details and any extract are bundled in the .twb or .twbx file.
Each workbook manages its own copy.
* Published Data Source: The connection or extract is hosted on Tableau Server, reusable across multiple workbooks.
Now, let's evaluate the options:
* Option C (Centralized data management is easier): Correct. Published data sources allow:
* Single source of truth: One data source can serve multiple workbooks, ensuring consistency.
* Unified updates: Refresh schedules, permissions, and metadata (e.g., calculated fields) are managed in one place via the Server UI.
* Governance: Administrators can control access and monitor usage centrally.In contrast, embedded data sources require individual updates per workbook, leading to duplication and management overhead.
* Option D (Storage space is conserved and resource usage during data refreshes is optimized):
Correct. With published data sources:
* Storage: A single extract on the Server (e.g., a .hyper file) is shared across workbooks, avoiding redundant copies stored in each embedded workbook.
* Refreshes: One refresh job updates the shared extract, reducing CPU and memory usage compared to multiple refreshes for duplicate embedded extracts.Embedded data sources replicate extracts, increasing disk space and refresh load.
* Option A (Data is protected so that it is only available in one workbook): Incorrect. This describes embedded data sources, not published ones. Published data sources are shared, not restricted to one workbook-permissions control access, not exclusivity.
* Option B (Drivers are automatically installed on each client's machine): Incorrect. Drivers (e.g., for SQL Server, PostgreSQL) must be installed on the Server hosting the published data source, not client machines. This is unrelated to the published vs. embedded distinction.
Why This Matters: Published data sources enhance scalability and efficiency in enterprise deployments, making them a cornerstone of Tableau Server's data strategy.
質問 # 120
What is the highest level of access for Tableau Online?
- A. Site Administrator Explorer
- B. Server Administrator
- C. Explorer
- D. Site Administrator Creator
正解：D
解説：
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/online/en-us/users_site_roles.htm
質問 # 121
If you later decide that you want to disable remote access to the Tableau Server repository, which command should you run?
- A. tsm postgres-repository disable
- B. tsm data-access repository-access close
- C. tsm data-access repository-access disable
正解：C
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/perf_collect_server_repo.htm
質問 # 122
Select all the site roles that can be assigned to a person with an Explorer license:
- A. Server Administrator
- B. Read Only
- C. Site Administrator Explorer
- D. Explorer (Can publish)
- E. Explorer
正解：A、B、C、D、E
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/users_site_roles.htm
質問 # 123
Select the correct statement below. Assume that the project content permissions are set to 'Customizable':
- A. If there are nested projects, permissions at the child level take precedence over permissions at the parent level
- B. If there are nested projects, permissions at the parent level take precedence over permissions at the child level
正解：A
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/permissions.htm
質問 # 124
What statement correctly describes locking permissions to a project?
- A. You can lock permissions to a project by setting the appropriate Project permission role
- B. Locking permissions to projects must be enabled on the Tableau Server Settings page
- C. You can lock permissions to a project by changing Customizable to Locked
- D. Content permissions are locked to a project by default
正解：C
解説：
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.
質問 # 125
What happens if you import users to the server, but not to a specific site?
- A. The users are not assigned to a particular site and will be Unlicensed
- B. Tableau Server will generate an error and will not complete the operation
正解：A
解説：
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/csvguidelines.htm
質問 # 126
Which of the following processes are NOT licensed? (Select all)
- A. Cluster Controller
- B. Backgrounder
- C. Ask Data
- D. Cache Server
- E. Data Engine
- F. Application Server
正解：A、D、E
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/processes.htm
質問 # 127
True or False:
If you use Tableau Online instead of an on-prem installation of Tableau Server, all supported drivers are already available to data sources published to your Tableau Online site
- A. TRUE
- B. FALSE
正解：A
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/datasource.htm
質問 # 128
What two events must occur for Tableau Server to recompute queries for a workbook cache after a scheduled refresh? (Choose two.)
- A. The workbook was published in the last month
- B. The workbook has been viewed recently
- C. The workbook has upcoming scheduled refresh tasks
- D. The All Users group has a permission rule allowing access to the workbook
正解：B、C
解説：
Tableau Server uses caching to speed up workbook loading by storing query results. After a scheduled extract refresh updates the data, the cache may need recomputing-let's dive into the mechanics:
* Caching Basics:
* VizQL Cache: Stores rendered views and query results for faster access.
* Refresh Trigger: A scheduled refresh updates the underlying extract (.hyper), but the cache isn't automatically invalidated-it's demand-driven.
* Recompute Conditions: Tableau recomputes the cache when the workbook is accessed (viewed) and its data has changed (e.g., via refresh).
* Evaluation:
* Option B (The workbook has upcoming scheduled refresh tasks): Correct.
* Why: An upcoming refresh task indicates the workbook relies on an extract with a schedule. After the refresh runs, the data changes, priming the cache for recomputation on next view. Without a schedule, no refresh occurs, so this is a prerequisite.
* Detail: Schedules are set inSchedules > Tasks-e.g., "Daily at 2 AM."
* Option D (The workbook has been viewed recently): Correct.
* Why: Viewing triggers cache recomputation if the data has changed (e.g., post-refresh).
Tableau uses a "lazy caching" model-cache updates only when a user loads the workbook, ensuring fresh results.
* Detail: "Recently" isn't strictly defined but implies post-refresh access.
* Option A (Published in the last month): Incorrect.
* Why: Publish date is irrelevant-cache recomputation ties to data changes and access, not publication timing.
* Option C (All Users group has permission rule allowing access): Incorrect.
* Why: Permissions enable viewing, but recomputation requires actual access (viewing) and a refresh event, not just potential access.
Why This Matters: Caching balances performance and freshness-understanding triggers prevents stale data surprises.
質問 # 129
What should you do to disable table recommendations for popular data sources and tables to users?
- A. Disable the option using the server Settings page
- B. Use the command: tsm configuration set -k recommendations.enabled -v false
- C. Disable the option using the site Settings page
- D. Publish data sources only to projects with permissions locked to the project
正解：C
解説：
Table recommendations in Tableau Server suggest popular tables and data sources to users when they create new content in the web authoring environment. This feature is enabled by default but can be disabled at the site level.
Option A (Disable the option using the site Settings page): Correct. A site administrator can disable table recommendations by navigating to the site's Settings > General page in the Tableau Server web interface and unchecking the option "Enable table recommendations." This prevents users on that site from seeing these suggestions, offering a straightforward UI-based solution.
Option B (Use the command: tsm configuration set -k recommendations.enabled -v false): Incorrect. There is no recommendations.enabled key in the TSM configuration settings. This feature is managed per site, not server-wide via TSM.
Option C (Publish data sources only to projects with permissions locked): Incorrect. Locking permissions restricts access but doesn't disable the recommendation feature itself. Users with access would still see recommendations.
Option D (Disable the option using the server Settings page): Incorrect. Table recommendations are a site- specific setting, not a server-wide setting. The server Settings page (via TSM) controls global configurations, not this feature.
質問 # 130
A user receives an error after attempting to run an extract refresh on the Tableau Server. What should you review to identify the cause of the problem?
- A. The Background Tasks for Extracts administrative view on the site status page
- B. The UNC path to the extract's data source
- C. The status of the Backgrounder process, as shown by the tsm status -v command
- D. Whether the project permissions are set to Locked to the project
正解：A
解説：
When an extract refresh fails on Tableau Server, troubleshooting requires identifying the root cause-e.g., connectivity issues, resource constraints, or configuration errors. TheBackgrounderprocess handles extract refreshes, so it's a key focus, but the best diagnostic tool depends on granularity and context. Let's explore this thoroughly:
* Extract Refresh Process:
* An extract refresh pulls data from a source (e.g., database, file) into a .hyper file stored on Tableau Server.
* The Backgrounder executes these tasks based on schedules or manual triggers.
* Errors could stem from: database connectivity, credentials, file access, resource overload, or task misconfiguration.
* Option B (Background Tasks for Extracts administrative view): Correct. This is the most direct and detailed method:
* Location: In the Tableau Server web UI, go toServer > Status > Background Tasks for Extracts(or site-specific underSite > Status).
* Details Provided:
* Task name, schedule, and workbook/data source.
* Start/end times and status (e.g., Failed, Success).
* Error messages (e.g., "Cannot connect to database," "Permission denied").
* Why It's Best: It pinpoints the exact failure (e.g., "timeout," "invalid credentials") for the specific refresh, offering actionable insights without needing to dig through logs manually. Server or site administrators can access this view to diagnose issues quickly.
* Example: If the error is "Database login failed," you'd check credentials in the data source settings next.
* Option A (Status of the Backgrounder process via tsm status -v): Partially useful but insufficient:
* What It Shows: Running/stopped status of all processes (e.g., "Backgrounder: RUNNING").
* Limitation: It confirms if Backgrounder is operational but doesn't reveal why a specific task failed-no error details or task-level granularity.
* Use Case: If Backgrounder is stopped or crashed, this might indicate a broader issue, but the question implies a single refresh error, not a server-wide failure.
* Option C (The UNC path to the extract's data source): Relevant but secondary:
* Context: If the data source is a file (e.g., CSV on a network share), the UNC path (e.g.,
\\server\share\file.csv) must be accessible.
* Why Not First: The error could be unrelated (e.g., database issue, not file-based). The admin view (B) would reveal if it's a path issue first, guiding you to check the UNC path only if indicated (e.g., "File not found").
* Practical Note: Backgrounder needs share permissions and the Run As account must access it- checking this without context wastes time.
* Option D (Whether project permissions are set to Locked): Unlikely cause:
* Permissions Impact: Locked permissions restrict who can edit/view content, not whether an extract refresh runs-that's tied to the data source's connection settings and Backgrounder execution.
* Exception: If the refresh user lacks "Connect" permission to the data source, it might fail, but this is rare (owner/schedule typically has access). The admin view would flag this.
Why This Matters: The Background Tasks view is Tableau's purpose-built tool for extract diagnostics, saving time and reducing guesswork in production environments.
質問 # 131
A user is complaining that she cannot see the subscription icon that typically resides in the upper right corner of the Tableau Server UI - which of the following reasons below IS NOT a plausible explanation for this?
- A. Tableau Server is configured for trusted authentication
- B. No subscriptions have been scheduled
- C. Tableau Server is configured using SAML authentication
- D. Tableau Server is configured using Kerberos authentication
- E. The view uses a live database connection so it's not available for subscription
正解：C、D
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/subscribe_trouble.htm#no-subscription-icon
質問 # 132
If you want to generate a list of licenses that are activated on your Tableau Server deployment, which TSM command should you run?
- A. tsm licenses list
- B. tsm list-licenses
- C. tsm licenses get
正解：A
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/cli_licenses_tsm.htm#tsm-licenses-list
質問 # 133
True or False: Server administrators do not count against site role limits
- A. TRUE
- B. FALSE
正解：A
解説：
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/site_role_limit.htm
質問 # 134
......
SCA-C01問題集と練習テスト（241試験問題)：https://www.jpntest.com/shiken/SCA-C01-mondaishu
ガイド（2025年最新）実際のTableau SCA-C01試験問題：https://drive.google.com/open?id=1gk6EI5pVjrL3kDfG3FXhteDxB9UcZ57f