What are the risks of adding too many VizQL processes to a node? (Select 3) The more VizQL processes, the less likely it is that the VizQL specific cache will be able to be utilized during a user's session Adding more than 2 VizQL processes is pointless, as they will be able to handle any amount of throughput required Without adding additional hardware resources as well, the node could become overloaded and reduce throughput, or crash There is a threshold of 4 VizQL processes beyond which throughput stops scaling linearly Application Servers must be added to the node in a 1:1 ratio to VizQL processes, otherwise not all sessions may be properly authenticated.
What type of requests does Gateway route? (Select all that apply) HTTP All inter-process communication in Tableau Server HTTPS Prep Flows and Extract Refreshes.
When should you recommend configuring multiple Application Servers? Almost always: Multiple instances allows for redundancy, and there is no noticeable downside Only sometimes: If there are throughput concerns for large REST API requests Only rarely: The potential resource concerns outweigh potential benefits most of the time Never: There are no benefits to having multiple instances.
What are the impacts of rebuilding the search index? (Pick Two) Very little disruption to users, so can be rebuilt at any time High impact to users, so should only be rebuilt when absolutely necessary Restarting the server rebuilds the index, and is the best method to do so Error messages will generally indicate when the index needs to be rebuilt.
When should we recommend isolating the use of Hyper for extract queries to a separate node? (Choose 2) When there is a need to reduce the query time of long running extract queries. When there are not enough resources available to increase the core count of the existing nodes used for extract queries. When slightly increasing the query times of short running (under 5 seconds) extract queries is acceptable. When the number of extracts being refreshed every day exceeds 1000.
Where is the best place to configure Cache Servers within a Tableau Server cluster? Collocated with Backgrounder: The minimal memory used by the Backgrounder allows the Cache Server to use more Collocated with VizQL Server: Putting both processes on the same machine makes VizQL more efficient in retrieving cached queries On any node: The results of caching are hashed and distributed evenly between every Cache Server, so they can be placed anywhere with equal efficiency On an isolated node: When there are no other configured processes, Cache Server can utilize all the memory on the machine, making it more efficient.
What are the current restrictions for using Ask Data on a data source? (Choose three) Users accessing the data source must have the appropriate site role of explorer or creator Tableau Server must be activated with a Data Management license key The fields with row level security won't be indexed The data source can't have more than 1000 fields The data source must be a live connection.
What are the benefits of data governance granted by Data Server? (Choose 3) Allows for easier auditing of data sources Tracking which users have utilized a given field Ensures a single source of truth, which prevents disagreement of analysis and concerns about data being stale Improves performance of data sources published to Tableau Server Allows for centralized driver deployment.
What are the triggers that cause File Store to replicate extracts to additional nodes?.
Assuming there is a need to eliminate resource contention with VizQL, which processes should Backgrounder be collocated with? (Select 2) VizQL Data Engine, which is configured automatically File Store Cache Server, if desired Data Server.
What type of data does the Repository store? All meta data except for .twb and .tds files, which are stored in File Store All meta data, except for files that are stored in the Client File Service All data published to Tableau Server All meta data, including plain text passwords and certificates for authentication.
What happens if the licensing service goes down? (Select 2) Tableau Server immediately goes into an unlicensed state, which stops anyone from logging in or publishing to the server If the regularly scheduled licensing check happens while the service is down, Tableau Server will go into an unlicensed state, which stops anyone from logging in or publishing to the server New users will not be able to be added, and AD syncs will fail until the service is started again Any licensed processes that restart while the service is down will not start correctly.
Which Processes are used in the following scenario?
An analyst published a viz connecting live to a Redshift database. Tabprotoserv Repository Application Server Gateway VizQL File Store.
Which processes are used in the following scenario?
A user subscribes to a dashboard published in the previous question (a viz connecting live to a Redshift database).
The subscription generates a view and emails it to the user. Backgrounder File Store Data Server VizQL Repository
Tabprotoserv.
Which processes are used in the following scenario?
An administrator is logging on to analyze which data sources have 0 workbooks connecting to them. The Server is configured to authenticate using Kerberos. Gateway Repository VizQL Search and Browse Application Server Data Server.
How often does the licensing service check the cluster to ensure it meets the requirements of the current license? Every hour Every 8 hours Every 24 hours Every 72 hours.
Scenario: A customer has configured Tableau Server in the below configuration. Which nodes will be utilized for sending queries to extracts? (Select two.) Initial Node Additional Node 1 Additional Node 2 Additional Node 3.
What steps need to be taken to change the identity store of Tableau Server? Tableau Server will need to be stopped, then it can be changed from the TSM GUI It can be changed at any time from the TSM GUI Tableau Server will need to be completely uninstalled, ideally by using the obliterate script, then it can be reinstalled and reconfigured to use the new identity store The setting can be changed in the workgroup.yml file. As long as Tableau Server is stopped, it shouldn't cause any issues.
|
