Cert++
  1. Home
  3. Tableau Architect

Tableau Architect

Checklist progressProgress

0/441Learned

Tableau Architect Study Checklist
  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Marketing Cloud Account Engagement Specialist
  • Marketing Cloud Next Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Communications AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • Public Sector Solutions AP
  • Revenue Cloud Consultant
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Next Consultant
  • Tableau Architect
  • Slack Administrator
  • Slack Consultant
  • Slack Developer

Checklist progressProgress

0/441Learned

  • Site roles versus license types for user capabilities
  • Mapping organizational personas to Creator, Explorer and Viewer licenses
  • Distributing administrative responsibilities across server and site roles
  • User role distribution and its effect on server sizing and topology
  • Enterprise architecture requirements to gather before designing Tableau Server
  • Hosting model choice under compliance, data and access constraints
  • Extract-heavy versus live-connection workloads as design constraints
  • Capacity planning for user and workload growth
  • Scale up versus scale out as Tableau Server workloads grow
  • Role-based versus core-based licensing models
  • License roadmap, growth and reclamation planning
  • Server ATR activation choice and product key portability
  • ATR lease duration, renewal checks and tuning
  • Offline and air-gapped activation with ATR
  • Requirements that call for a highly available Tableau Server cluster
  • Protection scope and remaining failure points in a Tableau Server HA cluster
  • RTO and RPO as drivers of Tableau Server disaster recovery needs
  • Tableau Cloud versus Tableau Server responsibility for availability and recovery
  • Base Tableau Server capabilities versus Advanced Management requirements
  • Advanced Management features for scalability and workload isolation
  • Advanced Management security features for key management and DMZ access
  • Advanced Management tools for monitoring, content migration and auditing
  • Advanced Management licensing scope, activation and expiration
  • Data Management capabilities for flows, lineage and data governance
  • When Tableau Cloud data connections require Tableau Bridge
  • Bridge client host options on Windows and Linux containers
  • Bridge network path and outbound security requirements
  • Bridge client service account and sign-in for unattended refreshes
  • Bridge refresh schedules versus Bridge legacy schedules
  • Bridge pool design: sizing, routing, concurrency and timeouts
  • Diagnosing Bridge refresh and live query failures
  • Choosing site and per-user sign-in methods for Tableau Cloud
  • Meeting the Tableau Cloud multi-factor authentication requirement
  • Tableau Cloud site SAML setup with an external identity provider
  • Client, REST API and tabcmd access under an SSO configuration
  • Embedded view authentication on Tableau Cloud versus Tableau Server
  • Site sign-in versus data source credentials
  • SCIM prerequisites and setup on a Tableau Cloud site
  • IdP-managed user lifecycle after SCIM is enabled
  • SCIM versus REST API and tabcmd scripting for user provisioning
  • Automated provisioning on Tableau Server versus Tableau Cloud
  • SCIM provisioning failures from an invalid or revoked secret
  • Troubleshooting ATR activation and add-on license errors
  • Troubleshooting SAML sign-in and Independent Gateway configuration failures
  • Tableau Cloud site capacity limits behind failed or queued jobs
  • Tenant versus site administration in Tableau Cloud Manager
  • Site creation limits and site lifecycle in Tableau Cloud Manager
  • Separate sites versus projects within one site
  • Tableau Cloud Manager REST API versus Tableau REST API for automation
  • Operational responsibilities taken on when moving to self-hosted Tableau Server
  • Content migration method from a Tableau Cloud site to Tableau Server
  • Content, schedules and connectivity rebuilt after a Cloud-to-Server move
  • Identity store and user name mapping for users arriving from Tableau Cloud
  • Tableau Cloud fit assessment for compliance and hosting requirements
  • Choosing a Tableau Server to Tableau Cloud migration approach
  • Data connectivity strategy for on-premises and cloud data after migration
  • Workload gaps on Tableau Cloud: Prep flows, connectors and Kerberos data access
  • Replacing Active Directory, Kerberos and LDAP authentication for Tableau Cloud
  • User provisioning and username mapping for migrated users
  • Tableau Cloud site capacity limits in migration planning
  • Refactoring REST API and automation tooling for Tableau Cloud
  • Migration sequencing, validation and Tableau Server cutover
  • Windows-to-Linux migration method and the TSM backup-restore path
  • Restore prerequisites for a Windows backup on a new Linux server
  • Configuration, assets and topology to rebuild after a restore to a new server
  • Authentication and service account differences when moving to Linux
  • Data connectivity and rendering differences to validate on Linux before cutover
  • Backup-and-restore migration path from Tableau Server on Linux to Windows
  • Mixed Linux and Windows nodes versus a parallel Windows environment
  • Linux-to-Windows platform differences to validate on the target
  • Changing the identity store type on an installed Tableau Server
  • Site export and import versus fresh install with user republishing
  • User name format mapping across identity stores
  • User filters after an identity store or authentication change
  • Backup-restore versus site export-import versus Content Migration Tool for consolidation
  • Site export and import between servers with user and schedule mapping
  • Identity store and user name alignment across consolidated servers
  • Sites versus projects as the isolation boundary after consolidation
  • Choosing a server-to-server migration method
  • Backup, settings export and restore sequence onto a new installation
  • Product key and ATR activation handling when moving to a new server
  • Rehosting Tableau Server from on-premises to a public cloud VM
  • Cutover planning and validation for a server environment migration
  • Content Migration Tool console runner for scheduled and grouped migrations
  • Pre-migration and post-migration scripts in a Content Migration Tool plan
  • Tableau Migration SDK versus Content Migration Tool for scripted moves to Tableau Cloud
  • Content Migration Tool use cases versus other migration tools
  • Content Migration Tool licensing and installation prerequisites
  • Connection, permission and user mappings in a migration plan
  • Handling extracts when migrating workbooks and data sources
  • Content Migration Tool migration limitations
  • Installer default process counts on the initial node
  • Initial sizing from user population and license mix
  • VizQL Server and Cache Server counts for user-traffic-heavy deployments
  • Backgrounder process counts for extract-heavy and refresh-heavy workloads
  • Changing process counts with TSM topology commands
  • Single-node versus two-node baseline topologies by workload
  • Enterprise reference architecture node layout and process colocation
  • Process dependencies that are added or colocated automatically
  • Backgrounder node role options for dedicating workloads
  • Backgrounder node role rules and full job coverage
  • File Store node roles for isolating extract queries from extract refreshes
  • When to deploy an external repository instead of a local repository
  • When to use External File Store instead of local File Store
  • Local versus external identity store selection
  • Identity store prerequisites for each authentication method
  • Kerberos versus SSPI automatic logon for Active Directory SSO
  • Multi-factor authentication requirements on Tableau Server
  • Identity pools for external users alongside a directory-backed server
  • Choosing, setting and applying TSM configuration keys for a use case
  • Hardening keys for HSTS, JMX and clickjack protection
  • External SSL for client-to-server traffic on Tableau Server
  • TLS protocol versions and cipher suites for client connections
  • Protecting node-to-node traffic in a multi-node cluster
  • Transport encryption for data source and SMTP connections
  • Extract encryption at rest scope and trade-offs
  • Local KMS versus AWS KMS or Azure Key Vault for extract encryption keys
  • Security updates, Run As account and file access hardening
  • Single-node production hardware recommendations
  • Hardware for dedicated-role nodes in a multi-node cluster
  • vCPU and physical core sizing for virtual and public cloud hosts
  • Disk space planning for extracts, refresh temp files and backups
  • Compute and storage choices for extract-heavy workloads
  • Distributed cluster host and network prerequisites
  • Node placement across data centers and network latency
  • Network placement and reverse proxy for external client access
  • Outbound internet access and forward proxy requirements
  • High availability versus disaster recovery for Tableau Server
  • Backup data types for a full Tableau Server recovery
  • Disaster recovery with External File Store and external repository
  • Advanced Management licensing for External File Store
  • Enabling and reconfiguring External File Store with TSM
  • Topology and performance effects of an External File Store
  • Backup and restore with External File Store
  • Fully managed versus self-managed hosting for the external repository
  • Advanced Management licensing for the external repository
  • PostgreSQL version compatibility and preparation for the external repository
  • Enabling an external repository with TSM
  • Backup and recovery with an external repository
  • Moving the repository from external back to local
  • Independent Gateway versus a separately managed reverse proxy
  • Independent Gateway licensing requirements
  • Installing and enabling Independent Gateway with TSM
  • Independent Gateway direct versus relay connection modes
  • Scaling and high availability with multiple Independent Gateway instances
  • Client pre-authentication through an Independent Gateway authentication module
  • Independent Gateway during backup, restore and upgrade
  • Configuring a node that runs only unlicensed processes
  • Unlicensed process status on an additional node
  • Coordination Service ensemble sizing and quorum by cluster node count
  • Deploying a Coordination Service ensemble with TSM topology commands
  • Coordination Service-only nodes versus colocated ensemble instances
  • Licensing prerequisites for Backgrounder node roles
  • Applying a Backgrounder node role with TSM topology commands
  • Multi-gateway topology behind a load balancer for high availability
  • Gateway settings that identify load balancers and reverse proxies to Tableau Server
  • SSL termination at the load balancer versus end-to-end encryption to gateways
  • Authentication methods and configuration order behind a load balancer
  • Air-gapped install prerequisites and installer transfer approach
  • Offline product key activation with Server ATR versus legacy licensing
  • Feature limitations and offline map options in an air-gapped deployment
  • Failover testing strategy for a multi-node Tableau Server HA cluster
  • Initial node failure behavior and recovery during HA testing
  • Restore-based disaster recovery drills for Tableau Server
  • Blue/green versus in-place upgrade for Tableau Server
  • Building and licensing the Green environment
  • Moving Blue content and settings into Green
  • Validating Green without production side effects
  • Cutting users over to Green and retiring Blue
  • Installation and upgrade log locations on Windows versus Linux
  • Windows Setup program logs and the `/log` install switch
  • Install log versus TSM controller log for diagnosing setup failures
  • Resource Monitoring Tool architecture and component placement
  • RMT Server and Agent installation and registration by operating system
  • RMT, Agent and Tableau Server version compatibility during upgrades
  • When to use the SilentInstaller.py automated installer
  • SilentInstaller configuration, registration and secrets files
  • Scripted multi-node cluster installation with SilentInstaller modes
  • Server-wide SAML versus site-specific SAML
  • Server-wide SAML configuration prerequisites and TSM steps
  • SAML coverage of Tableau clients, tabcmd and the REST API
  • SAML debug logging and log locations
  • IdP binding, endpoint and connectivity errors during SAML setup
  • IdP username and assertion mismatches at SAML sign-in
  • SAML sign-in failures behind an SSL-offloading proxy or load balancer
  • Kerberos SSO prerequisites in Active Directory environments
  • Enabling Kerberos SSO and deploying the keytab across cluster nodes
  • Diagnosing Kerberos SSO sign-in failures from client computers
  • Server-side Kerberos troubleshooting with logs and keytab checks
  • Kerberos delegation versus Run As service account for data access
  • OpenID Connect identity store prerequisites on Tableau Server
  • Configuring OIDC through the IdP and TSM web UI, CLI or settings file
  • OIDC user identity matching and identity provider changes
  • Command-line and API sign-in when OIDC is enabled
  • OIDC sign-in through a forward proxy on Tableau Server
  • OIDC troubleshooting with enhanced logging and IdP compatibility checks
  • Mutual SSL prerequisites and configuration through TSM
  • Client certificate user name mapping strategies
  • Troubleshooting mutual SSL sign-in failures and password fallback
  • Trusted ticket flow and trusted host configuration
  • Trusted authentication logs and test procedure
  • Trusted ticket request and redemption errors
  • Reverse proxy and load balancer effects on trusted tickets
  • Direct trust versus OAuth 2.0 trust connected apps
  • Direct trust connected app setup and access controls
  • Connected app JWT claims, scopes and signing requirements
  • Diagnosing connected app embedding failures from error codes
  • Connected apps alongside other authentication methods and clients
  • Simple bind versus GSSAPI bind to the LDAP directory
  • Encrypting the channel between Tableau Server and the LDAP directory
  • Configuring a generic LDAP directory with TSM CLI and the identityStore entity
  • Directory user sign-in failures: username mapping, domains and user import
  • Azure AD as a SAML identity provider for Tableau Server
  • Azure AD claim mappings and Tableau Server username matching
  • SAML audience mismatch with an Azure AD application ID
  • Azure AD session lifetime versus Tableau Server maximum authentication age
  • Azure AD Application Proxy in front of a SAML-enabled Tableau Server
  • Compatible combinations of Tableau Server authentication methods
  • Automatic logon (SSPI) platform and topology constraints
  • Client and programmatic authentication compatibility with SSO methods
  • Authentication options on Tableau Cloud versus Tableau Server
  • Multi-factor authentication on Tableau Cloud versus Tableau Server
  • Tableau Server encryption-in-transit channels and what each protects
  • SSL certificate requirements and client trust of the server certificate
  • Enabling external SSL for client traffic to Tableau Server
  • TLS configuration for Tableau Server Independent Gateway
  • SSL for internal Postgres repository communication
  • Encrypted connections to an external repository
  • Encryption of server secrets and stored data source credentials
  • Regenerating internal tokens and encryption keys after installation
  • Site-level extract encryption modes and their effects
  • Scope and limitations of extract encryption at rest
  • Key management system options for encrypted extracts
  • Re-encrypting extracts and rotating keys with tabcmd and the REST API
  • Backgrounder capacity planning for extract encryption workloads
  • Backup and restore considerations for encrypted extracts
  • Service principal names and keytab for Tableau Server Kerberos SSO
  • SPN alignment with load balancer URL and DNS names
  • Delegation rights to database SPNs for Kerberos data source delegation
  • Supported Linux platforms and cluster operating system requirements
  • Linux package installation methods and install location
  • Linux installation sequence through the TSM Web UI or TSM CLI
  • Adding nodes to a Linux cluster with a node bootstrap file
  • Hardware and resource shortfalls that block or stall a Linux install
  • Locale encoding and temporary database initialization failures
  • Windows line endings in Linux installation and configuration files
  • Clean reinstall after a failed Linux installation attempt
  • Additional node installation failures in a Linux cluster
  • Local firewall and port configuration for Linux cluster nodes
  • Hostname changes and Tableau Server startup failures on Linux
  • OS patching versus major OS or kernel upgrades on Tableau Server nodes
  • Disk space and log cleanup on Linux nodes
  • Outbound internet dependencies of Tableau Server
  • Database driver and data source connectivity issues on Linux nodes
  • Active Directory and LDAP identity store connectivity from Linux
  • SAML configuration string mismatches across the IdP, web tier and Tableau Server
  • External PostgreSQL repository connection and compatibility issues
  • Independent Gateway service restart and connectivity checks
  • Third-party security and monitoring software interfering with Tableau Server
  • Forward proxy configuration and limits for Tableau Server on Linux
  • Verifying reverse proxy connectivity to Tableau Server nodes
  • Apache httpd load balancing across Tableau Server gateways
  • Tableau Server on Linux log locations
  • Collecting logs on Linux: tsm maintenance ziplogs versus manual collection
  • systemd logs versus Tableau logs when Tableau Server on Linux will not start
  • Tableau Server on Linux system user, groups and TSM administrator access
  • TSM file access for keytabs, certificates and backups on Linux
  • Tableau Server on Windows installation sequence through the Setup wizard and TSM
  • Tableau Server Setup command-line switches and properties
  • Adding Windows nodes to a cluster with a bootstrap file
  • Minimum hardware and disk space prerequisites enforced by Setup
  • CPU instruction set requirements and VM processor compatibility mode
  • Installer account permissions and initialization failed errors
  • TSM initialization page not rendering after Setup
  • Recovering from failed Windows installs with the obliterate script
  • Additional node installation failures in a Windows cluster
  • First-line troubleshooting steps for Tableau Server on Windows
  • Network requirements between nodes in a distributed deployment
  • Port and local firewall configuration on Windows server nodes
  • Hostname resolution and hostname stability for Tableau Server nodes
  • Static IP addressing and IPv4 versus IPv6 behavior on server nodes
  • Multiple network interface cards and inconsistent process status
  • Antivirus scanning interference with Tableau Server on Windows
  • Operating system patching and major OS upgrades on Tableau Server computers
  • Core recognition, disk latency and licensing symptoms on cloud VMs
  • Licensing service reachability and activation failures
  • Active Directory identity store connectivity failures on Windows Tableau Server
  • Network reachability between Tableau Server and an external identity provider
  • SMTP server integration for subscriptions and alerts
  • External repository and External File Store dependency failures
  • Forward proxy versus reverse proxy roles for Tableau Server traffic
  • Windows LAN proxy settings under the Run As service account
  • Proxy environment variables and WinHTTP settings for Server ATR
  • Product key activation and refresh through a Windows forward proxy
  • Forward proxy authentication limits and required outbound destinations
  • Tableau Server on Windows log locations inside and outside the data directory
  • Gathering Tableau Server logs safely across a Windows cluster
  • TSM Administration Controller and agent logs for configuration and topology failures
  • Service logs for sign-in, SSL and request failures on Tableau Server
  • Windows operating system logs versus Tableau Server logs
  • Raising Tableau Server logging levels for a targeted investigation
  • Windows accounts that run Tableau Server services
  • Local Administrators and Users group membership for Tableau Server accounts
  • Run As folder permissions for default versus non-default install drives
  • Restoring Run As folder permissions after Group Policy changes
  • NetworkService permissions for custom tsm file paths and backup locations
  • Network Service versus domain user as the Run As service account
  • Data access exposure through the Run As service account
  • Server allowlist for file-based data sources with a domain Run As account
  • Local security policy and registry rights required by the Run As account
  • Changing the Run As service account in a multi-node deployment
  • SQL Server impersonation with the Run As service account
  • Run As account requirements for Kerberos delegation and Run As authentication

3.1.1 Interpret the repository schema and the event types

0/3

  • Historical events and event types in the repository schema
  • Built-in tableau versus readonly repository users
  • Repository data retention and its effect on custom admin views

3.1.2 Build admin dashboards for common scenarios

0/3

  • Pre-built administrative views versus custom admin dashboards
  • Slow-view dashboards from the sample performance workbook and repository data
  • Preferred active repository for custom administrative views

3.1.3 Utilize Admin Insights on Tableau Cloud

0/6

  • Admin Insights versus Site Status admin views on Tableau Cloud
  • Admin Insights project placement and Starter workbook customizations
  • Choosing the Admin Insights data source for a site monitoring question
  • TS Events event types and joins for site auditing
  • Admin Insights data history window and update frequency
  • Admin Insights in place of repository-based admin views after moving to Tableau Cloud

3.2.1 Recommend a load testing strategy

0/2

  • Load testing cadence and triggering events for Tableau Server
  • Single-user workbook optimization before a load-testing project

3.2.2 Configure and use a load testing tool such as TabJolt

0/2

  • TabJolt versus Replayer and Scout for Tableau Server performance testing
  • Configuring and running a TabJolt load test

3.2.3 Configure a test environment

0/3

  • Test environment fidelity to production for load testing
  • Seeding a test environment from a production backup
  • Replicating server configuration after a test environment restore

3.2.4 Create appropriate test plans

0/3

Selecting representative workbooks for a load test plan

Learn this concept
Unseen

Load test plan usage model and run conditions

Learn this concept
Unseen

Upgrade test plan scope for functional and acceptance validation

Learn this concept
Unseen

3.2.5 Interpret load test results and determine the appropriate action

0/2

  • Interpreting load test results against CPU and error-rate targets
  • Process count tuning versus scale up or scale out after a load test

3.3.1 Troubleshoot complex performance issues related to workbooks, data sources, and other types of content

0/4

  • Workbook design versus server capacity as the root cause of slow views
  • Isolating a slowdown to specific users, a workbook subset or a shared data source
  • Live connection versus extract for slow-querying data sources
  • Extract refresh contention from embedded extracts and peak-hour schedules

3.3.2 Perform resource analysis, latency analysis, and workload analysis to determine root cause of performance issues

0/3

  • Hardware resource analysis on Tableau Server nodes
  • View load time and query latency analysis
  • Workload analysis of background tasks versus interactive use

3.3.3 Create an action to resolve issues identified in performance recordings

0/6

  • Enabling and capturing a performance recording on Tableau Server
  • Navigating performance recording dashboards to locate the costliest events
  • Slow data source connection events and their root-cause layer
  • Query compilation versus query execution bottlenecks
  • Database-level tuning from recorded query text
  • Server rendering versus layout computation as the recorded bottleneck

3.3.4 Optimize caching for Tableau Server

0/4

  • Tuning the server data cache for freshness versus performance
  • Cache warm-up for extract workbooks after a scheduled refresh
  • Manually sizing the Tableau Server query cache
  • Cache Server process count and placement across nodes

3.4.1 Map the features and capabilities of the Tableau Server Resource Monitoring Tool to observability requirements

0/7

  • Resource Monitoring Tool licensing and platform prerequisites
  • RMT agent and server roles for monitoring multiple Tableau Server environments
  • Matching observability requirements to RMT pre-built charts and pages
  • RMT incidents and notifications for proactive alerting
  • Exporting Resource Monitoring Tool data for custom analysis in Tableau
  • RMT coverage of externally hosted Tableau Server services
  • Resource Monitoring Tool versus admin views, repository views and community tools

3.4.2 Recommend a strategy for collecting and analyzing Tableau Server logs

0/4

  • Cluster-wide log collection with a log archive versus manual folder copies
  • Tableau Server logging levels for targeted troubleshooting
  • Log analysis with Resource Monitoring Tool versus enterprise log platforms
  • Server logs, repository data, Activity Log or Admin Insights for a monitoring question

3.4.3 Recommend a strategy for collecting and analyzing Tableau Server process metrics

0/3

  • Process status checks with TSM CLI, TSM web UI and the Server Status page
  • Process-level monitoring with Resource Monitoring Tool agents
  • RMT versus TabMon or enterprise platforms for process and hardware metrics

3.4.4 Recommend a strategy for collecting and analyzing operating system and hardware-related metrics

0/4

  • Windows versus Linux tools for collecting Tableau Server hardware metrics
  • Hardware utilization alert thresholds and capacity headroom
  • RMT agent hardware data collection and missing performance data
  • Infrastructure monitoring responsibilities on Tableau Cloud versus Tableau Server

3.4.5 Interpret observability data

0/5

  • Hardware utilization metrics versus recommended headroom thresholds
  • Slow view load times in monitoring data and their likely causes
  • Adoption growth versus inefficient content as the cause of degradation
  • Background task failures and job queue delays
  • Usage and stale content data as triggers for maintenance actions

3.4.6 Revise architecture based on observability data

0/3

  • Content and schedule fixes versus infrastructure changes
  • Scale up versus scale out after sustained resource threshold breaches
  • Isolating background workload with dedicated backgrounder nodes and node roles

3.4.7 Troubleshoot connectivity in a single or multi-node environment, especially database connectivity

0/5

  • Database drivers in single-node and multi-node deployments
  • Database credential and identity paths for published data connections
  • Firewall and port requirements for node-to-node communication
  • Remote connectivity to the Tableau Server repository
  • Logs for isolating data source connection failures

3.4.8 Configure and implement Activity Log for Tableau Cloud or Tableau Server

0/4

  • Activity Log licensing and version prerequisites
  • Setting up Activity Log delivery and access on Tableau Cloud
  • Collecting Activity Log event files on Tableau Server
  • Auditing permission changes and data exports with Activity Log events

3.5.1 Manage and change Tableau Server resources programmatically, including Tableau Services Manager (TSM), REST APIs, and tabcmd

0/4

  • Choosing among TSM, the TSM API, the REST API and tabcmd for an admin task
  • tabcmd for scripted site administration tasks
  • Authenticating unattended REST API and tabcmd scripts
  • Programmatic administration differences between Tableau Server and Tableau Cloud

3.5.2 Recommend a script deployment method, including Windows Scheduler and cron

0/1

  • Windows Task Scheduler versus cron for Tableau Server maintenance scripts

3.5.3 Recommend automated deployment methods for Tableau Server, Tableau Desktop, and Tableau Prep

0/6

  • Scripted Tableau Server installation versus interactive setup
  • Silent command-line install versus extracted MSI for Desktop and Prep
  • Scripted Tableau Desktop and Prep deployment on macOS
  • Activation strategy for mass-deployed Desktop and Prep Builder
  • Tableau Prep Builder install placement relative to Desktop and Server
  • Client version compatibility and update strategy for Desktop and Prep

3.5.4 Design an automated complex disaster recovery process

0/5

  • Standby server versus rebuild-from-backup recovery strategies
  • Machine snapshots versus TSM backups for server recovery
  • Restore prerequisites on a replacement Tableau Server
  • Automated recovery from an initial node failure
  • Failover tests that validate redundancy in a recovery design

3.5.5 Plan and implement multi-node server upgrades

0/8

  • In-place versus blue/green upgrade for a multi-node cluster
  • Upgrade planning decisions, rollout order and rollback
  • Testing a Tableau Server upgrade before the production rollout
  • Pre-upgrade backup and scheduled task preparation
  • Multi-node in-place upgrade sequence across initial and additional nodes
  • Upgrading a cluster that uses an external repository or file store
  • Operating system upgrades on Tableau Server cluster nodes
  • Troubleshooting credential errors during a multi-node upgrade

3.5.6 Automate maintenance tasks, such as cleanup and backup

0/6

  • Backup responsibility on Tableau Cloud versus Tableau Server
  • Built-in TSM backup schedules versus OS-scheduled backup scripts
  • Backup file location, network share permissions and off-cluster retention
  • tsm maintenance cleanup scope, options and server-state behavior
  • Recommended cadence for Tableau Server maintenance tasks
  • Automating stale content archiving and purge

3.5.7 Configure and use the Metadata API

0/5

  • Enabling the Metadata API on Tableau Server versus Tableau Cloud
  • Metadata API authentication and the GraphQL endpoint
  • Metadata API versus REST API metadata methods
  • Lineage and impact analysis with the Metadata API
  • Metadata API, Tableau Catalog and Data Management licensing

3.6.1 Schedule content automation tasks by using webhooks, tabcmd, REST, or Hyper APIs

0/6

  • Choosing webhooks, tabcmd, REST API or Hyper API for content automation
  • Script-triggered extract refreshes with tabcmd versus the REST API
  • Managing refresh schedules and tasks through the REST API on Server versus Cloud
  • Refresh schedule priority and execution mode on Tableau Server
  • Event-driven automation with Tableau webhooks
  • Hyper API for custom ETL and incremental extract updates

3.6.2 Implement and configure dashboard extensions and web data connectors

0/7

  • Sandboxed and Tableau Trusted versus network-enabled extensions
  • Server-level and site-level dashboard extension settings
  • Safe list options for network-enabled extensions
  • Troubleshooting dashboard extensions that fail in published workbooks
  • Web data connector 2.0 versus 3.0 deployment considerations
  • Web data connector safe list management with TSM
  • Dashboard extensions versus web data connectors and neighbouring extensibility tools

3.6.3 Configure trusted tickets and connected apps for a custom embedded solution

0/4

  • Trusted tickets versus connected apps for an embedded web portal
  • Configuring trusted tickets for an embedding web server
  • Direct trust connected app configuration for embedding
  • JWT claims and scopes for embedded connected app sessions

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Tableau Architect studiers. 670 members and growing.

Go to Discord
  1. Tableau Architect Checklist
  3. Monitor and Maintain a Tableau Deployment

Selecting representative workbooks for a load test plan

Explainer

Learn More

Practice Question

Studying for this exam?

This is one of 441 concepts on the Salesforce Tableau Architect exam.

Looking for practice exams? Click below to try one!

Keep going

Next conceptLoad test plan usage model and run conditions

Checklist progress

0/441 (0%)

0 of 441 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Tableau Architect studiers. 670 members and growing.

Go to Discord
Close
  1. Tableau Architect Checklist
  3. Monitor and Maintain a Tableau Deployment
Selecting representative workbooks for a load test plan

Explainer

Learn More

Practice Question

Studying for this exam?

This is one of 441 concepts on the Salesforce Tableau Architect exam.

Looking for practice exams? Click below to try one!

Keep going

Next conceptLoad test plan usage model and run conditions

Explainer

A load test shows how much work Tableau Server can handle with your own environment, data, workload, and usage. A good test plan starts by choosing representative workbooks, taken from the workbooks your users view most. Slow workbooks get optimized before the test starts, because poorly authored workbooks are often the real cause of performance problems.
Core information
  • Load testing measures Tableau Server capacity for your unique environment, data, workload, and usage profile. It applies to Tableau Server only.
More details and nuances
  • A slow workbook and a busy server look different. If a view takes a long time to load no matter when it is viewed, the workbook needs to be optimized. If slow load times line up with a large number of sessions, user traffic is slowing down the server.

Explainer

A load test shows how much work Tableau Server can handle with your own environment, data, workload, and usage. A good test plan starts by choosing representative workbooks, taken from the workbooks your users view most. Slow workbooks get optimized before the test starts, because poorly authored workbooks are often the real cause of performance problems.
Core information
  • Load testing measures Tableau Server capacity for your unique environment, data, workload, and usage profile. It applies to Tableau Server only.
More details and nuances
  • A slow workbook and a busy server look different. If a view takes a long time to load no matter when it is viewed, the workbook needs to be optimized. If slow load times line up with a large number of sessions, user traffic is slowing down the server.