[2026年10月]更新のSalesforce Analytics-Admn-201テストエンジンとPDFで完全版無料問題集を無料提供
最新版を今すぐ試そうAnalytics-Admn-201認定有効な試験問題集
質問 # 35
You need to ensure that Tableau Server requires the setup of a new administrator account the next time you attempt to log in. What should you do?
- A. Edit tabsvc.yml
- B. Reinstall Tableau Server
- C. Run the tsm reset command
- D. Run the tsm register command
正解：C
解説：
To force Tableau Server to require the setup of a new administrator account (e.g., resetting the server to an initial setup state), the tsm reset command is the appropriate tool. This command resets Tableau Server's administrative configuration, including the TSM administrator account, while preserving content like workbooks and data sources.
Option B (Run the tsm reset command): Correct. Running tsm reset clears the current TSM administrator credentials and configuration settings. The next time you access TSM (e.g., via the web interface or CLI), it prompts you to set up a new administrator account, mimicking the initial setup process. Command: tsm reset --username <new-username> --password <new-password>.
質問 # 36
Which Tableau Server process performs the role of a database for metadata?
- A. Repository
- B. Data Engine
- C. Backgrounder
- D. File Store
正解：A
解説：
Tableau Server relies on several processes to function, each with a specific role. The Repository process (powered by PostgreSQL) serves as the database for metadata, storing critical information such as:
User and group details.
Permissions and site configurations.
Workbook and data source metadata (e.g., schedules, subscriptions). Option B (Repository):
Correct. The Repository is the centralized database that holds all metadata, making it the backbone of Tableau Server's content management. There are typically two instances in an HA setup (one active, one passive), monitored by the Cluster Controller.
質問 # 37
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. Use the Stale Content administrative view
- B. Delete all extracts and allow them to be re-generated automatically if they are still in use
- C. View all workbooks, and sort by the Modified date
- D. Examine the extract files in ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract
正解：A
解説：
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. The Stale Content view, accessible under Server > 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., under Content > 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.
Reference: Tableau Server Documentation - "Administrative Views" (https://help.tableau.com/current/server
/en-us/adminview_stale_content.htm).
質問 # 38
What does locking permissions on a project accomplish?
- A. It hides the project from the site's navigation
- B. It prevents any user from viewing content in the project
- C. It enforces the project's default permission rules on all content within it, preventing individual overrides
- D. It disables publishing to the project entirely
正解：C
解説：
Locking a project's permissions ensures all content inside (including in sub-projects) uses the project-level default permission rules, and publishers/owners cannot set custom permissions on individual items - useful for standardized governance.
質問 # 39
What event is most likely to cause problems for a Tableau Server?
- A. Configuring the server to use a static IP address
- B. Running additional software on the server
- C. Separating the Backgrounder and VizQL processes to different machines
- D. Using a non-default installation path
正解：B
解説：
Tableau Server's performance and stability depend on dedicated resources and proper configuration. Running additional software on the same server is the most likely to cause problems because:
Resource contention: Tableau Server requires significant CPU, RAM, and disk I/O. Other software (e.g., databases, web servers) can compete for these resources, leading to slowdowns, crashes, or failed tasks.
Port conflicts: Tableau uses specific ports (e.g., 80, 443, 8850), and other applications might interfere. Security risks: Additional software increases the attack surface, potentially compromising Tableau Server.
Tableau recommends running the server on dedicated hardware without unrelated applications.
Option A (Running additional software on the server): Correct. This is a common cause of performance issues and is explicitly discouraged in Tableau's best practices.
質問 # 40
Which three types of data should you backup to ensure that you can restore a Tableau Server?
(Choose three.)
- A. Repository data
- B. Server secrets and Repository passwords
- C. Configuration data
- D. Topology data
正解：A、B、C
解説：
Backing up Tableau Server ensures recovery from failures or migrations. A full backup includes multiple data types--let's dissect this comprehensively:
Backup Components:
Repository Data: PostgreSQL database with metadata (users, permissions, workbooks). Backed up via tsm maintenance backup -f <filename>.tsbak.
Configuration Data: Server settings (e.g., ports, authentication) also in the .tsbak file. Server Secrets: Encryption keys, internal tokens, Repository passwords--critical for restoring functionality.
Extracts: .hyper files in File Store (optional, separate backup).
Option A (Server secrets and Repository passwords): Correct. Details: Includes encryption keys (for extracts), internal tokens (process communication), and Repository credentials. Backed up separately or stored securely (e.g., tsm security export-keys). Why Critical: Without these, restored data may be inaccessible or services may fail.
Option C (Configuration data): Correct.
Details: Ports, authentication settings, process topology--part of the .tsbak file. Why Critical:
Restores server behavior and connectivity post-recovery.
Option D (Repository data): Correct.
Details: Core metadata database--also in .tsbak.
Why Critical: Without it, all content and user data is lost.
質問 # 41
What process decides when a Repository failover is required?
- A. Cluster Controller
- B. Coordination Service
- C. Backgrounder
- D. Gateway
正解：A
解説：
In a high-availability (HA) Tableau Server setup, the Repository (PostgreSQL) has an active and passive instance. Failover occurs if the active Repository fails. Let's dive into the process:
* HA Setup:
* Two Repository instances across nodes (active/passive).
* Failover switches to the passive instance if the active one becomes unavailable (e.g., crash, network issue).
* Cluster Controller:
* Role: Monitors all processes (e.g., Repository, File Store) across nodes, detecting failures via heartbeats and status checks.
* Failover Decision: If the active Repository stops responding, Cluster Controller initiates failover, promoting the passive instance to active.
* Coordination: Works with Coordination Service (ZooKeeper) to update topology but makes the initial detection call.
* Option A (Cluster Controller): Correct.
* Why: It's the watchdog process, constantly monitoring Repository health and triggering failover when needed.
* Option B (Coordination Service): Incorrect.
* Role: ZooKeeper maintains cluster state and coordinates topology updates post-failover, but doesn't detect the failure-Cluster Controller does.
* Option C (Gateway): Incorrect.
* Role: Routes client requests-unrelated to internal process monitoring or failover.
* Option D (Backgrounder): Incorrect.
* Role: Executes background tasks-no involvement in Repository failover decisions.
Why This Matters: Understanding failover ensures HA reliability-Cluster Controller is the linchpin for resilience.
Reference: Tableau Server Documentation - "High Availability" (https://help.tableau.com/current/server/en-us
/ha.htm).
質問 # 42
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 security validate-asset-keys
- C. tsm data-access caching set -r 1
- D. tsm licenses refresh
正解：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.
質問 # 43
Which metric would an administrator most likely check in the Server Status / Resource Monitoring Tool to diagnose slow dashboard load times?
- A. Number of active sites
- B. VizQL Server CPU and memory utilization
- C. Site storage quota usage
- D. Number of configured schedules
正解：B
解説：
Since VizQL Server renders views for users, high CPU/memory pressure on that process is a primary cause of slow dashboard rendering. Site counts, schedule counts, and storage quota relate to capacity/governance, not real-time rendering performance.
質問 # 44
Which two tasks always require a server administrator? (Choose two.)
- A. Locking project permissions
- B. Creating a schedule
- C. Adding users
- D. Adding a site
正解：C、D
解説：
In Tableau Server, roles and permissions dictate who can perform specific administrative tasks. A "server administrator" has full control over the entire Tableau Server deployment, while site administrators manage specific sites. Some tasks are restricted to server administrators due to their server-wide impact.
Option B (Adding a site): Creating a new site in a multi-site Tableau Server environment is a server-level task that only a server administrator can perform. Sites are logical partitions within the server, and adding a site affects the overall server structure. Site administrators cannot create new sites; they can only manage existing ones.
Option D (Adding users): Adding users to Tableau Server (e.g., via the TSM interface or tabcmd) is a server administrator task when it involves adding users at the server level or assigning them to the default site. While site administrators can add users to their specific site in a multi-site environment, the initial addition of users to the server requires server administrator privileges. The question's phrasing ("always require") suggests a server-wide context, making this a correct choice.
Option A (Creating a schedule): This is incorrect because both server administrators and site administrators can create schedules for tasks like extract refreshes or subscriptions within their scope. It's not exclusive to server administrators.
Option C (Locking project permissions): This is incorrect because locking project permissions can be done by a site administrator or project leader with appropriate permissions. It's a project-level action, not a server- level task requiring a server administrator.
Reference: Tableau Server Documentation - "Administrative Tasks" (https://help.tableau.com/current/server
/en-us/admin_tasks.htm) and "User Management" (https://help.tableau.com/current/server/en-us/users.htm).
質問 # 45
You install Tableau Server on a server that has four processor cores. How many instances of each Tableau Server process are installed?
- A. 0
- B. 1
- C. 2
- D. 3
正解：A
解説：
Tableau Server's installer configures process instances based on hardware and deployment type (single-node vs. multi-node). For a single-node installation with 4 cores, we need to consider the default process topology
. Let's break this down exhaustively:
* Key Processes:
* Gateway: Handles incoming requests (1 instance).
* Application Server (VizPortal): Manages UI and sessions (1 instance).
* VizQL Server: Renders visualizations (2 instances).
* Backgrounder: Runs extract refreshes, subscriptions (1 instance).
* Data Server: Manages data connections (1 instance).
* File Store: Stores extracts (1 instance).
* Repository: Metadata database (1 instance, active).
* Cluster Controller, Cache Server, etc.: Supporting processes (typically 1 each).
* Default Configuration:
* On a single-node install, Tableau sets 1 instance per process unless specified otherwise, except for VizQL, which defaults to 2.
* The installer doesn't scale instances linearly with cores (e.g., 4 cores # 4 instances). Post-install, TSM can adjust this (e.g., tsm topology set-process), but the question asks for the installed default.
* Minimum hardware (8 cores, 32 GB RAM) suggests higher defaults, but 4 cores still triggers a minimal setup.
* Option B (1): Correct with Caveat.
* Most processes (e.g., Backgrounder, Gateway, Data Server) default to 1 instance on install, regardless of 4 cores.
* VizQL defaults to 2, but the question's phrasing ("each process") implies a general rule.
Historically (and per docs), 1 is the baseline for most, with VizQL as the exception.
* Interpretation: Assuming "each" means the typical case, 1 fits most processes on a 4-core single- node setup.
* Option A (2): Incorrect. Only VizQL defaults to 2; others don't.
* Option C (8): Incorrect. Far exceeds defaults-8 cores might justify more, but not 4.
* Option D (4): Incorrect. Not tied to core count by default; manual config would be needed.
Why This Matters: Understanding defaults aids capacity planning-4 cores is below production minimum (8), so performance tuning may be needed post-install.
Reference: Tableau Server Documentation - "Server Process Settings" (https://help.tableau.com/current/server
/en-us/processes.htm).
質問 # 46
Which permission capability controls whether a user can create new data source connections directly from the web authoring interface?
- A. Save
- B. Web Edit
- C. Connect
- D. Create/Refresh Metadata
正解：B
解説：
The "Web Edit" capability governs whether a user can enter web authoring mode to build or modify visualizations and, depending on data source permissions, create new connections through the browser. "Connect" applies specifically to querying an existing published data source rather than initiating web authoring itself.
質問 # 47
What two Tableau Services Manager (TSM) processes continue to run when Tableau Server is stopped?
(Choose two.)
- A. Administration Controller
- B. License Manager
- C. Backgrounder
- D. VizQL Server
正解：A、B
解説：
Tableau Server consists of multiple processes managed by TSM. When you stop Tableau Server (e.g., via tsm stop), most application processes halt, but some TSM-specific processes remain active to manage the server's infrastructure. Let's examine each:
* TSM Processes: These include the Administration Controller, Administration Agent, and License Manager, which handle configuration, monitoring, and licensing.
* Application Processes: These include VizQL Server, Backgrounder, Data Server, etc., which deliver Tableau's core functionality and stop when the server is stopped.
When tsm stop is executed:
* The Administration Controller (port 8850) continues running to manage TSM operations (e.g., restarts, status checks).
* The License Manager remains active to validate licenses and ensure compliance, even when the server is offline.
* Application processes like VizQL Server and Backgrounder shut down, as they're tied to user-facing services.
* Option B (License Manager): Correct. It persists to handle licensing tasks, ensuring the server can restart without license issues.
* Option D (Administration Controller): Correct. It's the core TSM process, always running to accept commands and manage the server state.
* Option A (VizQL Server): Incorrect. VizQL stops, as it renders visualizations for users-an application process tied to active server operation.
* Option C (Backgrounder): Incorrect. Backgrounder stops, as it processes background tasks (e.g., extract refreshes), which halt when the server is down.
Why This Matters: Understanding which processes persist helps administrators troubleshoot and manage server lifecycle events effectively.
Reference: Tableau Server Documentation - "TSM Processes" (https://help.tableau.com/current/server/en-us
/tsm_overview.htm#processes).
質問 # 48
What is the minimum hardware recommendation for a single-node production installation of Tableau Server?
- A. 4-Core CPU (2.0 GHz or higher), 16 GB RAM, 50 GB free disk space
- B. 4-Core CPU (2.0 GHz or higher), 64 GB RAM, 50 GB free disk space
- C. 2-Core CPU (1.8 GHz or higher), 8 GB RAM, 15 GB free disk space
- D. 8-Core CPU (2.0 GHz or higher), 32 GB RAM, 50 GB free disk space
正解：D
解説：
Tableau Server's minimum hardware recommendations for a production single-node deployment ensure reliable performance for small to medium workloads. As of the latest documentation:
CPU: 8 cores (2.0 GHz or higher) to handle concurrent users, rendering, and background tasks.
RAM: 32 GB to support in-memory processing (e.g., VizQL, Data Engine) and caching. Disk Space: 50 GB free for installation, logs, extracts, and temporary files.
Option C (8-Core CPU, 32 GB RAM, 50 GB free disk space): Correct. This matches Tableau's official minimum for production:
8 cores ensure sufficient parallelism for processes like Backgrounder and VizQL. 32 GB RAM supports multiple users and extract refreshes. 50 GB disk space accommodates growth (initial install is ~1-2 GB, but logs and extracts expand).
質問 # 49
What event is most likely to cause problems for a Tableau Server?
- A. Configuring the server to use a static IP address
- B. Running additional software on the server
- C. Separating the Backgrounder and VizQL processes to different machines
- D. Using a non-default installation path
正解：B
解説：
Tableau Server's performance and stability depend on dedicated resources and proper configuration. Running additional software on the same server is the most likely to cause problems because:
* Resource contention: Tableau Server requires significant CPU, RAM, and disk I/O. Other software (e.
g., databases, web servers) can compete for these resources, leading to slowdowns, crashes, or failed tasks.
* Port conflicts: Tableau uses specific ports (e.g., 80, 443, 8850), and other applications might interfere.
* Security risks: Additional software increases the attack surface, potentially compromising Tableau Server.
Tableau recommends running the server on dedicated hardware without unrelated applications.
* Option A (Running additional software on the server): Correct. This is a common cause of performance issues and is explicitly discouraged in Tableau's best practices.
* Option B (Separating the Backgrounder and VizQL processes to different machines): Incorrect.
This is a supported multi-node configuration that can improve performance, not cause problems, if properly set up via TSM.
* Option C (Configuring the server to use a static IP address): Incorrect. A static IP is recommended for Tableau Server to ensure consistent network access, so it's unlikely to cause issues.
* Option D (Using a non-default installation path): Incorrect. While not default, a custom path is supported (via TSM or installer options) and unlikely to cause problems if permissions and disk space are adequate.
Reference: Tableau Server Documentation - "Best Practices for Installation" (https://help.tableau.com/current
/server/en-us/install_best_practices.htm).
質問 # 50
What Tableau Server authentication method should you configure to use OpenID Connect?
- A. SAML
- B. Active Directory
- C. Local Authentication
- D. Kerberos
正解：A
解説：
Tableau Server supports multiple authentication methods, including Local Authentication, Active Directory, Kerberos, SAML, and OpenID Connect. OpenID Connect (OIDC) is an identity layer built on OAuth 2.0, commonly used for single sign-on (SSO). In Tableau Server, OIDC is implemented as a variant of SAML (Security Assertion Markup Language) authentication because both are SSO protocols managed through the same configuration workflow.
To use OpenID Connect:
* Configure Tableau Server for SAML/SSO.
* Provide an OIDC-compatible identity provider (IdP) configuration (e.g., Google, Okta).
* Set up the IdP metadata and certificates in TSM.
* Option D (SAML): Correct. Tableau Server treats OIDC as a subset of its SAML authentication framework, so you configure it under the SAML settings in TSM.
* Option A (Local Authentication): Incorrect. Local Authentication uses Tableau's internal user database, not an external SSO protocol like OIDC.
* Option B (Kerberos): Incorrect. Kerberos is a network authentication protocol for Windows environments, unrelated to OIDC.
* Option C (Active Directory): Incorrect. AD uses LDAP or Kerberos, not OIDC, for authentication.
Reference: Tableau Server Documentation - "Configure SAML and OpenID Connect" (https://help.tableau.
com/current/server/en-us/saml_config.htm).
質問 # 51
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. Use the Stale Content administrative view
- B. Delete all extracts and allow them to be re-generated automatically if they are still in use
- C. View all workbooks, and sort by the Modified date
- D. Examine the extract files in ProgramData/Tableau/Tableau Server/data/tabsvc/dataengine/extract
正解：A
解説：
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. The Stale Content view, accessible under Server > 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.
質問 # 52
An administrator needs to restore Tableau Server to a new machine after a hardware failure.
Which two files are required? (Choose two.)
- A. The tabcmd.exe executable
- B. The server log archive
- C. The tsm settings export (JSON) file
- D. The .tsbak backup file
正解：C、D
解説：
A full disaster recovery requires the .tsbak file (containing repository and file store data, created via tsm maintenance backup) and the exported configuration/topology settings file (tsm settings export), which is imported on the new server before restoring the backup. tabcmd and log archives are not part of the restore process.
質問 # 53
What two events must occur for Tableau Server to recompute queries for a workbook cache after a scheduled refresh? (Choose two.)
- A. The All Users group has a permission rule allowing access to the workbook
- B. The workbook was published in the last month
- C. The workbook has been viewed recently
- D. The workbook has upcoming scheduled refresh tasks
正解：C、D
解説：
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).
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 in Schedules > 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.
質問 # 54
Your deployment of Tableau Server uses Active Directory authentication. What statement correctly describes the process of importing a group from Active Directory?
- A. If an imported group contains any users that have Tableau Server accounts, their site role will be changed to match the site role specified during the import
- B. New users created as a result of importing a group are assigned the site role specified during the import
- C. Importing a group from Active Directory requires a .csv file that lists user IDs
- D. You can change the name of a group during import, although this will not change the group's name in Active Directory
正解：B
解説：
Importing an AD group into Tableau Server syncs user management-let's analyze the process and options:
* AD Group Import Process:
* How: In the UI (Users > Groups > Add Group > Active Directory), enter the AD group name, set a site role, and sync.
* Behavior:
* Existing Users: If a user is already in Tableau Server, their site role remains unchanged unless manually adjusted-sync applies the minimum role only if it upgrades access.
* New Users: Added to Tableau with the site role specified during import.
* Config: Requires AD authentication enabled in TSM.
* Option D (New users created are assigned the site role specified during import): Correct.
* Details: When importing (e.g., "SalesTeam" group, site role: Explorer):
* New users get Explorer.
* Existing users keep their role unless it's below Explorer (e.g., Unlicensed # Explorer).
* Why: Ensures consistent onboarding-new users align with the group's intended access.
* Option A (Existing users' roles change to match import): Incorrect.
* Why: Existing roles persist unless lower than the minimum-e.g., Viewer stays Viewer if import sets Explorer, but Unlicensed upgrades. Not a full overwrite.
* Option B (Requires a .csv file): Incorrect.
* Why: AD import uses live sync via LDAP-no .csv needed (that's for local auth imports).
* Option C (Change group name during import): Incorrect.
* Why: The AD group name is fixed-you can't rename it in Tableau during sync (it mirrors AD).
Post-import renaming is possible but not part of the process.
Why This Matters: Accurate AD sync ensures seamless user management-missteps can disrupt access or licensing.
Reference: Tableau Server Documentation - "Synchronize Active Directory Groups" (https://help.tableau.com
/current/server/en-us/groups_sync.htm).
質問 # 55
Which two statements are advantages of published data sources in comparison to embedded data sources? (Choose two.)
- A. Storage space is conserved and resource usage during data refreshes is optimized
- B. Data is protected so that it is only available in one workbook
- C. Drivers are automatically installed on each client's machine
- D. Centralized data management is easier
正解：A、D
解説：
In Tableau, data sources can be embedded (stored within a workbook) or published (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.
質問 # 56
You use Tableau Desktop 10.5 and plan to publish a visualization to a Tableau Server that runs version
2020.1. You are assigned the Creator site role, and Publisher permissions for a project. What statement correctly describes what happens when you attempt to publish the visualization?
- A. You will see a warning message instructing you that the workbook will be upgraded to a new version
- B. You will see a warning message instructing you that embedded .tde extracts will be upgraded to .hyper
- C. You will successfully publish the visualization without any errors or warnings
- D. You will see an error message instructing you that you are unable to publish the workbook to a newer version of Tableau Server
正解：B
解説：
Tableau Desktop and Tableau Server have versioning considerations when publishing content, particularly regarding compatibility between older Desktop versions (e.g., 10.5) and newer Server versions (e.g., 2020.1).
Let's break this down step-by-step:
* Version Context: Tableau Desktop 10.5 was released in 2017 and used the .tde (Tableau Data Extract) format for extracts. Tableau Server 2020.1, released in 2020, introduced the .hyper extract format (starting with version 10.5, but fully standardized later). When publishing from an older Desktop version to a newer Server version, Tableau ensures backward compatibility but may upgrade certain components.
* Publishing Process: With a Creator site role and Publisher permissions, you have the rights to publish workbooks to the specified project. Tableau Server accepts workbooks from older Desktop versions (e.
g., 10.5) and upgrades them to the current Server version (2020.1) during publishing. This process is seamless for the workbook itself, but extracts require special handling.
* Extract Handling: If the workbook contains embedded .tde extracts (stored within the .twb or .twbx file), Tableau Server 2020.1 converts these to .hyper format upon publishing. This conversion is necessary because .hyper replaced .tde as the default extract engine starting in Tableau 10.5 and beyond, offering better performance and scalability. During this process, Tableau Desktop or Server displays a warning to inform the user of the upgrade, as it's a one-way conversion (you can't revert to .
tde on the Server).
Now, let's evaluate the options:
* Option A (You will successfully publish without any errors or warnings): Incorrect. While the publishing succeeds, a warning about the .tde to .hyper conversion appears if the workbook contains embedded extracts. Without extracts, no warning occurs, but the question's context implies extracts are likely involved (common in visualizations).
* Option B (Error message: unable to publish to a newer version): Incorrect. Tableau supports publishing from older Desktop versions to newer Server versions. There's no outright error blocking this; compatibility is maintained.
* Option C (Warning: embedded .tde extracts will be upgraded to .hyper): Correct. This is the precise warning displayed when a workbook with .tde extracts is published to a Server version that uses
.hyper. It ensures the user is aware of the format change, which might affect extract refresh schedules or performance expectations.
* Option D (Warning: workbook will be upgraded to a new version): Partially correct but less specific. The workbook is upgraded to 2020.1 compatibility, but the warning focuses on the extract format change (.tde to .hyper), not the workbook version generically. Option C is more accurate.
Why This Matters: The .tde to .hyper shift improves query performance and supports larger datasets, but users need to know about it for planning (e.g., extract refresh schedules might need adjustment). The warning ensures transparency.
Reference: Tableau Server Documentation - "Publish a Workbook" (https://help.tableau.com/current/server
/en-us/publish_workbook.htm) and "Hyper Extract FAQ" (https://help.tableau.com/current/server/en-us
/hyper_faq.htm).
質問 # 57
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. tsm customize
- D. tabcmd
正解：A、B、D
解説：
Tableau Server provides multiple methods to create groups (collections of users) and projects (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 to Users > Groups > Add Group, name it, and optionally sync with Active Directory.
Projects: Go to Content > 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.
質問 # 58
Which action requires a server restart or at minimum applying pending changes via TSM?
- A. Adding a new user to a site
- B. Publishing a new workbook
- C. Changing a TSM configuration key such as SMTP settings
- D. Creating a new project
正解：C
解説：
Configuration changes made with tsm configuration set are staged and require tsm pending- changes apply (which may restart affected services) to take effect. Content and user- management actions like creating projects, adding users, or publishing workbooks take effect immediately without any TSM changes.
質問 # 59
To which site role can you associate the Viewer user-based license level?
- A. Viewer
- B. Explorer
- C. Creator
- D. Explorer (can publish)
正解：A
解説：
Tableau Server uses a role-based licensing model with three primary license levels: Creator, Explorer, and Viewer. Each license level corresponds to specific site roles that define what users can do on the server.
Viewer License: This is the most restrictive license, allowing users to view and interact with published content (e.g., dashboards and visualizations) but not to create or publish new content.
Site Role: The Viewer license can only be associated with the Viewer site role. This role restricts users to viewing capabilities, aligning with the license's purpose.
Option C (Viewer): Correct. The Viewer site role matches the Viewer license level perfectly.
質問 # 60
......
Salesforce Analytics-Admn-201 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
100%合格保証付きの素晴らしいAnalytics-Admn-201試験問題PDF：https://jp.fast2test.com/Analytics-Admn-201-premium-file.html
Analytics-Admn-201問題集で2026年最新のSalesforce試験問題：https://drive.google.com/open?id=1N9XJGx2hXZI0yBZ3KqSBMM01BEyiKNve