Salesforce Analytics-Admn-201 問題集 練習問題・模擬試験｜日本語版＆英語版対応

Explanation: Tableau Server uses a PostgreSQL database as its repository to store metadata, user information, and permissions. In a high-availability (HA) setup with multiple nodes, there are typically two repository instances: one active and one passive. The "preferred active repository" refers to designating which repository instance should take priority as the active one. This is managed through Tableau Services Manager (TSM). The correct method to set the preferred active repository is by using the tsm configuration set command. Specifically, you would use a command like: tsm configuration set -k pgsql.preferred_host -v <hostname> This command allows an administrator to specify the preferred host for the active repository, ensuring control over which node takes precedence in an HA environment. Option B (tabcmd set command) is incorrect because tabcmd is a command-line utility primarily used for administrative tasks like managing users, groups, and content (e.g., publishing workbooks), not for configuring server topology or repository settings. Option C (TSM browser client's Maintenance page) is incorrect because the Maintenance page in the TSM web interface is used for tasks like backups, restores, and cleanup, but it does not provide an option to set the preferred active repository. Option D (TSM browser client's Configuration Topology page) is partially relevant since the Topology page displays the current configuration of services across nodes, including the repository. However, it does not allow direct modification of the preferred active repository; this must be done via the tsm command line. Reference: Tableau Server Documentation - "Configure Tableau Server Repository" (https://help.tableau.com/current/server/en-us/repository.htm) and "TSM Command Line Reference" (https://help.tableau.com/current/server/en-us/cli_configuration_set.htm)

Explanation: The tsm maintenance backup command creates a backup file (with a .tsbak extension) that captures critical data needed to restore Tableau Server in case of failure or migration. This backup primarily includes: Repository data: This encompasses the PostgreSQL database, which stores metadata such as workbooks, data sources, user information, permissions, schedules, and subscriptions. Configuration data: This includes server settings like authentication methods, port configurations, and service layouts, but it does not include topology data as a separate entity (topology is part of the configuration). The command does not back up the following: Extract files (stored in the File Store), which must be backed up separately if needed. Log files, which are archived using tsm maintenance ziplogs. Option A (Notification settings) is incorrect because while notification settings are part of the configuration data stored in the repository, they are not the primary focus of the backup. The broader category is "repository data." Option B (SMTP server settings) is also incorrect for the same reason―SMTP settings are configuration data within the repository, but the backup is not limited to just these settings. Option D (Topology data) is incorrect because topology data (e.g., how services are distributed across nodes) is part of the configuration included in the backup, but it’s not stored as a standalone item. The .tsbak file is centered on the repository database. Reference: Tableau Server Documentation - "Back Up Tableau Server Data" (https://help.tableau.com/current/server/en-us/backup_restore.htm).

Explanation: 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).