Alteryx Server Admin study plan

Diagram the Server topology (Controller, Worker nodes, Gallery, Mongo, persistence layer) from memory and label every component's role

Explain how the Controller schedules and dispatches work versus how a Worker executes it, in writing

List which components are stateless versus stateful and note the implications for scaling

Identify the ports and services each component depends on and build a reference table

Trace the full lifecycle of a scheduled workflow from trigger to output and annotate each handoff point

Describe how the Scheduler queue, worker assignment, and concurrency settings interact

Compare worker types and runtime settings and record when each is appropriate

Map which architecture components are involved in execution versus content storage

Write a pre-installation checklist covering host requirements, service accounts, and prerequisites

Sequence the installation steps for a multi-node deployment and note the order dependencies

Document the upgrade path and the pre-upgrade backup/validation steps required before patching

List the configuration files and settings that must be reviewed post-install

Compare supported authentication methods and select the right one for three stated scenarios

Configure role-based permissions in a lab and verify each role's effective access

Explain how authentication and authorization differ in the Server and where each is enforced

Identify security hardening steps for transport, service accounts, and API access

Create and troubleshoot scheduled workflows, including dependency and failure-handling behavior

Diagnose a stuck or failed job by inspecting queue state and worker health

Distinguish the sharing/permission models for workflows, collections, and curated content

Set up a curated collection and verify visibility for different user roles

Locate and interpret the primary log sources and correlate entries across components

Build a monitoring checklist covering service health, queue depth, and worker availability

Practice root-causing three simulated failure scenarios using logs only

Identify which metrics warrant alerting and set thresholds

Define what must be backed up (Mongo, settings, content) and how each is restored

Design an HA approach addressing single points of failure in the architecture

Write and test a recovery procedure for a simulated node loss

Document RTO/RPO assumptions and validate them against the backup strategy

Configure and validate a data connection and explain how credentials are stored and referenced

Compare credential-handling options and select the appropriate one for given requirements

Troubleshoot a connectivity failure by isolating network, driver, and credential causes

Run a full-length practice exam and review every missed item against its domain