VA-003
HashiCorp Certified: Vault Associate (003) practice test
175 Hashicorp VA-003 practice questions with explanations, in study, timed and flashcard modes.
Full access
$99
- All 175 questions, with explanations
- Study, timed and flashcard modes
- Progress saved, resume any time
- Questions
- 175
- Free samples
- –
- Versions
- 1
- Updated
- Mar 2026
$99full access
Try the free samplesExam simulator
Practice VA-003 in the simulator.
Study, timed and flashcard modes. Answers and explanations as you go, and your progress saves.
At a glance
VA-003, by the numbers.
Official specifications published by Hashicorp.
- Duration
- 60 min
- Questions
- 57
- Passing score
- Not officially disclosed (approximately 70%)
- Exam fee
- $71

Exam guide
Everything about VA-003.
VA-003 · Hashicorp · 003
What is VA-003?
VA-003 is HashiCorp's Vault Associate exam, and it shows you can store secrets and control access with Vault. It suits cloud, security and DevOps engineers who are starting to use Vault at work. Vault is more than a password safe, because it can also create short-lived secrets on demand. These dynamic secrets, such as a database login that expires on its own, are a key topic. For example, you may choose between a service token and a batch token for a short job. The practice test works through authentication methods, policies, tokens, leases and secrets engines.
What you'll practise
- Choose an authentication method for people or for machines, based on the use case.
- Write Vault policies using paths and capabilities.
- Pick service or batch tokens, and explain root tokens and token accessors.
- Renew and revoke the leases on secrets.
- Choose secrets engines, compare static and dynamic secrets, and use transit encryption.
- Explain sealing, unsealing, storage backends and cluster options.
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: basic terminal skills and basic knowledge of on-premises or cloud architecture.
- Recommended: a basic grounding in security; production Vault use helps but is not required.
Who it's for
- DevOps and cloud engineers who manage application secrets.
- Security engineers who control access to systems and data with Vault.
- Engineers planning to move on to Vault Operations Professional.
Exam details
Published by Hashicorp, plus what is in our question bank.
- Duration
- 60 min
- Questions
- 57
- Passing score
- Not officially disclosed (approximately 70%)
- Level
- Associate
- Exam fee
- $71
- Delivery
- Certiverse (online proctored), online proctoring
- Schedule
- developer.hashicorp.com
- Valid for
- 2 years
- Recertification
- Pass the Vault Operations Professional exam (extends Associate credentials and earns Professional-level badge); Retake the 003 version of the Vault Associate exam starting 6 months before expiration (extends Associate credentials)
What does VA-003 cover?
9 weighted domains. Open a domain for its topics, and a topic for its objectives. Practice questions are tagged to these.
- Understand that auth methods are components in Vault that perform authentication and assign identity and policies to a user
- Role of auth methods in Vault
- Auth methods verify user/machine identity
- Auth methods return a Vault token upon successful authentication
- Token auth method is enabled by default on all Vault instances
- Auth methods are mounted at paths within Vault
- Select the correct authentication method for a given use case involving human users or machine/application workloads
- Selecting appropriate auth methods
- Userpass for simple username/password authentication
- LDAP for enterprise directory integration
- GitHub for developer teams using GitHub organizations
- AppRole for machine-to-machine authentication
- AWS auth method for AWS EC2/IAM-based authentication
- Kubernetes auth method for pods running in Kubernetes
- OIDC/JWT for SSO integration
- TLS certificates auth method
- Differentiate between authentication methods designed for human users and those designed for machine/application workloads
- Human-centric auth methods
- Machine-oriented auth methods
- LDAP - enterprise directory services
- GitHub - developer organizations
- Userpass - simple credentials
- OIDC - single sign-on
- Human auth methods typically involve interactive login
- AppRole - for applications and automated workflows
- AWS - for EC2 instances and IAM roles
- Kubernetes - for pods and service accounts
- TLS Certificates - for certificate-based machine identity
- Machine auth methods are non-interactive and automated
- Explain how Vault uses entities and groups to manage identities across different authentication backends
- Vault Identity system
- Entities represent a single person or machine across multiple auth methods
- Aliases map external identity to an entity
- Groups aggregate entities for policy assignment
- Internal groups vs. external groups
- Identity-based policies via group membership
- Demonstrate the ability to authenticate to Vault using CLI commands, API calls, and the web UI
- CLI authentication
- API authentication
- UI authentication
- vault login command
- vault login -method=userpass
- VAULT_TOKEN environment variable
- Token helper for storing tokens locally
- POST to auth method login endpoint
- X-Vault-Token header for authenticated requests
- API returns client_token in response
- curl examples for API authentication
- Web-based login at Vault address
- Selecting auth method from dropdown
- Configure and enable authentication methods using the Vault CLI, HTTP API, and web UI
- Enabling and configuring auth methods
- vault auth enable command
- vault auth enable -path= for custom mount paths
- Configuring auth method settings (e.g., default_lease_ttl)
- API: POST /sys/auth/:path to enable auth methods
- UI: Access > Auth Methods > Enable new method
Hands-on skills
- Enable an auth method via CLI
- Authenticate using different auth methods
- Configure AppRole auth method
- Manage entities and groups
Common mistakes
- Confusing auth methods with secrets engines
- Forgetting that token auth is always enabled by default
- Mixing up human-centric and machine-oriented auth methods
- Not understanding that entities consolidate identities across multiple auth backends
- Explain why Vault policies are necessary and how they enforce least-privilege access
- Purpose and design of Vault policies
- Policies control access to paths in Vault
- Vault is deny-by-default: no policy means no access
- Policies are written in HCL or JSON
- Two built-in policies: root and default
- Root policy grants full access to everything
- Default policy is attached to all tokens by default
- Write and interpret Vault policy paths including glob and segment wildcards
- Policy path syntax
- Paths correspond to Vault API paths
- Glob (*) matches any character within a single path segment or at the end
- Plus (+) is a single-segment wildcard (matches exactly one path segment)
- Path matching is most-specific-wins
- Policy path examples: secret/data/*, kv/+/team_*
- Identify and apply the correct capabilities for Vault policy definitions
- Policy capabilities
- create - create new data at a path (POST/PUT to non-existent)
- read - read data at a path (GET)
- update - modify data at a path (POST/PUT to existing)
- delete - delete data at a path (DELETE)
- list - list data at a path
- sudo - elevated access needed for certain system paths
- deny - explicitly deny access (overrides all other capabilities)
- Select or design an appropriate Vault policy given a set of access control requirements
- Policy design for requirements
- Principle of least privilege
- Combining multiple policies for fine-grained access
- Policies are additive (union of capabilities)
- deny capability overrides additive behavior
- Associating policies with tokens and auth methods
- Create, read, update, and delete Vault policies using the CLI and web UI
- Managing policies via CLI and UI
- vault policy write <name> <file> - create/update policy from file
- vault policy read <name> - display policy content
- vault policy list - list all policies
- vault policy delete <name> - remove a policy
- UI: Policies > Create ACL policy
- Editing policies in the UI text editor
Hands-on skills
- Write HCL-format policies
- Use vault policy write/read/list/delete commands
- Associate policies with auth methods and tokens
- Test policy capabilities with vault token capabilities
Common mistakes
- Forgetting Vault is deny-by-default
- Confusing * (glob) with + (segment wildcard) in policy paths
- Not understanding that deny capability overrides everything
- Assuming policies are evaluated independently rather than additively
- Compare service and batch tokens and select the appropriate type for a given use case
- Service tokens vs. batch tokens
- Service tokens: stored in Vault backend storage, can create child tokens, support all features
- Service tokens start with hvs. prefix
- Batch tokens: not persisted, lightweight, encrypted binary blobs
- Batch tokens start with hvb. prefix
- Batch tokens cannot be renewed, cannot create child tokens
- Batch tokens are ideal for high-volume, short-lived workloads
- Service tokens are the default type
- Describe the creation, use, and security considerations of root tokens in Vault
- Root token management
- Root tokens have the root policy attached
- Root tokens are generated during vault init
- Root tokens can be regenerated using unseal keys (vault operator generate-root)
- Root tokens should be revoked after initial setup
- Root tokens never expire (no TTL)
- Best practice: do not use root tokens for day-to-day operations
- Explain the purpose and use cases of token accessors for managing tokens without exposing the token ID
- Token accessors
- Token accessor is a reference to a token (not the token itself)
- Can be used to look up token properties without the token ID
- Can look up token capabilities on a path
- Can be used to renew or revoke a token
- Enables management operations without exposing the actual token
- Batch tokens do not have accessors (accessor is n/a)
- Explain how TTL, max TTL, and renewal affect token validity and access to Vault secrets
- Token TTL and lifecycle
- TTL (time-to-live) defines how long a token is valid
- Tokens can be renewed to extend TTL
- Max TTL limits how long a token can be renewed
- explicit_max_ttl sets a hard cap on token lifetime
- Periodic tokens have no max TTL (can be renewed indefinitely)
- When a token expires, all child tokens and leases are revoked
- Explain what orphan tokens are, how they differ from child tokens, and when they are used
- Orphan tokens
- Orphan tokens have no parent token
- Orphan tokens do NOT expire when their parent token expires
- Created with vault token create -orphan or certain auth methods
- Orphan tokens still have their own TTL and max TTL
- Auth method tokens are orphan tokens by default
- Tokens directly created by vault token create are child tokens by default
- Create Vault tokens with appropriate properties for different use cases using CLI commands
- Token creation options
- vault token create command and its flags
- -policy flag to attach policies
- -ttl flag to set TTL
- -orphan flag to create orphan tokens
- -type=batch to create batch tokens
- -num-uses to limit usage count
- -wrap-ttl to create a wrapped token
- vault token renew to extend token lifetime
- vault token revoke to invalidate tokens
Hands-on skills
- Create service and batch tokens
- Look up token properties using token accessor
- Revoke tokens using vault token revoke
- Interpret vault token lookup output
Common mistakes
- Confusing batch tokens (hvb.) with service tokens (hvs.)
- Assuming batch tokens can be renewed (they cannot)
- Forgetting that orphan tokens still have their own TTL
- Not recognizing num_uses=0 means unlimited uses
- Confusing token accessors with token IDs
- Explain what a lease ID represents and its role in managing the lifecycle of dynamic secrets
- Lease ID concept
- Leases are metadata associated with secrets (especially dynamic secrets)
- Lease ID is a unique identifier for each lease
- Lease ID is used to renew, revoke, or inspect a lease
- Leases have a TTL that determines when the secret expires
- When a lease expires, the associated secret is revoked
- Describe how to renew leases using the CLI and API, and understand renewal constraints
- Lease renewal
- vault lease renew <lease_id> to renew a lease
- Renewal extends the TTL of the lease
- Max TTL limits how long a lease can be renewed
- Not all secrets engines support lease renewal
- API: PUT /sys/leases/renew with lease_id
- Describe how to revoke leases and understand the impact of revocation on associated secrets
- Lease revocation
- vault lease revoke <lease_id> to revoke a specific lease
- vault lease revoke -prefix <prefix> to revoke all leases under a prefix
- Revocation invalidates the associated secret (e.g., deletes DB credentials)
- Revoking a parent token also revokes all associated leases
- API: PUT /sys/leases/revoke with lease_id
- Force revocation with -force flag
Hands-on skills
- Manage dynamic secrets leases with vault lease commands
- Renew and revoke database credential leases
- Inspect lease metadata
Common mistakes
- Confusing token TTL with lease TTL
- Not understanding that lease revocation also deletes the underlying secret
- Forgetting that prefix-based revocation affects all leases under that path
- Assuming all secrets have leases (static KV secrets do not)
- Select the appropriate secrets engine for a given use case
- Secrets engine selection
- KV (Key/Value) v1 and v2 for static secrets storage
- Database secrets engine for dynamic database credentials
- Transit for encryption as a service
- PKI for dynamic X.509 certificates
- AWS secrets engine for dynamic AWS credentials
- Cubbyhole for token-scoped secret storage
- Identity for identity-based tokens
- Compare static and dynamic secrets, explain their use cases, and identify which secrets engines produce each type
- Static vs. dynamic secrets
- Static secrets: stored and retrieved (e.g., KV secrets engine)
- Static secrets do not expire automatically
- Dynamic secrets: generated on demand with a lease
- Dynamic secrets are unique per request and automatically revoked
- Dynamic secrets reduce blast radius of credential compromise
- Database secrets engine is the canonical example of dynamic secrets
- AWS secrets engine generates temporary IAM credentials
- Explain the Transit secrets engine's purpose as encryption as a service and its key operations
- Transit secrets engine (EaaS)
- Provides encryption as a service (EaaS)
- Data is not stored in Vault - only encryption/decryption operations
- Supports AES-GCM, ChaCha20-Poly1305, and other algorithms
- Named encryption keys for different purposes
- Supports key rotation without re-encrypting all data
- Rewrap operation to update ciphertext to latest key version
- Encrypt, decrypt, rewrap, sign, verify operations
- Explain the role of secrets engines in Vault and how they are organized via mount paths
- Secrets engines overview
- Secrets engines store, generate, or encrypt data
- Mounted at specific paths within Vault
- Can be enabled, disabled, tuned, and moved
- Multiple instances of the same engine can be mounted at different paths
- Each engine is isolated to its own mount path
- Some engines connect to external services (databases, cloud providers)
- Explain how response wrapping provides secure secret transmission using short-lived wrapping tokens
- Response wrapping with cubbyhole
- Response wrapping stores a secret in a cubbyhole and returns a wrapping token
- Only the wrapping token reference is transmitted, not the actual secret
- Wrapping tokens are single-use: can only be unwrapped once
- Short TTL on wrapping token limits exposure window
- Detects tampering: if wrapping token is used twice, it signals compromise
- Created with -wrap-ttl flag on CLI or X-Vault-Wrap-TTL header on API
- Unwrap with vault unwrap command
- Articulate the security and operational benefits of using short-lived, dynamically generated secrets
- Value of dynamic secrets
- Reduced blast radius when credentials are compromised
- Automatic revocation when lease expires
- Unique credentials per application instance
- No shared credentials between services
- Audit trail of who requested which credentials and when
- Eliminates password sprawl and long-lived credentials
- Enable and configure secrets engines using the Vault CLI, HTTP API, and web UI
- Enabling secrets engines
- vault secrets enable <type> to enable at default path
- vault secrets enable -path=<custom> <type> for custom mount path
- vault secrets list to view all enabled engines
- vault secrets disable <path> to remove an engine
- vault secrets tune <path> to modify engine configuration
- API: POST /sys/mounts/:path to enable a secrets engine
- UI: Secrets Engines > Enable new engine
- Read and write Vault secrets using the CLI, HTTP API, and web UI across different secrets engines
- Reading and writing secrets
- vault kv put <path> <key>=<value> to write KV secrets
- vault kv get <path> to read KV secrets
- vault kv get -version=<n> for specific versions (KV v2)
- vault kv delete and vault kv destroy for KV v2
- vault kv metadata for version metadata (KV v2)
- API: GET/PUT to the secrets engine API path
- KV v2 paths include /data/ segment: secret/data/<path>
- UI: navigate to secrets engine and browse/edit
Hands-on skills
- Enable and configure KV v2 secrets engine
- Create and manage dynamic database secrets
- Use Transit engine for encryption/decryption
- Implement response wrapping
- Manage KV secret versions
Common mistakes
- Confusing Transit (encryption only) with KV (storage)
- Forgetting the /data/ segment in KV v2 API paths
- Assuming all secrets engines produce dynamic secrets
- Confusing vault secrets list with vault kv list
- Not understanding that multiple instances of the same engine can be mounted at different paths
- Perform encryption and decryption operations using the Transit secrets engine via CLI and API
- Transit encrypt/decrypt operations
- vault write transit/encrypt/<key-name> plaintext=<base64-encoded>
- Plaintext must be base64-encoded before encryption
- Ciphertext format: vault:v<version>:<ciphertext>
- vault write transit/decrypt/<key-name> ciphertext=<ciphertext>
- Decryption returns base64-encoded plaintext
- Must decode base64 to get original plaintext
- API: POST /transit/encrypt/:name and POST /transit/decrypt/:name
- Perform encryption key rotation and rewrap operations using the Transit secrets engine
- Key rotation and rewrapping
- vault write -f transit/keys/<key-name>/rotate to rotate key
- Key rotation creates a new version of the encryption key
- Old ciphertext can still be decrypted with the old key version
- Rewrap operation: vault write transit/rewrap/<key-name> ciphertext=<old>
- Rewrap updates ciphertext to use the latest key version without exposing plaintext
- min_decryption_version and min_encryption_version control key version constraints
- API: POST /transit/keys/:name/rotate
Hands-on skills
- Create Transit encryption keys
- Encrypt and decrypt data using Transit
- Rotate encryption keys
- Rewrap ciphertext to latest key version
Common mistakes
- Forgetting to base64-encode plaintext before encryption
- Forgetting to base64-decode after decryption
- Confusing key rotation with re-encryption (rewrap does not expose plaintext)
- Thinking rotation invalidates old ciphertext (it does not)
- Describe how Vault's encryption barrier ensures all data at rest is encrypted in the storage backend
- Vault encryption barrier
- All data written to storage backend is encrypted
- Encryption barrier sits between Vault core and storage backend
- Storage backend never sees unencrypted data
- Vault uses AES-256-GCM for encryption
- Root key (formerly master key) encrypts the encryption key
- Encryption key is stored in the keyring
- Data flow: Vault Core -> Encryption Barrier -> Storage Backend
- Explain the seal/unseal process including Shamir's Secret Sharing and auto unseal mechanisms
- Seal/unseal process
- Auto unseal
- Sealed Vault can access storage but cannot decrypt data
- Unsealing reconstructs the root key to decrypt the encryption key
- Shamir's Secret Sharing: root key is split into shares
- Default: 5 key shares, 3 required threshold
- vault operator unseal command to provide key shares
- vault operator seal to manually seal Vault
- Sealing requires sudo capability on sys/seal
- Vault starts in a sealed state after restart
- Auto unseal delegates root key protection to an external service
- Supported providers: AWS KMS, Azure Key Vault, GCP Cloud KMS, HSM (PKCS#11)
- Configure essential Vault environment variables for CLI communication with a Vault server
- Vault environment variables
- VAULT_ADDR - address of the Vault server (e.g., http://127.0.0.1:8200)
- VAULT_TOKEN - token for authenticating to Vault
- VAULT_CACERT - path to CA certificate for TLS verification
- VAULT_SKIP_VERIFY - skip TLS verification (not for production)
- VAULT_NAMESPACE - target namespace (Enterprise feature)
- VAULT_FORMAT - output format (json, table, yaml)
- Environment variables override CLI defaults
Hands-on skills
- Initialize Vault with custom key shares and threshold
- Unseal Vault using key shares
- Configure auto unseal with a cloud KMS
- Set and verify Vault environment variables
Common mistakes
- Confusing sealed state (can access storage, cannot decrypt) with an offline state
- Not knowing that sealed Vault requires threshold number of key shares to unseal
- Forgetting that VAULT_ADDR must be set before any CLI operation
- Confusing root key with encryption key
- Compare self-managed Vault clusters with HashiCorp-managed HCP Vault Dedicated clusters
- Cluster deployment strategies
- Self-managed: install and operate Vault on your own infrastructure
- HCP Vault Dedicated: HashiCorp-managed Vault cluster on HCP
- HCP Vault handles upgrades, backups, and operational overhead
- Self-managed offers full control but more operational burden
- Recommended: 3 or 5 node clusters for high availability
- Single leader with standby nodes in HA configuration
- Explain the role and options for storage backends, with emphasis on Integrated Storage (Raft)
- Storage backend options
- Integrated Storage (Raft): built-in, recommended storage backend
- Raft uses consensus protocol for data replication across nodes
- Consul storage backend (legacy option)
- Storage backend only stores encrypted data
- Integrated Storage vs. Consul: Raft is simpler (no external dependency)
- Storage backend configuration in Vault server config file
- HA support varies by storage backend
- Explain Shamir's Secret Sharing algorithm and how it is used for Vault unseal key management
- Shamir secret sharing in depth
- Shamir's Secret Sharing splits the root key into N shares
- Any T (threshold) of N shares can reconstruct the root key
- Provides protection: no single person holds the complete root key
- Key shares distributed to trusted operators
- vault operator init sets -key-shares and -key-threshold
- vault operator rekey to change the number of shares or threshold
- vault operator rotate to rotate the encryption key (not the root key)
- Differentiate between disaster recovery and performance replication and explain their use cases
- Enterprise replication types
- Disaster Recovery (DR) Replication: mirrors entire primary cluster for failover
- DR secondaries do NOT handle client requests (warm standby)
- DR replicates tokens and leases from primary
- Performance Replication: mirrors configuration for read scaling
- Performance secondaries CAN handle client requests
- Performance secondaries maintain their own tokens and leases
- Both are Vault Enterprise features
- DR = fault tolerance; Performance = scalability
- Compare the features, responsibilities, and trade-offs between self-managed and HCP Vault deployments
- Self-managed vs. HCP Vault
- Self-managed: full control, responsible for upgrades, backups, HA, scaling
- Community Edition (open source) and Enterprise Edition for self-managed
- HCP Vault Dedicated: fully managed service
- HCP handles infrastructure, upgrades, high availability, backups
- HCP available in AWS and Azure regions
- HCP supports most Vault Enterprise features
- Trade-off: operational control vs. operational simplicity
Hands-on skills
- Configure Vault with Integrated Storage (Raft)
- Initialize Vault with custom key shares and threshold
- Understand reference architecture diagrams
- Configure and observe replication (conceptual)
Common mistakes
- Confusing DR replication (no client requests) with Performance replication (handles client requests)
- Forgetting that both replication types are Enterprise-only features
- Confusing vault operator rekey (new shares) with vault operator rotate (new encryption key)
- Assuming Consul storage is still the recommended backend (Raft/Integrated Storage is now recommended)
- Describe the Vault Agent, its capabilities (auto-auth, caching, templating), and how it simplifies secret consumption for applications
- Vault Agent capabilities
- Vault Agent is a client-side daemon
- Auto-auth: automatically authenticates to Vault and manages token lifecycle
- Caching: caches tokens and leases locally to reduce Vault load
- Templating: renders secrets into configuration files using Consul Template syntax
- Eliminates need for applications to be Vault-aware
- Agent runs as a sidecar or on the same host as the application
- Handles token renewal automatically
- Describe the Vault Secrets Operator, its features, and how it enables native Kubernetes secret management with Vault
- Vault Secrets Operator (VSO)
- VSO is a Kubernetes operator for syncing Vault secrets to Kubernetes Secrets
- Manages the lifecycle of Kubernetes Secret objects
- Supports instant updates when Vault secrets change
- Encrypted client cache for resilience during Vault unavailability
- Secret transformation: modifies secret data before creating Kubernetes Secret
- Kubernetes-native approach to secret management
- Reduces complexity compared to Vault Agent sidecar in Kubernetes
Hands-on skills
- Configure Vault Agent with auto-auth
- Set up Agent templating for configuration files
- Deploy VSO in a Kubernetes cluster
- Configure VSO for instant updates
Common mistakes
- Confusing Vault Agent with Vault Proxy
- Not knowing that VSO is specifically for Kubernetes
- Forgetting that Agent templating uses Consul Template syntax
- Confusing VSO capabilities with Vault Agent sidecar injector
How do I earn this certification?
Passing VA-003 earns the HashiCorp Certified: Vault Associate in the Security Automation track.
- VA-003Vault Associate (003)
- VAULT-OPERATIONS-PROFESSIONALHashiCorp Certified: Vault Operations ProfessionalVault Operations Professional
- TERRAFORM-ASSOCIATETerraform Associate (003)Complementary IaC skills - Terraform is frequently used alongside Vault for infrastructure provisioning
- Consul Associate (003)Consul Associate (003)Complementary networking and service mesh skills in the same Security Automation certification track
How to study for this exam?
Use the VA-003 practice test alongside the official material below.
- Vault Associate (003) Learning Pathself-paced tutorials · Free
Official study guide with curated tutorials covering all exam objectives organized by learning area
- Vault Associate (003) Exam Content Listexam reference · Free
Complete list of exam objectives mapped to specific documentation and tutorials
- Vault Associate (003) Sample Questionspractice questions · Free
Official sample questions in True/False, Multiple Choice, and Multiple Answer formats
- Preparing for the HashiCorp Certified: Vault Associate (003) Certification Exam (Webinar)webinar · Free
Official exam preparation webinar from HashiCorp
Complete product documentation for the version tested on the exam
Getting started tutorials covering core Vault concepts
Documentation for all supported authentication methods
Documentation for all secrets engines including KV, Transit, Database, etc.
Core concepts including tokens, policies, seal/unseal, leases, and response wrapping
Complete CLI command reference for all Vault operations
Official community forum for Vault discussions and troubleshooting
FAQ and support articles about HashiCorp certification exams
Three ways to practise
Study mode
Work through the bank at your own pace with the answer and explanation one tap away. Flag questions, add notes, bookmark the hard ones.
Open in the simulatorTimed mode
A shuffled deck with a countdown that mirrors the real exam. Your score is saved to your attempt history.
Open in the simulatorFlashcards
Question on the front, answer on the back. Good for the last week before the exam.
Open in the simulatorVA-003 questions, answered
