Salesforce Certified Slack Administrator Practice Exam
Built to the current Slack Administrator exam guide — six weighted objective areas, 105 minutes, a published 65% passing score, and the newly assessed Slack AI, lists and canvases, and Workflow Builder content. Objective-mapped questions, source-linked explanations in Learn mode, full timed simulation in Exam mode.
Start 24-hour free trial →Slack Administrator exam at a glance
- Vendor
- Salesforce (Slack)
- Credential
- Salesforce Certified Slack Administrator
- Level
- Administrator (specialist credential)
- Blueprint
- Current exam guide; questions align to the Spring ’26 release. Six objective areas, each with a published weight
- Format
- 60 multiple-choice questions, plus up to five unscored questions randomly integrated
- Duration
- 105 minutes
- Passing score
- 65%
- Delivery
- Proctored — onsite at a testing center or in an online environment
- Prerequisites
- None
- Cost (USD)
- $200 registration; $100 retake, plus applicable local taxes
- Maintenance
- Annual. Complete the Slack Administrator maintenance badge on Trailhead once a year or the credential expires
- Reference materials
- None permitted during the exam
Sources: Salesforce — Slack Administrator Exam Guide · Salesforce — Slack Administrator credential page. Verify current details with Salesforce before scheduling.
About the Salesforce Certified Slack Administrator credential
The Slack Administrator credential is aimed at people who run Slack at scale — not casual power users. Salesforce frames the role as owning the implementation, daily configuration, administration and optimisation of a Slack organisation: the person who decides how users are provisioned, which channels exist and who can create them, which apps get approved, what happens to sensitive data, and whether the platform is actually being adopted.
The current exam guide is a meaningful rewrite rather than a refresh. Governance, security and compliance is now the single heaviest area, and app administration has been merged with a brand-new AI administration objective — enabling Slack AI features, managing permissions for them, and evaluating app scopes against security policy. Slack lists, canvases and enterprise search appear in the audience description for the first time, and Workflow Builder is described in more detail, including nested branching and Salesforce Flow triggers. There is no formal prerequisite, but the assessed surface assumes you have actually operated an admin dashboard.
Nearly every question is a scenario: you are given a business requirement and asked which setting, role, plan or policy satisfies it. That means memorising feature names is not enough — you need to know which lever sits at the org level and which sits at the workspace level, and what changes when a company moves onto Enterprise Grid. For the wider certification landscape this credential sits inside, see our Salesforce certification study guide.
Slack Administrator objective areas and weights
Six areas, weighted, summing to 100%. This replaces the previous outline, which listed a longer set of areas and published a percentage for only one of them. Plan study time roughly in proportion to the weights below — the top two areas alone account for well over a third of the exam.
Configuring security policies; meeting compliance standards for an individual’s message history; tracking a security concern in an Enterprise Grid environment; assessing PII sharing in Slack; deciding when to initiate a workspace migration into Enterprise Grid; moderating conversations that breach a code of conduct.
Implementing Slack AI; managing app installation and the app-approval process; evaluating app scopes for compliance with security policy. This area is new in its current shape — AI administration did not previously appear as an assessed objective.
Choosing the right feature for a stated requirement; determining the correct level of access for a person; the common responsibilities of the Admin and Owner roles; knowing when to use each Slack plan.
Managing channels; the permissions required to manage cross-workspace channels; adjusting settings so every member of a workspace can reach a feature; managing a user account’s access across multiple workspaces; configuring Slack Connect channels.
Granting the correct access level; getting new users into the right workspaces and channels; correct deactivation; choosing authentication and provisioning options by plan; managing identity-provider groups after configuration; access levels for Slack Connect and guest accounts; validating user groups and their permissions.
Monitoring feature adoption among active members; reading user feedback to identify adoption and usability problems; aligning Slack features and workflows with business-unit requirements; building a champion network to sustain adoption.
Source: Salesforce — Slack Administrator Exam Guide, Exam Outline. Weights are Salesforce’s published figures and total 100%.
Who the Slack Administrator exam is for
Salesforce describes the certified Slack Administrator as the primary architect of collaboration inside the platform, responsible for keeping every interaction inside the organisation’s security and data-governance policies. In practice that maps to four groups:
- Slack workspace and org administrators who own roles, channels, policies and the admin dashboard day to day.
- IT and systems administrators responsible for collaboration platforms generally — identity, provisioning, device management and compliance controls.
- Salesforce administrators and consultants extending into Slack, particularly where Salesforce records, channels and Flow-triggered workflows meet.
- Operations leads and internal-comms owners accountable for adoption: analytics, champion networks, and aligning Slack workflows to business-unit needs.
Within the Slack credential family, the Slack Consultant exam goes deeper on solution design and change management, and the Slack Developer exam covers building on the platform. If you administer Salesforce more broadly, the Platform Administrator exam is the natural companion. To see the roles this credential feeds and what they pay, review the IT administrator career track in our Career Hub.
What this Slack Administrator practice exam delivers
Learn mode
Correct answer, the reasoning, why each distractor fails, and a link to the Slack or Salesforce documentation the question derives from — immediately after each question. Most useful on the governance and Enterprise Grid scenarios, where the answer turns on one requirement in the stem.
Exam mode
60 questions on a 105-minute timer against the published 65% standard — the real format, including multiple-select items. Builds the pacing and the habit of reading each scenario for its governing constraint.
Source-linked explanations
Every answer cites a specific Slack Help or Salesforce article — SCIM provisioning, retention, DLP, app approval, Slack AI, analytics — so you can verify the reasoning and read further rather than memorise.
Score by objective area
Results break down across the six current areas. Because governance and app/AI administration alone carry 42% of the exam, knowing which of the six is weak tells you exactly where the next session goes.
Sample Slack Administrator practice questions
Ten free questions spread across all six current objective areas, each with a full explanation and a link to the documentation it derives from. The complete bank comes with the 24-hour trial.
A company with five business units wants each unit to keep its own Slack workspace while security policies, provisioning and compliance controls are administered centrally for all of them. Which Slack plan meets the requirement?
- Free
- Pro
- Enterprise Grid
- Business+
Show answer & explanation
Correct: C — Enterprise Grid. Enterprise Grid is the only plan that introduces an organisation layer above multiple interconnected workspaces, so each business unit can hold its own workspace while security, provisioning and compliance are administered once at the org level.
Why not the others: Free (A) is a single workspace with usage limits and no enterprise identity or compliance controls. Pro (B) is also a single workspace — there is no org layer to administer centrally. Business+ (D) adds enterprise identity and data-export capability, but it is still one workspace, so it cannot give five units separate workspaces under shared central administration.
Source: Slack Help — Slack plans and features →An administrator needs to delegate a narrow set of duties — managing channels and user groups — to a regional lead in an Enterprise Grid org, without granting broad organisation-wide control. What is the appropriate approach?
- Make the regional lead an Org Owner so they inherit every permission they might need
- Assign a scoped system role that carries only the specific administrative permissions required
- Share the Org Owner credentials with the regional lead for the duration of the project
- Add the regional lead as a single-channel guest in every channel they must manage
Show answer & explanation
Correct: B — assign a scoped system role. System roles let an org grant a defined subset of administrative permissions to a member, which is exactly the least-privilege delegation the scenario describes. The lead gets the duties they need and nothing else.
Why not the others: Org Owner (A) is the broadest role in the org and hands over far more than channel and user-group management. Credential sharing (C) breaks accountability and audit-log attribution and is never an acceptable answer. Single-channel guest (D) is a restricted external-collaboration role with no administrative capability at all — it is the opposite of what is needed.
Source: Slack Help — Assign members to system roles → Further reading: PowerKram — Platform administration fundamentals →An organisation wants Slack accounts created, updated and deactivated automatically as employee records change in its identity provider — including for staff who have not yet signed in to Slack. Which provisioning approach fits?
- Just-in-time provisioning, which creates the account on first successful sign-in
- SCIM provisioning, which lets the identity provider push create, update and deactivate operations to Slack
- Bulk email invitations sent from the admin dashboard each time HR reports a change
- Domain claiming, so anyone with a company email address is added automatically
Show answer & explanation
Correct: B — SCIM provisioning. SCIM lets the identity provider act as the system of record and push account creation, attribute updates and deactivation into Slack, so lifecycle changes flow without anyone signing in or an admin intervening.
Why not the others: Just-in-time (A) only creates the account at the moment of first sign-in, so it cannot pre-provision staff or push a deactivation. Manual invitations (C) are exactly the administrative overhead the requirement is trying to remove, and they do not deactivate anyone. Domain claiming (D) governs which accounts an org can claim and how people join — it is not a lifecycle sync mechanism.
Source: Slack Help — Manage members with SCIM provisioning →In an Enterprise Grid org, a project channel needs to be shared so that members of three different workspaces can participate in the same conversation. What should the administrator do?
- Create a duplicate channel in each of the three workspaces and ask members to cross-post
- Convert the channel to a private channel and invite individuals from the other workspaces
- Send a Slack Connect invitation to the other two workspaces
- Make it a multi-workspace channel shared across the three workspaces in the org
Show answer & explanation
Correct: D — a multi-workspace channel. Multi-workspace channels exist precisely so one channel can be shared across several workspaces inside the same Enterprise Grid org, keeping a single conversation and a single history rather than parallel copies.
Why not the others: Duplicate channels (A) fragment the conversation and the search history, which is the problem being solved. Making it private and inviting individuals (B) does not cross the workspace boundary and quietly hides the channel from everyone else. Slack Connect (C) is for collaborating with people in a different organisation; these three workspaces are inside one org, so Connect is the wrong tool.
Source: Slack Help — Manage multi-workspace channels →Security has asked that no external organisation be able to start a shared channel with the company until an administrator has reviewed the request. Which configuration satisfies this?
- Require admin approval for Slack Connect channel invitations, so requests queue for review before a connection is established
- Set message retention to the shortest permitted period for all external channels
- Turn off channel creation for all members of the workspace
- Restrict which apps members may install from the Slack Marketplace
Show answer & explanation
Correct: A — require admin approval for Slack Connect invitations. Slack Connect approval settings put inbound and outbound external-channel invitations into an administrator review queue, which is the control that gates the external connection itself.
Why not the others: Retention (B) governs how long messages are kept, not whether an external connection may be formed. Disabling channel creation (C) blocks ordinary internal work and still says nothing about external invitations. App install restrictions (D) address the Marketplace, a different risk surface entirely.
Source: Slack Help — Manage Slack Connect approval settings →A team requests an app that asks for permission to read the content of all public channels. Company policy forbids third-party services from ingesting message content. What should the administrator do?
- Approve the app but instruct the team to use it only in channels containing no sensitive material
- Approve the app and rely on the data-retention policy to limit exposure
- Review the requested scopes against policy and decline the request, using the app-approval process to record the decision
- Allow the install and audit usage afterwards to see whether any content was actually read
Show answer & explanation
Correct: C — evaluate the scopes and decline through the approval process. The current outline calls out evaluating app scopes for compliance with security policy as an assessed skill. The requested scope directly contradicts policy, and the app-approval workflow is the mechanism that both blocks the install and leaves a record of why.
Why not the others: Approving with a usage instruction (A) substitutes an unenforceable convention for a technical control. Retention (B) governs Slack’s own storage and has no bearing on what a third party has already ingested. Auditing afterwards (D) inverts the order — the policy violation happens at install time, not at detection time.
Source: Slack Help — Manage app approval →Leadership wants to pilot Slack’s AI capabilities — channel recaps, thread summaries and AI search — with one department before a wider rollout. What is the administrator’s role in this?
- Nothing — AI features are available to every member automatically once the workspace is on a paid plan
- Turn on access to the AI features and manage which members are permitted to use them, then review adoption before extending the pilot
- Ask each pilot member to enable the AI features individually in their own preferences
- Install a third-party AI app from the Marketplace, since Slack has no native AI capability
Show answer & explanation
Correct: B — the admin enables the AI features and manages who may use them. The current exam guide lists AI management and governance as an administrator responsibility: turning on access to Slack AI features such as recaps, summaries and AI-powered search, and assigning user permissions for them. A departmental pilot is exactly that permission-scoped rollout.
Why not the others: Automatic availability (A) is wrong — access is administered, not implicit. Individual member preferences (C) would remove the governance control the pilot depends on. A Marketplace app (D) is unnecessary and factually wrong: Slack AI is native, and the outline assesses implementing it.
Source: Slack Help — Guide to AI features in Slack → Further reading: PowerKram — Salesforce certification study guide →Compliance requires that messages containing customer payment-card numbers be detected and acted on as they are posted, rather than found later during an investigation. Which capability addresses this?
- Audit logs, reviewed on a weekly schedule
- A custom retention policy that deletes messages after thirty days
- An export of workspace data, searched for card-number patterns
- Data loss prevention, which detects sensitive content against defined rules and takes action on it
Show answer & explanation
Correct: D — data loss prevention. DLP is the control designed to identify sensitive content against defined rules as it moves through Slack and act on it, which is what “detected and acted on as posted” requires. The other options are all retrospective.
Why not the others: Audit logs (A) record administrative and access events, not message content, and weekly review is by definition after the fact. Retention (B) eventually deletes the message but does nothing at the moment of posting — the data has already been exposed. A data export (C) is an investigative artefact produced after the event, not a preventive control.
Source: Slack Help — Slack data loss prevention → Further reading: PowerKram — Enterprise security practices →Security suspects that an org-level setting was changed without authorisation last week and needs to establish who changed what and when. Which source should the administrator use?
- The analytics dashboard, filtered to the week in question
- The channel where the change was announced, checking message edit history
- The audit logs, which record administrative and access events with actor, action and timestamp
- The billing history, which shows plan and configuration changes
Show answer & explanation
Correct: C — the audit logs. Audit logs are the record of administrative and access events in an Enterprise Grid org, capturing who performed an action, what was changed and when — exactly the evidence needed to track a security concern.
Why not the others: The analytics dashboard (A) reports usage and engagement, not configuration changes. Message edit history (B) reflects what someone said about a change, not the change itself, and is trivially unreliable as evidence. Billing history (D) covers plan and payment activity, not administrative settings.
Source: Slack Help — Audit logs in Slack →Six months after rollout, leadership wants evidence of whether a newly launched workflow is actually being used by active members before funding a second phase. What should the administrator do first?
- Review the analytics dashboard for activity and engagement among active members, and use those figures to make the recommendation
- Send an all-company message asking people to reply if they use the workflow
- Archive the channels associated with the workflow to see whether anyone objects
- Move the workspace to a higher plan so more reporting becomes available
Show answer & explanation
Correct: A — read the analytics dashboard. The adoption objective is explicitly about monitoring feature adoption among active members and making data-driven recommendations. The dashboard is the built-in source for that evidence, and it exists before any new spend is required.
Why not the others: A voluntary all-company reply (B) produces self-selected, unrepresentative data. Archiving channels to provoke complaints (C) is a disruptive experiment that measures noise rather than adoption. Upgrading the plan (D) commits budget before the question has been answered and inverts the decision the scenario asks for.
Source: Slack Help — View your analytics dashboard → Further reading: PowerKram — Platform administration fundamentals →Keep going: study guides and career paths
Slack administration sits inside two larger stories — the Salesforce certification ladder, and the collaboration-platform administrator role that hiring managers actually recruit for.
Deep dive: what changed, format and scoring, Enterprise Grid, study path, maintenance
What changed in the current exam guide
This is the most significant revision the credential has had. The outline has been restructured into six weighted areas that sum to 100%, replacing a longer list on which only one area carried a published percentage. Governance, security and compliance is now the heaviest single area at 22%, and app administration has absorbed a new AI administration objective to reach 20%. The audience description adds Slack AI enablement and governance, Slack lists and canvases, enterprise search, and a fuller account of Workflow Builder including nested branching and Salesforce Flow triggers. Anything written before this revision will over-prepare you on unweighted breadth and under-prepare you on AI and governance. Read the Salesforce certification study guide →
Format and scoring
Sixty scored multiple-choice questions in 105 minutes, plus up to five unscored questions that are randomly integrated and have no effect on your result. The passing score is published as 65%, which is unusually explicit for a Salesforce credential — many of its exams publish a per-form standard instead. No hard-copy or online reference materials may be used. Delivery is proctored, either onsite at a testing centre or online. Registration is US$200 with a US$100 retake, plus local taxes. Read the platform administration guide →
Enterprise Grid is where most candidates lose marks
A large share of the harder scenarios turn on one distinction: is this an org-level control or a workspace-level one? Migrating workspaces into an org, claiming domains, connecting identity-provider groups, assigning system roles, tracking a security concern across the org, and sharing a channel across several workspaces are all org-shaped problems. Retention exceptions, channel management permissions and default channels behave differently at the workspace level. Practise stating, for each setting you meet, where it lives and who can change it — and remember that Slack Connect crosses organisations while multi-workspace channels stay inside one. Read the enterprise security practices guide →
A realistic study path
The exam guide currently lists its official Trailmix as forthcoming, so self-study against Slack Help plus hands-on practice is the reliable route. A workable plan: spend the first block on the two heaviest areas — governance and app/AI administration — because together they carry 42% of the exam; work through the admin dashboard of a real or trial workspace rather than reading about it; then use timed practice to expose the areas where you recognise the feature but cannot place the setting. Candidates with a Salesforce administration background usually need extra time on identity, provisioning and compliance; candidates from an IT background usually need extra time on the adoption objective. Read the platform administration guide →
Maintenance and where the credential leads
Maintenance is annual, not multi-year: you complete the Slack Administrator maintenance badge on Trailhead each year, and the credential expires if you miss the due date. Treat it as a recurring calendar item rather than a distant renewal. As a career asset the credential is most valuable in combination — with Salesforce platform administration for the ecosystem roles, or with identity and security work for the collaboration-platform administrator roles where governance is the job. See the IT administrator career track →
Slack Administrator exam FAQ
What are the Slack Administrator objective areas and weights?
How long is the exam and what is the passing score?
Do I need the Salesforce Administrator certification first?
How much does the exam cost and how is it delivered?
How do I keep the credential current?
Does the exam cover Slack AI?
Start your free 24-hour Slack Administrator practice trial
Full access to the question bank, both study modes, source-linked explanations and score-by-objective-area. No credit card required.
Start free trial →