Explanation:

On Tableau Cloud, a common governance pattern that balances control with self-service is:

Sandbox (or “Development”) projects
Creators can freely publish and iterate on workbooks and data sources.
Viewers typically do not have access here.

Production projects
Only validated, approved dashboards are promoted here.
Viewers are granted access only to these projects.

This lets creators self-serve while the admin (or a governance group) controls what content becomes “official” for the wider audience.

Why the others are weaker
B. Separate sandbox site + CMT – Overkill for most orgs; more admin overhead. Project-level sandbox/production separation on the same site is the standard recommendation.

C. Personal Space – Personal Space is meant for private work; admins moving content from many personal spaces is messy and not scalable as a governance strategy.

D. Restrict data source permissions on uncertified dashboards – Helpful as a supporting practice but doesn’t provide a full promotion path or clear separation between ad hoc and production content.

So the recommended governance strategy is A: sandbox and production projects on the same site.

Explanation:

The Workbook Optimizer is a Tableau feature specifically designed to evaluate whether a workbook follows performance best practices. It provides actionable recommendations based on Tableau’s internal guidelines, covering areas like:

Data source usage
Calculations
Dashboard design
Filters and formatting

This tool is ideal for new users or consultants who want to quickly assess and improve workbook performance without manually inspecting every component.

❌ Why the other options are less suitable:
A. Inbuilt dashboards in Tableau Server: These are useful for monitoring server usage and user activity, but they don’t evaluate workbook design or performance best practices.
B. Performance Recording on Tableau Server: This records performance events but is more technical and diagnostic. It’s better suited for troubleshooting specific slow interactions, not general best practice evaluation.
C. Performance Recording in Tableau Desktop: Similar to option B, this helps analyze performance bottlenecks but doesn’t provide structured best practice feedback like the Workbook Optimizer does.

🔗 Reference:
Tableau Workbook Optimizer Overview

Explanation:

The core problem is that the Top 10 Filter (which is a Set/Conditional/Top N Filter) is applying before the view is partitioned by the Region dimension.
Current (Incorrect) Order:
Dimension Filters (including the invisible Region filter being applied by the sheet layout) execute early.
Top N Filter then finds the overall top 10 customers across the entire dataset.
The view is then partitioned by Region, but the data is already limited to the overall top 10 customers. The image shows that some regions have fewer than 10 customers displayed (e.g., EMEA, Latam, North America), because the customers filling the overall Top 10 spots happened to come predominantly from AsiaPac and other regions not fully visible.

Required Solution (Context Filter):
A Context Filter executes before the Top N filter in the Tableau Order of Operations.
By dragging the [Region] field to the Filter shelf and right-clicking to select Add to Context, the following process occurs:
1. Context Filter: The data is first filtered and partitioned by Region. Tableau essentially creates temporary data subsets for each region.
2. Top N Filter: The Top 10 Filter on [Customer Name] is then applied independently within each of those partitioned regions.
This ensures the analysis finds the Top 10 Customers in AsiaPac, the Top 10 Customers in EMEA, and so on, achieving the analyst's goal.

❌ Incorrect Answers
A. Extract filter
Incorrect. An Extract filter removes data from the extract file itself. It is applied once during extract creation and would permanently remove all customers from regions not included, still not solving the problem of applying the Top N filter per region.

B. Dimension filter
Incorrect. The [Region] field is already acting as a dimension filter by being placed on the Rows shelf. Using it as a standard filter would place it at the same spot in the Order of Operations as other dimension filters, which execute after the Top N filter is calculated on the full dataset.

C. Table Calculation filter
Incorrect. Table Calculation filters execute last in the Order of Operations. Using a Table Calculation filter on Region would apply after the Top 10 filter has already run across the entire dataset, thus having no impact on the Top N result.

📚 References
Tableau Help: Order of Operations
The documentation explicitly lists Context Filters as executing before Conditional/Top N Filters, which is the mechanism required to solve this problem.
Tableau Help: Creating a Context Filter
This is the official guidance for elevating a standard dimensional filter to a Context Filter to influence subsequent calculations like Top N sets.

Explanation:

Fixed-Sized Layouts within a Single Dashboard: This is the correct and most efficient method. Tableau allows a single dashboard to have different layouts optimized for various devices. When you design a dashboard, you can select 'Device Preview' and then add specific layouts for 'Desktop', 'Tablet', and 'Phone'. This means you only have one workbook to maintain on the server, but each device type gets a custom-tailored view. The fixed size ensures that the layout will appear as designed, without the elements shifting or resizing in a way that could break the user experience.

Why other options are incorrect:
B. Build one dashboard and fix the size of the dashboard: Fixing the size of a single dashboard to, for example, a desktop resolution, will lead to a poor experience on smaller devices like phones. The user would have to zoom and pan to see the content, making it difficult to interact with.

C. Build one dashboard and set the size to Automatic: Setting the size to Automatic tells Tableau to automatically resize the dashboard to fit the screen. While this might seem convenient, it can lead to unpredictable results. Charts may become too small to be readable, text can overlap, and the overall design can break on different screen sizes, especially on phones and tablets.

D. Build one dashboard for each type of device and fix the size of the layouts: This is inefficient. While it could technically work, it creates three separate workbooks (one for each device) that would need to be published and maintained. Any changes to the underlying data or calculations would have to be applied and tested on all three dashboards, which is a major time drain and a source of potential errors. The single-dashboard, multiple-layout approach is the best practice for streamlined development and maintenance.

Explanation:

Correct Solution: Explorer (can publish) (Option A)
The Explorer (can publish) site role is the perfect fit because it grants sales users exactly what they need while minimizing licensing costs:

Access published visualizations from anywhere (including outside the network) – Yes
Edit existing visualizations – Yes (they can open workbooks and save overwrites or new versions to the server)
Create new visualizations based on published data sources – Yes (they can connect to any published data source and publish new workbooks)
Lowest possible license cost for these capabilities – Yes (significantly cheaper than Creator licenses)

This role is designed precisely for power business users who need full interactivity and publishing rights without the overhead (and cost) of a full Creator license.

Why Site Administrator (Option B) Is Overkill and Expensive
Site Administrator gives complete control over the entire Tableau site (user management, projects, settings, etc.). It is unnecessary, risky from a governance standpoint, and still consumes a Creator-level license.

Why Viewer (Option C) Is Insufficient
Viewer is read-only. Users can view dashboards and interact with filters/actions, but they cannot edit or create new content and cannot publish anything — failing two of the four requirements.

Why Creator (Option D) Is Unnecessarily Expensive
Creator provides everything (including Desktop access, ability to build from live connections or new extracts, etc.), but it is the most expensive license tier. Since the sales users only need to work with published data sources and published visualizations, Explorer (can publish) delivers the same end-user experience at a lower cost.

In summary, when the goal is to enable editing, creating, and publishing from published content outside the network while minimizing licensing costs, the Analytics-Con-301 answer is always A – Explorer (can publish). This is Tableau’s official cost-optimization recommendation for this exact scenario.