Domain 4: Publish & Manage Content on Server/Cloud (9%) Flashcards
When publishing a workbook, how do you add tags with spaces?
Tags help users find related workbooks when they browse the server. Normally, you can simply separate tags using a comma or space. But to add a tag that contains a space, put the tag in quotation marks.
What happens when you publish a workbook and select “Show Sheets as Tabs?”
The various sheets in a workbook can be navigated with tabs at the top of the visualization.
When a workbook shows sheets as tabs, workbook-level permission rules are applied to the sheets.
When the sheets aren’t shown as tabs, any changes made to workbook permissions don’t apply to the individual sheets (aka views).
When publishing a workbook, what does the “Preview device layouts” selection allow you to do?
To see how your designs appear on mobile devices, click Preview device layouts in the browser when publishing is complete.
Then choose a device type above the viz, and a specific dashboard from the menu at the right.
How do you set up row level security using user-based filtering?
User-based filtering is one option to help secure your data source or workbook using RLS. This procedure is best for a small and fairly static set of users or groups, and only a small number of workbooks that need user filters.
1) In Tableau Desktop, open the workbook and connect to the data you want to filter.
2) Navigate to the worksheet that you want to apply a filter to.
Select Server > Create User Filter. Then select the field you want to use for filtering the view, such as Region.
3) If prompted, sign in to your server or site.
4) In the User Filter dialog box, name the filter. We’ll use Regional Managers.
5) Select a user or group on the left, then indicate which values on the right they should be able to see. Repeat this process for each user or group, and click OK when you’re done mapping users to values.
6) After you create the user filter, it appears in the Sets area of the Data pane.
7) Drag the user filter to the Filters shelf. The filter becomes a context filter, and the view adjusts to show data that you are allowed to see.
How do you set up row-level security so that users cannot remove the user filter(s) you set up?
To secure user filters, the following capabilities must be set to Deny, either during publishing, or afterward on the server.
Workbooks:
* Web Edit
* Download/Save a copy
* Set Permissions
Data sources:
* Save
* Download
* Set Permissions
Explain the row-level security concept of a dynamic filter, using a security field in the data?
Using this method, you create a calculated field that automates the process of mapping users to data values. This method requires that the underlying data include the security information you want to use for filtering.
The most common way to do this is to use a reference (“look-up,” “entitlements,” or “security”) table that contains this information. For example, if you want to filter a view so that only supervisors can see it, the underlying data must be set up to include user names and specify each user’s role.
Because filtering is defined at the data level and automated by the calculated field, this method is more secure than mapping users to data values manually.
What does a Data Policy do with regards to row-level security?
Starting in Tableau 2021.4, when the Data Management Add-On is enabled in Tableau Server or Tableau Cloud, users with a Creator license can implement row-level security through data policies on virtual connections. Because virtual connections are centralized and reusable, you can manage row-level security for each connection in one place, safely and securely, across all content that uses that connection.
Unlike the above solutions for row-level security in Tableau, this method doesn’t carry the same risk of exposing information if an author neglects to properly secure permissions on the workbook or data source, because the policy is enforced on the server for every query.
Row-level security through virtual connection data policies was developed to address shortcomings of other row-level security solutions. We recommend this solution in most situations where it’s an option.
How do you set up row-level security using a dynamic filter (using a field in the data)?
1) In Tableau Desktop, open the workbook and connect to the data you want to filter. In this example, we use a table called Orders.
2) Double click the Orders table to open the join canvas. Add the reference table (People) with a left join. For this example, join on the field Region.
3) On the worksheet, select Analysis > Create Calculated Field, and create the following field, named “User is a manager”.
USERNAME() = [Manager]
This calculation returns TRUE if the user name of the person signed in to the server exists in the manager column of the People table.
4) Add the User is a manager field to the Filters shelf.
5) In the Filter dialog box, select True, and then click OK.
This sets the filter so that only people who are managers can see the data in the view. If you are not listed in the Manager field, your view while authoring might appear as a blank canvas.
6) See how the view looks to a particular person: in the lower-right, open the Filter as User menu, and select someone you know is a manager.
Can row-level security exist in the database themselves?
Yes. It is not necessarily easier or better to implement a built-in RLS model vs. building it with Tableau in mind; these techniques are generally leveraged when an organization has already invested in these technologies and they want to take advantage of that investment, or when they need to apply the same security policies to other database clients in addition to Tableau.
The main benefit of using built-in RLS is that administrators can implement and control their data security policy in one place: their databases.
How do you publish a data source that is connected to your workbook?
1) On Tableau Server, open a workbook in web authoring.
2) Click the tab for any worksheet.
3) From the Data pane, click the drop-down menu for the data source you want to share, and click Save as Published Data Source.
Name the four primary components of a Tableau data source.
1) The data connection information that describes what data you want to bring into Tableau for analysis (includes joins, field names, etc.).
2) An extract, if you decide to create one.
3) Information about how to access or refresh the data. Examples of this type of information include:
* The path to an original Excel file.
* Embedded credentials or OAuth access tokens for accessing the data directly.
* Alternatively, no credentials, so that users are prompted to enter them when they want to access the data (whether it’s to view a workbook that connects to it, or to connect a new workbook to it).
4) Customization and cleanup that helps you and others use the data source efficiently (calculations, sets, groups, bins, and parameters, etc.).
When is Tableau Bridge needed?
To keep data sources that connect to on-premises data fresh after publishing to Tableau Cloud, Tableau Bridge is required.
Tableau Cloud relies on Bridge to facilitate the connection between it and data accessible only from inside a private network.
What are the two primary ways to export a data source to a .csv?
- From the Data Source page:
On the Data Source page, select Data > Export Data to CSV to export all the data in your data source to .csv file. - From the view:
On the sheet tab, drag a field to the Columns or Rows shelf, click the View Data icon in the Data pane, and click the Export All button.
How do you export the data needed to render the view only - as a .csv?
Export the data that is used to generate the view as an Access database (Windows only) or .csv file (Mac only).
In Tableau Desktop, select Worksheet > Export > Data.
Note: you can similarly copy to your clipboard or Export to Excel.
What does a .tds contain?
A .tds contains only the information you need to connect to the data source, including the following:
* Data source type
* Connection information specified on the data source page; for example, database server address, port, location of local files, tables
* Groups, sets, calculated fields, bins
* Default field properties; for example, number formats, aggregation, and sort order.
