Analytics-Arch-201 Salesforce Certified Tableau Architect Exam Topics and Questions
These Salesforce Certified Tableau Architect (Analytics-Arch-201) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Analytics-Arch-201 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Certified Tableau Architect certification exam.
Let's Practice Free Salesforce Analytics-Arch-201 Questions Aligned with Official Exam Topics
This topic sets the foundation for everything that follows. You need to translate business constraints into a working server topology, choose between Cloud and Server, size the deployment, and plan for migrations. The exam tests whether you can map requirements to architecture decisions under real constraints: budget limits, growth curves, disaster recovery mandates, and identity stores that already exist. β Requirements gathering and licensing Start by gathering requirements for a complex deployment. You evaluate user counts, role distributions, and future...
This topic sets the foundation for everything that follows. You need to translate business constraints into a working server topology, choose between Cloud and Server, size the deployment, and plan for migrations. The exam tests whether you can map requirements to architecture decisions under real constraints: budget limits, growth curves, disaster recovery mandates, and identity stores that already exist.
β Requirements gathering and licensing
Start by gathering requirements for a complex deployment. You evaluate user counts, role distributions, and future growth to determine whether the organisation needs Server or Cloud, how many sites, and which features matter. Licensing strategy includes Authorization-to-Run and understanding when to use add-ons like Advanced Management or Data Management. The exam expects you to match constraints (regulatory, geographic, user volume) to the right licensing model. You also assess high availability and disaster recovery needs early, because those decisions shape topology and cost. Cloud versus Server is not a preference question; it turns on data residency, control requirements, and whether the organisation can accept a multi-tenant SaaS model.
β Cloud, Bridge, authentication and provisioning
Planning Tableau Cloud means understanding its constraints: you cannot control the underlying infrastructure, so you work within the boundaries of sites, capacity, and the features Salesforce exposes. Tableau Bridge extends Cloud to on-premises data, and you need to know when to deploy it, how many clients, and how to secure the connection. Authentication planning covers SAML, OpenID Connect, Kerberos, Mutual SSL, trusted authentication, and connected apps. Each method has prerequisites, and some are incompatible with certain deployment models. Automated user provisioning through SCIM reduces manual overhead, but only if the identity provider supports it and the organisation has the right entitlements. Troubleshooting advanced configuration issues means knowing where to look when settings conflict or when a protocol handshake fails.
β Migration planning and execution
Migrations are high-risk, high-visibility projects. You plan moves from Cloud to Server, Server to Cloud, Windows to Linux, Linux to Windows, one identity store to another, or a consolidation of multiple servers into fewer. Each path has dependencies: extract compatibility, authentication method support, operating system differences, and downtime tolerance. The Tableau Content Migration Tool automates some of this, but you still need custom scripts for edge cases like remapping users or rewriting connection strings. The exam tests whether you know which migrations require a full reinstall, which can be done in place, and what breaks when you change the identity store mid-flight.
β Topology design and configuration recommendations
Designing a process topology means specifying process counts, node count, and service-to-node relationships. You decide when to isolate services (backgrounders on dedicated nodes for extract refreshes) and when to colocate them (smaller deployments where separation adds complexity without benefit). External services (repository, file store, gateway) offload work and enable high availability, but they add network hops and points of failure. Configuration recommendations include choosing an identity store, setting specific TSM configuration keys, addressing encryption at rest and over the wire, and sizing hardware and network. A disaster recovery strategy ties this together: you define RTO and RPO, choose between active-passive and active-active, and script the failover process so it works when the primary site is offline.
How Design a Tableau Infrastructure is tested
At 22 percent, this topic anchors the exam. Items present a scenario with competing constraints (user growth projection, budget cap, compliance requirement) and ask you to recommend a topology, a licensing model, or a migration path. You lose marks when you choose a technically correct answer that ignores a stated constraint, such as recommending Server when the scenario specifies no on-premises infrastructure, or proposing a migration method that exceeds the allowed downtime window. The exam also tests your ability to map features to requirements: knowing that Advanced Management enables content migration API access, or that SCIM requires specific identity providers. Disaster recovery items describe an outage and ask what the architect should have configured in advance. The weight reflects the breadth: every decision in this topic has downstream consequences for deployment, monitoring, and maintenance.
A practice test gives you exposure to the scenario format before you pay for the exam. The PDF version lets you review topology and migration questions when you have ten minutes between meetings, so you can build pattern recognition across the 22 percent without blocking out study time you do not have.
The question below presents a migration scenario with constraints on downtime, identity store compatibility, and existing content volume.
How does the Tableau Server Resource Monitoring Tool contribute to the observability of a Tableau Server environment in terms of system resource usage?
After you design the infrastructure, you build it. This topic covers production-ready deployments: installing Server on Windows or Linux, configuring external services, implementing every authentication method the platform supports, and encrypting data in transit and at rest. The weight is 37 per cent because deployment is where theory meets the file system, the network, and the identity provider. Mistakes here cascade into support tickets, security audits, and downtime. β Installation and external service configuration You deploy Tableau Server using the...
After you design the infrastructure, you build it. This topic covers production-ready deployments: installing Server on Windows or Linux, configuring external services, implementing every authentication method the platform supports, and encrypting data in transit and at rest. The weight is 37 percent because deployment is where theory meets the file system, the network, and the identity provider. Mistakes here cascade into support tickets, security audits, and downtime.
β Installation and external service configuration
You deploy Tableau Server using the Installation Wizard or the Silent Installer for automated builds. External services (file store, repository, gateway) offload storage and compute, and you configure them during initial setup or migrate to them later. An unlicensed node participates in the coordination ensemble without consuming a license, useful in high-availability topologies. The coordination ensemble itself requires an odd number of nodes to maintain quorum. Backgrounder processes can be assigned specific node roles to isolate extract refresh workloads from interactive queries. Configuring Tableau for a load balancer means setting the gateway public URL and ensuring health checks hit the right endpoint. Air-gapped environments require pre-downloaded installers, offline activation, and careful handling of dependencies. Blue-green deployments let you validate a new build in parallel before switching traffic. The Resource Monitoring Tool server and agents collect performance data, and you install them separately from the core server.
β Authentication methods and troubleshooting
Authentication is the largest sub-group in this topic. SAML integrates with enterprise identity providers and requires XML metadata exchange, assertion signing, and name identifier mapping. Kerberos depends on service principal names, keytab files, and domain controller reachability; a misconfigured SPN or clock skew breaks the handshake silently. OpenID Connect is simpler to configure than SAML but requires the identity provider to support the protocol. Mutual SSL authenticates both client and server using certificates, used in embedded scenarios. Trusted authentication generates tokens for seamless sign-on from another application, while connected apps provide a more secure, scoped alternative. LDAP and Azure Active Directory synchronise users and groups, and each has its own query syntax and attribute mapping. Dependencies between methods matter: Kerberos does not work with Tableau Cloud, and some methods cannot coexist on the same site. Troubleshooting means reading logs, testing connectivity, and verifying that each component in the chain (DNS, certificates, firewall rules) is correct.
β Encryption and security configuration
Encryption protects data at rest and in transit. SSL encryption requires a certificate, a private key, and configuration of the gateway to serve HTTPS. Database encryption protects the Tableau repository, and extract encryption protects .hyper files on disk. Each layer addresses a different threat model: SSL for network eavesdropping, database encryption for physical access to the repository host, extract encryption for stolen backups. Setting up Kerberos SPNs is part of authentication, but it also enables encrypted communication between Tableau and data sources that require it. The exam tests whether you know which encryption method applies to which asset, and what breaks when certificates expire or keys are rotated.
β Platform-specific installation and troubleshooting
Linux and Windows installations share concepts but differ in implementation. On Linux, you use CLI commands or the Installation Wizard, verify system groups and file permissions, and check that the unprivileged account has the rights it needs. On Windows, you use the Run As service account and ensure it has the correct privileges. Installation issues often trace to operating system configuration: ports already bound, firewall rules blocking traffic, DNS resolution failures, or proxy settings that prevent activation. Interfaces with external systems (LDAP, Kerberos, SAML) fail when network routes are wrong or certificates are untrusted. Logs are your diagnostic tool: Tableau logs in the data directory, operating system logs for service startup failures, and network traces when connectivity is suspect. Identifying the right log file for a given failure mode is part of the skill.
How Deploy Tableau Server is tested
At 37 percent, this is the heaviest topic. Items describe a deployment requirement (high availability with external repository, Kerberos authentication for a specific data source, SSL with a wildcard certificate) and ask you to configure it or troubleshoot a failure. You lose marks when you choose a configuration that works in a lab but fails under the stated constraints: proposing SAML when the identity provider only supports LDAP, or configuring Kerberos without verifying SPN registration. Authentication troubleshooting items give you symptoms (users see a login loop, or an error message) and ask what is misconfigured. Encryption items test whether you know which setting encrypts which asset, and whether you can sequence the steps (generate CSR, install certificate, configure gateway, restart services). The weight reflects the surface area: every authentication method, every external service, both operating systems, and every failure mode that stops a deployment going live.
Deployment questions span authentication, encryption, external services, and platform-specific configuration. The practice test shows you how items combine multiple concepts in one scenario, so you learn to check every dependency before choosing an answer. Timed sessions replicate exam pressure when you have forty questions and limited time to parse logs and error messages.
The sample below gives you a Kerberos authentication failure with symptoms and asks you to identify the root cause from the configuration details provided.
For a large-scale Tableau Server deployment, what is the most effective strategy for collecting and analyzing server process metrics to maintain optimal performance?
Once the deployment is live, you keep it running. This topic is the largest at 41 per cent, covering observability, performance tuning, automation, and extensions. You build admin dashboards from the repository, run load tests, interpret metrics, troubleshoot slow workbooks, and script maintenance tasks. The exam tests whether you can diagnose a performance problem from incomplete data and choose the intervention that fixes the root cause rather than the symptom. β Administrative views and observability Custom administrative views query the...
Once the deployment is live, you keep it running. This topic is the largest at 41 percent, covering observability, performance tuning, automation, and extensions. You build admin dashboards from the repository, run load tests, interpret metrics, troubleshoot slow workbooks, and script maintenance tasks. The exam tests whether you can diagnose a performance problem from incomplete data and choose the intervention that fixes the root cause rather than the symptom.
β Administrative views and observability
Custom administrative views query the Tableau repository schema directly. You interpret event types, join tables, and build dashboards that answer common questions: which workbooks consume the most CPU, which users have not signed in, which extracts are failing. Admin Insights on Tableau Cloud provides pre-built views, but Server requires you to build your own. The Resource Monitoring Tool collects process metrics, latency data, and resource usage across nodes. You map its capabilities to observability requirements: if you need to track query performance by data source, RMT captures that; if you need operating system memory pressure, you collect OS metrics separately. Log analysis requires a strategy: centralised logging, retention policy, and tooling to parse and alert on errors. Interpreting observability data means spotting patterns (backgrounder queue depth rising, cache hit rate falling) and revising architecture before users complain.
β Load testing and performance tuning
Load testing validates that the topology can handle projected user load. You recommend a strategy (test realistic workloads, not synthetic ones), configure a tool like TabJolt, create test plans that simulate concurrent users, and interpret results to find bottlenecks. A passing load test does not mean the system is fast; it means it does not fall over. Performance tuning starts after deployment. You troubleshoot slow workbooks by analysing performance recordings, identify whether the delay is in the data source query, the view rendering, or the network, and create an action (optimise the query, reduce mark count, cache the extract). Resource analysis tells you if the server is CPU-bound, memory-bound, or I/O-bound. Workload analysis tells you if the problem is one expensive workbook or many cheap ones. Caching is the fastest fix when it applies: tuning cache timeout and warming caches for high-traffic views.
β Connectivity troubleshooting and Activity Log
Database connectivity issues are common in multi-node environments. A workbook loads on one node but times out on another. You check firewall rules, DNS resolution, data source credentials, and whether the connection is going through a proxy or load balancer. The repository connection is a special case: if the external repository is unreachable, the entire server stops. Activity Log captures user actions, content access, and sign-in events for Tableau Cloud or Server. You configure it, send logs to an external system, and use them for security audits or usage analysis. Connectivity and logging are not glamorous, but they are where deployments fail in production.
β Automation and APIs
Automation reduces operational overhead and error rates. You manage server resources programmatically using TSM, REST APIs, and tabcmd. TSM scripts configure settings and restart services; REST APIs publish workbooks, update permissions, and manage users; tabcmd automates tasks like triggering extract refreshes. You recommend a deployment method for these scripts (Windows Scheduler, cron, or orchestration tools) and schedule them to run during maintenance windows. Automated disaster recovery means scripting backup, failover, and validation so a non-expert can execute the plan. Multi-node upgrades require coordination: stopping services, upgrading nodes in sequence, and verifying health before resuming traffic. Maintenance tasks like cleanup and backup run on a schedule, and you monitor their logs to catch failures early.
β Extensions, webhooks and embedded solutions
Extensions expand Tableau's capabilities. The Metadata API exposes lineage and schema information for governance tools. Dashboard extensions and web data connectors run custom code inside a workbook, and you configure sandboxing and network access. Server extensions must be approved and managed centrally. Content automation uses webhooks to trigger workflows when an event occurs (a workbook is published, an extract refresh completes), or you schedule tasks with REST, tabcmd, or Hyper APIs. Embedded solutions integrate Tableau into another application. Trusted tickets generate short-lived tokens for single sign-on; connected apps provide a more secure, OAuth-based alternative. You configure them, test the integration, and troubleshoot when tokens expire or scopes are wrong.
How Monitor and Maintain a Tableau Deployment is tested
At 41 percent, this topic dominates the exam. Items present a performance symptom (slow dashboard load, rising backgrounder queue, failed extract refresh) and ask you to diagnose the root cause from metrics, logs, or a performance recording. You lose marks when you choose an intervention that addresses a symptom rather than the cause: restarting the server when the real problem is an under-provisioned backgrounder, or increasing cache timeout when the workbook query itself is inefficient. Automation items describe a recurring task and ask you to script it or choose the right API. Observability items give you partial data (CPU usage is high, but you do not know which process) and ask what additional metric you need to collect. The weight reflects the operational reality: architects spend more time maintaining deployments than building them, and the exam reflects that balance.
Monitoring and automation questions require you to synthesise metrics, logs, and architecture knowledge. The practice test lets you see how items layer complexity (a performance problem with multiple plausible causes, an automation task with dependencies) so you learn to eliminate wrong answers systematically rather than guessing under time pressure.
The sample below describes a performance degradation with metrics from the Resource Monitoring Tool and asks you to determine the next diagnostic step.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Analytics-Arch-201 Exam Questions π