ベストな準備プランSCA-C01試験2025年最新のTableau Desktop Certified Associate無制限241問題
注目すべき時短になるSCA-C01オールインワン試験ガイド
質問 # 109
Which tsm configuration set option controls whether Tableau Server collects historical user activity and other information in the repository?
- A. auditing.enabled
- B. lineage.activated
- C. lineage.enabled
- D. auditing.activated
正解：A
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/adminview_postgres.htm
質問 # 110
Fill in the blanks: By default, Tableau Services Manager (TSM) and Tableau Server log events at the _____ level
- A. info
- B. trace
- C. debug
- D. warn
正解：A
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/logs_debug_level.htm
質問 # 111
What is the minimum number of Tableau Server nodes required to satisfy High Availability (HA) requirements?
- A. 0
- B. 1
- C. 2
- D. 3
- E. 4
正解：E
質問 # 112
Select all the types of backup data generated by the tsm settings export command:
- A. Extract (.tde or .hyper) files
- B. SMTP, alerting configuration data
- C. Workbook metadata
- D. Tableau Server topology data
正解：B、D
解説：
Link to Tableau Server documentation:
https://help.tableau.com/current/server-linux/en-us/backup_restore.htm
質問 # 113
Which of the following IS NOT a tool that Tableau provides to help you track and manage licensing and usage in your organization?
- A. Tableau Desktop reporting
- B. REST API
- C. Login-based License Usage Report
- D. Virtual Desktop Support
- E. Customer portal
正解：B
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/desktopdeploy/en-us/desktop_deploy_reporting_admin.htm
質問 # 114
Which Tableau Server process is being described?
* Responsible for monitoring various components, detecting failures
* Running failover when needed
* Must be installed on each node
- A. Cache Server
- B. Backgrounder
- C. Ask Data
- D. Cluster Controller
- E. Application Server
正解：D
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/processes.htm
質問 # 115
To ensure that the Coordination Service works properly in a High Availability deployment, it requires a quorum, defined as the minimum number of instances in the service. What is the recommended number of Coordination Service nodes to use in a 4-node deployment of Tableau Server?
- A. 0
- B. 1
- C. 2
- D. 3
- E. 4
正解：D
解説：
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/distrib_ha_zk.htm
質問 # 116
Which Tableau Server tool / functionality should be used to perform the following tasks?
* Initial configuration of Tableau Server after installation
* Ongoing configuration management, including editing settings and changing the server topology
- A. tsm
- B. tabcmd
- C. tabadmin
正解：A
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/tsm_overview.htm
質問 # 117
What is the highest level of access for Tableau Online?
- A. Server Administrator
- B. Site Administrator Creator
- C. Explorer
- D. Site Administrator Explorer
正解：B
解説：
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/online/en-us/users_site_roles.htm
質問 # 118
Which TSM command should you run before migrating a site, in order to detect issues with site content such as workbooks and data sources that will cause a site import to fail?
- A. tsm maintenance validate-content
- B. tsm maintenance validate-resources
- C. tsm maintain validate-content
- D. tsm maintain validate-resources
正解：B
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server-linux/en-us/cli_maintenance_tsm.htm#tsmValidateResources
質問 # 119
What command should you run to update the automatically-generated secrets that are created during a Tableau Server installation?
- A. tsm security regenerate-internal-tokens
- B. tsm data-access caching set -r 1
- C. tsm licenses refresh
- D. tsm security validate-asset-keys
正解：A
解説：
Tableau Server uses internal secrets (tokens) for secure communication between its processes (e.g., Repository, File Store). These are automatically generated during installation and can be regenerated if compromised or for security maintenance. The command to update these is:
* tsm security regenerate-internal-tokens: This regenerates the internal security tokens, ensuring all processes use the new tokens after a restart.
* Option C (tsm security regenerate-internal-tokens): Correct. This is the documented command for updating internal secrets.
* Option A (tsm data-access caching set -r 1): Incorrect. This command configures caching behavior, not security tokens.
* Option B (tsm licenses refresh): Incorrect. This refreshes license data, unrelated to internal secrets.
* Option D (tsm security validate-asset-keys): Incorrect. This validates encryption keys for assets, not internal tokens.
質問 # 120
In the command tsm data-access caching set -r <value>, what value should be set if you want Tableau Server to always get the latest data?
- A. always
- B. live
- C. 0 (zero)
- D. active
正解：A、C
解説：
Explanation
Link to Tableau Server documentation: https://help.tableau.com/current/server/en-us/config_cache.htm
質問 # 121
A user reports that a newly-published workbook runs slowly. What should you ask the user first to investigate the problem?
- A. Does it run any faster in Tableau Desktop?
- B. How many times have you opened the workbook in Tableau Server?
- C. Did you enable caching on the workbook?
- D. Does the workbook always run slowly or does performance vary?
正解：A
解説：
When a user reports slow performance for a newly-published workbook on Tableau Server, troubleshooting requires isolating the cause-e.g., data source issues, server load, workbook design, or caching. Thefirst questionshould establish a baseline to narrow the scope. Let's analyze this step-by-step with depth:
* Performance Context:
* A workbook's speed depends on:
* Data Source: Query complexity, size, network latency (e.g., database vs. extract).
* Workbook Design: Filters, calculations, dashboard complexity.
* Server Resources: VizQL rendering, Backgrounder load, caching.
* "Newly-published" implies it's not yet optimized or cached on the server.
* Option A (Does it run any faster in Tableau Desktop?): Correct.
* Why First: Comparing Desktop vs. Server performance is the most foundational diagnostic step:
* Desktop Baseline: If it's slow in Desktop (local machine), the issue likely lies in the workbook (e.g., complex queries, large data) or data source (e.g., slow database)-not Server-specific.
* Server Difference: If it's fast in Desktop but slow on Server, the problem could be server- side (e.g., resource contention, network latency to the data source from Server).
* Practical Next Steps:
* Slow in Desktop: Optimize workbook (e.g., simplify calcs, use extracts).
* Fast in Desktop: Check Server (e.g., caching, VizQL load).
* Why Critical: Establishes whether the issue is inherent to the workbook/data or introduced by Server-guides all further investigation.
* Option B (Does the workbook always run slowly or does performance vary?): Useful but secondary.
* Why Not First: Variability (e.g., slow at peak times) points to server load, but without a Desktop baseline, you can't rule out workbook design. It's a follow-up question after A.
* Detail: Variability might suggest caching or concurrent user impact, but it assumes Server-side causation prematurely.
* Option C (How many times have you opened the workbook in Tableau Server?): Less relevant initially.
* Why Not First: Frequency of access might affect caching (first load is slower, subsequent loads faster), but it's too specific and doesn't isolate Desktop vs. Server. It's a niche follow-up.
* Option D (Did you enable caching on the workbook?): Misleading and incorrect.
* Why Not First: Caching is server-managed (e.g., VizQL cache settings via tsm data-access caching set), not a user-toggle per workbook. Users don't "enable" it-admins do. Plus, it's premature without a baseline.
Why This Matters: Starting with Desktop performance cuts through assumptions, pinpointing whether the root cause is client-side (workbook/data) or server-side-essential for efficient resolution in production.
質問 # 122
A Tableau Server admin would like to see how many users signed-in to Tableau Server over the past 24 hours.
Which administrative view would contain this information?
- A. Actions by Recent Users
- B. Actions by Specific User
- C. Traffic to Views
- D. Actions by All Users
正解：A
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/adminview_users_recent.htm
質問 # 123
Which three methods should an administrator use to create a Tableau Server group or project? (Choose three.)
- A. Tableau Server browser interface
- B. REST API
- C. tabcmd
- D. tsm customize
正解：A、B、C
解説：
Tableau Server provides multiple methods to creategroups(collections of users) andprojects(content containers), catering to UI, CLI, and programmatic needs. Let's dissect each option with depth:
* Option B (Tableau Server browser interface): Correct.
* Groups: Go toUsers > Groups > Add Group, name it, and optionally sync with Active Directory.
* Projects: Go toContent > Projects > New Project, set name, description, and permissions.
* Details: The web UI is intuitive, requiring server/site administrator rights. It's ideal for manual, ad-hoc creation with immediate visibility.
* Permissions: For projects, you can set default permissions or lock them here.
* Option C (tabcmd): Correct.
* Groups: tabcmd creategroup "GroupName" creates a local group. Add users with tabcmd addusers "GroupName" --users "user1,user2".
* Projects: tabcmd createproject -n "ProjectName" -d "Description" creates a project.
* Details: tabcmd is a command-line tool for batch operations or scripting (e.g., automating group
/project setup). It requires a server admin login (tabcmd login).
* Limitation: No AD sync via tabcmd-that's UI or REST API territory.
* Option D (REST API): Correct.
* Groups: Use the POST /api/api-version/sites/site-id/groups endpoint with a payload (e.g.,
{"group": {"name": "GroupName"}}). Supports AD import too.
* Projects: Use POST /api/api-version/sites/site-id/projects (e.g., {"project": {"name":
"ProjectName", "description": "Desc"}}).
* Details: The REST API is programmatic, ideal for integration with external systems or bulk automation. Requires authentication via a token and server/site admin rights.
* Power: Offers full control, including nested projects and custom permissions.
* Option A (tsm customize): Incorrect.
* Purpose: tsm customize modifies TSM UI branding (e.g., logos, colors) via commands like tsm customize --logo "path/to/logo.png".
* Why Wrong: It's unrelated to creating groups or projects-it's for cosmetic server configuration, not content/user management.
Why This Matters: Offering UI, CLI, and API options ensures flexibility-manual for small tasks, automation for scale-critical in enterprise deployments.
質問 # 124
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. Data is protected so that it is only available in one workbook
- C. Storage space is conserved and resource usage during data refreshes is optimized
- D. Centralized data management is easier
正解：C、D
解説：
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.
質問 # 125
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. 8 cores and 32 GB of RAM
- C. 4 cores and 16 GB of RAM
- D. 4 cores and 32 GB of RAM
正解：C
解説：
Explanation
Link to Tableau Server documentation:
https://help.tableau.com/current/server/en-us/server_hardware_min.htm
質問 # 126
What is the maximum number of tasks that a single Backgrounder process can execute simultaneously?
- A. One
- B. Three
- C. Unlimited (based on server resources)
- D. Two
正解：A
解説：
TheBackgrounderprocess in Tableau Server handles tasks like extract refreshes and subscriptions-let's explore its concurrency:
* Backgrounder Behavior:
* Each instance is single-threaded for task execution-one task at a time per Backgrounder.
* Multiple Backgrounders (e.g., in multi-node setups) increase parallelism, but a single Backgrounder is limited to1 concurrent task.
* Queue: Additional tasks wait in the queue, prioritized by their priority (1-100).
* Option A (One): Correct.
* Details: A single Backgrounder executes one task (e.g., an extract refresh) until completion before starting the next.
* Config: Add more Backgrounders via TSM (tsm topology set-process -n node1 -pr backgrounder
-c 2) for more concurrency.
* Option B (Two): Incorrect.
* Why: Not natively supported-a single Backgrounder doesn't multi-thread tasks.
* Option C (Three): Incorrect.
* Why: Exceeds the single-threaded design.
* Option D (Unlimited): Incorrect.
* Why: Concurrency is fixed at 1 per instance-resources affect queue processing speed, not simultaneous tasks.
Why This Matters: Understanding Backgrounder limits guides scaling-more instances mean more parallel tasks, critical for heavy workloads.
質問 # 127
......
合格保証付きSCA-C01問題集：https://jp.fast2test.com/SCA-C01-premium-file.html
あなたを合格さすTableau SCA-C01試験専門はここにある：https://drive.google.com/open?id=1Vfxq4LzQiKjuVBg_AYhIrpN8ZyAJNc_v