What should you do to ensure that server tasks associated with a particular schedule run one-at-a- time?
Answer(s): A
In Tableau Server, schedules manage tasks such as extract refreshes and subscriptions. The execution mode of a schedule determines how tasks within that schedule are processed by the Backgrounder process:Parallel: Tasks run simultaneously (up to the Backgrounder's capacity), which is the default setting.Serial: Tasks run one-at-a-time in sequence, ensuring that one task completes before the next begins. To ensure tasks associated with a particular schedule run one-at-a-time, you must configure the schedule's execution mode to Serial. This is done in the Tableau Server web interface:Go to Schedules.Select the schedule, click Actions > Edit Schedule.Under Execution, choose Serial instead of Parallel.Option A (Set Execution to Serial): Correct. This directly addresses the requirement by forcing tasks to execute sequentially.Option B (Set Default priority to 0): Incorrect. Priority (1100) determines the order of task execution across all schedules, not whether tasks run one-at-a-time within a single schedule. Also, 0 is not a valid priority value (minimum is 1).Option C (Set Frequency to Hourly): Incorrect. Frequency (e.g., hourly, daily) controls when the schedule runs, not how tasks within it are executed.Option D (Set Execution to Parallel): Incorrect. Parallel execution allows tasks to run simultaneously, which contradicts the requirement.
Tableau Server Documentation - "Create or Modify a Schedule" (https://help.tableau.com/current/server/en-us/schedule_manage_create.htm).
Which Tableau Server process performs the role of a database for metadata?
Answer(s): B
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. Option A (Data Engine): Incorrect. The Data Engine manages in-memory data processing and extract storage (e.g., .hyper files), not metadata. It's separate from the Repository. Option C (Backgrounder): Incorrect. The Backgrounder handles background tasks like extract refreshes and subscriptions, but it doesn't store metadata--it interacts with the Repository to retrieve task details.Option D (File Store): Incorrect. The File Store manages physical extract files and workbook assets, not metadata, which is stored in the Repository.
Tableau Server Documentation - "Tableau Server Processes" (https://help.tableau.com/current/server/en-us/processes.htm).
What is the minimum required free hard disk space recommended for a Tableau Server installation in production?
Tableau Server has specific hardware requirements for production environments to ensure stability and performance. The minimum recommended free disk space for a production installation is 50 GB.This accounts for:The installation itself (approximately 12 GB).Space for log files, temporary files, and extracts managed by the File Store and Data Engine.Room for backups and operational overhead.The full minimum hardware recommendations for a single-node production deployment are:8 CPU cores (2.0 GHz or faster).32 GB RAM.50 GB free disk space (on the system drive, typically C: on Windows). Option A (32 GB): Incorrect. While 32 GB is the minimum RAM requirement, it's insufficient for disk space in production.Option B (50 GB): Correct. This matches Tableau's official recommendation for production environments.Option C (15 GB): Incorrect. 15 GB is the minimum for a non-production or trial installation, not production.Option D (64 GB): Incorrect. While 64 GB exceeds the minimum, it's not the specified requirement-- 50 GB is sufficient.
Tableau Server Documentation - "Minimum Hardware Recommendations" (https://help.tableau.com/current/server/en-us/requirements.htm).
What event is most likely to cause problems for a Tableau Server?
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.
Tableau Server Documentation - "Best Practices for Installation" (https://help.tableau.com/current/server/en-us/install_best_practices.htm).
What should you do to configure the view URL and enable recording for a site that has recording workbook performance metrics enabled?
Tableau Server can record performance metrics for workbooks to troubleshoot slow-loading views. This feature must be enabled at the site level (via Settings > 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, immediately after 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 Performance option 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.
Tableau Server Documentation - "Record Performance of a View" (https://help.tableau.com/current/server/en-us/perf_record.htm).
Post your Comments and Discuss Salesforce Analytics-Admn-201 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Analytics-Admn-201 content, but please register or login to continue.