Tableau Interview Questions Guide
Uploaded by
aishwaryan48Tableau Interview Questions Guide
Uploaded by
aishwaryan48Common questions
Powered by AIRow-level security in Tableau can be set up by defining user filters that restrict data access based on the user's credentials or group membership. At the desktop level, this often involves creating calculated fields with security logic. On the server, this configures via user filter settings or permissions to ensure granular control. This ensures that users only see information pertinent to them, which is vital in maintaining data confidentiality across varied user roles .
Dual-axis charts in Tableau effectively visualize multiple measures by sharing a single chart space while displaying two different scales. This technique allows for the comparison of different data values or trends on dual axes, like blending bar graphs with line charts. It presents a holistic view, highlighting relationships between data sets, increasing insights without cluttering the visual design. Properly labeling and differentiating between axes with colors or markers is crucial to avoid misinterpretations .
Custom views in Tableau Server can be configured to restrict what a client sees by default by saving a specific view of a dashboard with applied filters and subcategories relevant to that client. This saved view is made available as the default setting when the client accesses the dashboard. Administrators can control these settings through server-side configurations to ensure user-configurable dashboards meet specific security and visibility requirements .
In Agile workflows, priorities are typically set based on the business value, customer needs, and the cost of delay for deliverables. Complexity is assessed using estimation techniques such as story points or T-shirt sizing, factoring in past performance data, team capacity, and potential risks. Tools like the MoSCoW method (Must have, Should have, Could have, and Won't have) are often used to ensure resources are allocated efficiently, balancing new feature developments with technological debt management .
CHAR and VARCHAR differ mainly in how they allocate space. CHAR is used for fixed-length fields, which can save time on processing as the length is consistent but potentially wastes space if the field is not entirely filled. VARCHAR is used for variable-length fields, efficiently using storage space, which can improve performance if field lengths vary significantly. Understanding these differences is crucial in optimizing database design, ensuring that resources are used efficiently without sacrificing data integrity or application speed .
Asterisks often appear in Tableau visualizations after data blending due to issues related to non-uniquely identifying fields across data sources, causing Tableau to aggregate datasets improperly. This indicates ambiguity in the data for specific fields. Using relationships instead of blending helps prevent this. Relationships maintain the context needed to dynamically relate data without redundancy and offer a more reliable way to handle multi-source data configurations .
DELETE operations remove rows from a table based on a WHERE clause, and each operation logs the removal of individual rows, which allows for rolling back transactions in systems that support transactions. This makes it a safer option if there's a need to recover deleted data. TRUNCATE, on the other hand, deletes all rows in a table by deallocating the data pages, which makes it faster than DELETE. However, since TRUNCATE operations cannot be rolled back in most systems, they're not suitable when recovery is a concern .
To manage duplicate records effectively with Common Table Expressions (CTEs) in SQL, best practices include using CTEs to partition data based on key fields and assign row numbers to identify duplicates. For instance, utilizing a 'ROW_NUMBER()' window function within a CTE allows for marking each duplicate entry systematically, enabling developers to selectively delete duplicates while keeping the desired records intact. Implementing indexes on relevant fields can enhance performance during such operations .
In Tableau, relationships should be used instead of data blending when handling data from multiple sources as they allow for more flexible, dynamic and efficient data integration. Relationships enable Tableau to create logical links between data tables, leading to more optimized queries that leverage Tableau's in-memory data engine for efficient query generation. This approach allows for context-aware join calculations, and can handle more complex scenarios without duplicating data, as data blending might do .
Rolling calculations, like rolling 3-month averages, smooth out data to identify trends over time by continually calculating averages over specified periods. This approach minimizes the influence of short-term fluctuations and focuses on long-term trends. However, the main challenge is deciding the appropriate rolling period. Using these calculations provides a clearer, more stable view of performance, helping to make informed strategic decisions .