You have a server that contains 16 processor cores. What is the default number of VizQL instances configured by the installer?
Answer(s): D
The VizQL Server process in Tableau Server handles rendering visualizations and processing queries for users viewing dashboards or workbooks. During installation, Tableau Server automatically configures the number of VizQL instances based on the number of processor cores on the machine, following this rule:Default VizQL instances = 2 per node, unless manually adjusted post-installation. In multi-node setups, additional instances may be added based on core count, but the question specifies a single server with 16 cores.The installer does not scale VizQL instances linearly with core count by default (e.g., it doesn't set 1 instance per 4 cores). Instead:For a single-node installation, the default is 2 VizQL instances, regardless of core count (assuming the minimum hardware requirements are met: 8 cores, 32 GB RAM). Administrators can later adjust this using TSM (e.g., tsm topology set-process) based on performance needs, but the question asks for the default configured by the installer. Option A (4): Incorrect. Four instances might be configured manually for a 16-core server, but it's not the default.Option B (6): Incorrect. Six instances exceed the default for a single node. Option C (10): Incorrect. Ten instances are far beyond the default and would require manual configuration.Option D (2): Correct. The installer sets 2 VizQL instances by default on a single-node installation.
Tableau Server Documentation - "Server Process Settings" (https://help.tableau.com/current/server/en-us/processes.htm).
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?
Answer(s): B
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>. Option A (Edit tabsvc.yml): Incorrect. The tabsvc.yml file contains service configuration data, but manually editing it is not supported or recommended for resetting the administrator account. It could also corrupt the installation.Option C (Run the tsm register command): Incorrect. The tsm register command is used to register Tableau Server with a new product key or identity store, not to reset the administrator account. Option D (Reinstall Tableau Server): Incorrect. Reinstallation wipes the entire server, including content, and is overkill for this task. The tsm reset command achieves the goal without data loss.
Tableau Server Documentation - "TSM Reset Command" (https://help.tableau.com/current/server/en-us/cli_reset.htm).
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?
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).
What Tableau Server authentication method should you configure to use OpenID Connect?
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.
Tableau Server Documentation - "Configure SAML and OpenID Connect" (https://help.tableau.com/current/server/en-us/saml_config.htm).
Share your comments for Salesforce Certified Tableau Server Administrator exam with other users:
the questions are incredibly close to real exam. you people are amazing.
q15. answer is b. simple
great practice
thanks to this exam dumps, i felt confident and passed my exam with ease.
need 1z0-1105-22 exam
this is a beautiful tool. passed after a week of studying.
can you please upload the dumps for 1z0-1096-23 for oracle
its intresting, i would like to learn more abouth this
q252: dns poisoning is the correct answer, not locator redirection. beaconing is detected from a host. this indicates that the system has been infected with malware, which could be the source of local dns poisoning. location redirection works by either embedding the redirection in the original websites code or having a user click on a url that has an embedded redirect. since users at a different office are not getting redirected, it isnt an embedded redirection on the original website and since the user is manually typing in the url and not clicking a link, it isnt a modified link.
helpful dump questions
question 423 eigrp uses metric
hello nice dumps
good resource for learning
very useful
physical tempering techniques
its giving best technical knowledge
please upload
great question with explanation thanks!!
does this exam have lab sections?
please upload the braindump for .net
i need this exam 1z0-1107-2. please.
very useful!
for this question - "which three type of basic patient or member information is displayed on the patient info component? (choose three.)", list of conditions is not displayed (it is displayed in patient card, not patient info). so should be thumbnail of chatter photo
q52 should be d. vm storage controller bandwidth represents the amount of data (in terms of bandwidth) that a vms storage controller is using to read and write data to the storage fabric.
nice questions
question # 208: failure logs is not an example of operational metadata.
good questions
thank you for the test materials!
its very helpful
good questons
i need the dumb of the hcip security v4.0 exam