Q # 1: Is it possible to secure one dimension on dashboard from a user?

/
Example, On a dashboard, the User X can drill down from bank level to branches
level, whereas User Y should not be able to drill down from bank level to branches
level on same dashboard. How is this possible?
This can be achieved by Row Level Security. By sharing workbooks with others users
using Tableau Server, by default users can access all the data shown in the views.
Alternatively, we can create filters to limit the data that any given person can see. For
example, in following report that gets shared between two different business users to
see data (In Date Granularity e-g Quarters) across same report and reporting objects but
different level of hierarchy, we want to limit one user to only specific quarter e-g Q1 and
other Q3.Other User will not be capable of viewing other secured data anymore. Rather
than create a separate view for each business user, we defined row-level security that
allows each user to see only the data for a particular Quarters (In Date Hierarchy).
Row Level Security Detail
Following is sample report \ view for row level security (includes all year across all
quarter)

User 1 View after Implementation

Report has been limited to Q3 for User 1.

User 2 View after Implementation

Report has been limited to Q1 for User 2.

Q # 2: How Tableau manage version control? How is this possible in Tableau

Server? How is this possible in Tableau Desktop Professional? {If someone delete
an object, how can we retrieve previous version?}
Tableau files (data sources, work books etc.) are simply XML files these can be
versioned.

Tableau Server Version Control

Tableau Server holds backup of Tableau server which includes copy of all deployed data
sources, Databases, Project & Workbooks. These can be saved on daily bases with date
time stamp for future use. Process of Tableau Server making backup is as follows.

In windows Command Prompt run batch of script (for 64-bit architecture)

cd..
cd..
cd C:\Program Files (x86)\Tableau\Tableau Server\8.0\bin
tabadmin stop
tabadmin backup [backupfilename] -d -t C:\Program Files (x86)\Tableau\Tableau
Server\8.0\bin
tabadmin start
exit
This script will make copy of all deployed data source and Projects in to one backup file
(.tsbak) based on current time stamp. We can schedule and make batch file and
windows task scheduler to run daily and make versions of Tableau Server.
In order to restore version backup, need to run following batch of script in command
prompt
cd..
cd..
cd C:\Program Files (x86)\Tableau\Tableau Server\8.0\bin
tabadmin stop
tabadmin restore [backupfilename]
tabadmin start
exit
Tableau Desktop Version Control

Tableau provides a solution of version control system through XML code. We can use
our XML code as all Tableau Sources, Workbooks mainly stores data in XML format.

Q # 3: What is difference between Load Balancer and Gateway in Tableau. Why

Load balancer is not enough and we need gateway?
Tableau Gateway/ Load Balancer
The Gateway is the primary Tableau Server that routes requests to other components.
Requests that come in from the client first hit the gateway server and are routed to the
appropriate process.
If multiple processes are configured for any component, the Gateway will act as a load
balancer and distribute the requests to the processes. In a single-server configuration,
all processes sit on the Gateway, or primary server. When running in a distributed
environment, one physical machine is designated the primary server and the others are
designated as worker servers which can run any number of other processes. Tableau
Server always uses only one machine as the primary server.

Automatic Gateway Failover:

Rather than setting up a gateway failover within Tableau, Tableau 8.1 can now be set up
to use an external load balancer to handle gateway duties.
You can now run multiple gateways in your Tableau Server cluster and front them with a
load balancer. If one gateway becomes inactive, the load balancer automatically
distributes traffic across the active gateways. This makes your deployment of Tableau
Server resilient against system failures and eliminates single-machine risk.

Q # 4: Load Balance (Gateway) also balance load between Primary Node and
Worker Node? For now it seems, Worker node is just backup of Primary node. but
does Load balancer send traffic to worker node as well to balance load between
primary and worker nodes?
At a minimum for high availability, the Tableau Server cluster should consist of three
nodes. One node will serve as the Primary Tableau Server running as the Gateway,
while the other two nodes are worker servers, hosting the core Tableau components.
While Tableau Server can be configured to run on more than three nodes for additional
scalability, the high availability function will only be able to replicate data from one active
Data Engine and Repository to one standby Data Engine and Repository.

The two additional servers will run the core Tableau processes. These servers can be
set up for high availability by configuring both servers to host the Data Engine and
Repository processes. The Tableau Server cluster will automatically designate one of
these servers as the host for the active Data Engine and Repository, while the other
server is designated as the host for the standby Data Engine and Repository. The data
will be replicated across the two servers in near real-time.
The architecture indicates that, at a particular time, only one primary server is available
for services of request in Tableau server. Load balancer will only shift load to worker
server when primary server is unavailable.