Salesforce-Slack-Administrator Practice Test
Updated On 1-Jan-2026
200 Questions
You're the Primary Org Owner for your university's Slack Enterprise Grid. You're
responsible for launching Slack to first-year students and faculty members.
What is the most efficient way to set up students as full members and faculty members as
Workspace Admins?
(Select the best answer.)
A. Use SCIM provisioning to create accounts for students and faculty members. Then, update their profile fields to reflect their title by syncing with the SCIM API.
B. Use SCIM provisioning to create accounts for students and faculty members, and create an identity provider (IdP) group for all faculty members. Then, promote the members of the IdP group .. bulk to Workspace Admins.
C. Use "Just-in-time" provisioning to allow students and faculty members to create an
account upon first login, eliminating the time and effort with onboarding new accounts.
Then, promote each faculty member to Workspace Admin.
D. Use either \Just-in-time" or SCIM provisioning to invite students and faculty members to Slack. Then, create a user group of faculty members and promote that user group in bulk to Workspace Admins.
Explanation:
1. Why B is correct?
SCIM provisioning is the most efficient way to create accounts at scale for both students and faculty
Creating an IdP group for faculty allows for:
➡️ Automatic role assignment through group synchronization
➡️ Bulk promotion to Workspace Admin status
➡️ Easy future management as faculty changes occur
This approach minimizes manual work while ensuring proper permissions
2. Why A is incorrect?
While SCIM provisioning works for account creation, updating profile fields doesn't address the Workspace Admin requirement
This approach would require manually promoting each faculty member individually
3. Why C is incorrect?
Just-in-time provisioning doesn't automatically handle the Workspace Admin permissions
Would still require manually promoting each faculty member
Less control over account creation compared to SCIM
4. Why D is incorrect?
User groups can't be directly promoted to Workspace Admin status in bulk
While you can mention user groups, admin permissions must be assigned individually or through IdP groups
Key Benefits of Solution B:
Automated account creation via SCIM
Bulk permission management through IdP groups
Future-proof - new faculty added to the IdP group automatically get correct permissions
Consistent - ensures all faculty have appropriate admin rights
Reference: Slack's Enterprise Grid provisioning documentation and IdP group management
This approach provides the most scalable, manageable solution for a university environment with clear differentiation between student and faculty permissions.
Slack business+ plan and currently authenticates users via username and password.
Your company uses Google Workspace (formerly G Suite) for its identity provider (IdP).
Your security team would like to assign specific users or groups of users access to Slack
from your IdP (rule-based access).
How would you configure Slack to satisfy these requirements?
(Select the best answer.)
A. Configure Google Workspace Auth to enable users to log in via their Google Workspace credentials, and send out binding emails to existing users to connect their accounts with your IdP.
B. Set up Google Workspace SAML-based SSO in a new Slack workspace since your company already uses username and password to authenticate in its existing workspace.
C. Build a custom SAML connection with Slack in order to use the Google Workspace Id, and apply rule-based access.
D. Configure Google Workspace SAML-based SSO with Slack, and send out binding emails to existing users to connect their accounts with your IdP.
Explanation:
D. Configure Google Workspace SAML-based SSO with Slack, and send out binding emails to existing users to connect their accounts with your IdP.
To implement rule-based access using Google Workspace as your IdP, you configure SAML-based Single Sign-On (SSO) between Google Workspace and Slack. This allows users to authenticate through Google Workspace, leveraging group or user assignments defined in Google Workspace to control access. After setting up SSO, existing Slack users receive binding emails to link their Slack accounts with their IdP credentials, ensuring a smooth transition.
Why the other options are less suitable:
A. Configure Google Workspace Auth to enable users to log in via their Google Workspace credentials, and send out binding emails to existing users to connect their accounts with your IdP.
While Google Workspace Auth (OAuth) allows login via Google credentials, it does not provide the granular rule-based access control that SAML SSO offers.
B. Set up Google Workspace SAML-based SSO in a new Slack workspace since your company already uses username and password to authenticate in its existing workspace.
Creating a new workspace is unnecessary and disruptive. SAML SSO can be configured on the existing workspace without starting fresh.
C. Build a custom SAML connection with Slack in order to use the Google Workspace Id, and apply rule-based access.
Slack provides native support for Google Workspace SAML SSO, so building a custom SAML connection is not required.
Reference:
Slack Help Center – Set up SAML SSO with Google Workspace
Google Workspace Admin Help – Using SAML app
You're an Org Owner on the Slack Enterprise Grid plan responsible for posting new for
your entire organization to read. You want to limit posting permissions to admins only.
Sometimes the newsletters contain important action items, so it’s important that everyone
in your organization sees the message.
What is the best way to post your message? (Select the best answer)
A. Create a default org-wide channel called #announcements, and post your newsletter in this channel.
B. Send your newsletter to your team's channel and then copy/paste the link to your message to each team channel in your organization.
C. Send your newsletter in all of your department-specific channels to maximize visibility.
D. Send your newsletter to your organizations #general channel, and use the @channel notification
Explanation:
As an Org Owner in Slack Enterprise Grid, the best practice for company-wide communication is to use an org-wide announcement channel.
You can create an org-wide default channel (like #announcements) and configure it so that:
All members (including future new hires) are automatically added.
Posting permissions are restricted to admins only, preventing clutter and ensuring important posts stand out.
Everyone can still read the messages.
This ensures your newsletters and critical updates reach every member of the org while keeping the channel free of unnecessary chatter.
❌ Why the Other Options Are Incorrect:
B. Send your newsletter to your team’s channel and copy/paste the link...
✗ Very inefficient, error-prone, and does not guarantee org-wide reach.
C. Send your newsletter in all of your department-specific channels...
✗ Repetitive, time-consuming, and risks missing members who aren’t in a department channel.
D. Send your newsletter to #general and use @channel...
✗ On Enterprise Grid, #general is workspace-specific, not org-wide. Also, using @channel is noisy and discouraged for formal announcements.
📖 Reference:
Slack Help: Create and manage announcement channels
Slack Admin Guide: Default channels in Enterprise Grid
👉 Pro tip for the exam:
Whenever the question involves org-wide communications with limited posting permissions, the answer is usually an org-wide announcement channel.
Your company has just hired 10 new employees in the Los Angeles (LA) region. All 10 of
these employees are currently working remotely as there is no physical office. You need to
enable the LA employees as well as other employees potentially visiting LA from out of
town to discuss events, meetups and possible
volunteer opportunities.
What is the best way to facilitate this conversation?
(Select the best answer.)
A. Create a group direct message (OM) with the 10 employees in the LA region.
B. Create a Stack Connect channel with the 10 people aligned to the LA region.
C. Initiate direct messages (DMs) with each of the 10 employees aligned to the LA region.
D. Create a public channel (ex. #social-LA) and add the 10 people aligned to the LA Region
Explanation:
1. Why D is correct?
⇒ A public channel is the most scalable solution because:
→ It allows all LA-based employees (current and future) to easily find and join
→ Visiting employees can discover and participate in the conversation
→ Discussions remain discoverable and archived for reference
→ Enables organic growth of the community over time
⇒ The channel name (#social-LA) clearly indicates its purpose and location focus
2. Why A is incorrect?
→ A group DM is limited to only the initially added members (max 9 people in basic Slack)
→ New employees or visitors can't join the conversation
→ Lacks discoverability and doesn't scale well
3. Why B is incorrect?
→ Slack Connect is for collaborating with external organizations, not internal discussions
→ Would be unnecessarily complex for an internal use case
→ Doesn't provide the discoverability benefits of a public channel
4. Why C is incorrect?
→ Individual DMs don't facilitate group discussion
→ Would require maintaining 10 separate conversations
→ Impossible for visiting employees to participate
Best Practices:
→ Public channels are ideal for location-based or interest-based communities
→ Naming convention (#social-[location]) makes the channel purpose clear
→ Allows for organic discovery and participation
→ Scales automatically as new LA-based employees join the company
Reference:
Slack's Channel Naming Conventions best practices guide.
What would be the expected behavior if a team member in Enterprise Grid is added to an IdP (Identity Provider) group with auto-provisioning enabled to a workspace?
A. The member would be automatically added to the new workspace and would be unable to leave
B. The member would be notified that they have a new workspace that they can join and would be unable to dismiss it until they have joined the workspace.
C. There will be no changes to the member’s workspace list.
D. The member would be automatically added to the new workspace unless it is a hidden workspace.
Explanation:
Why D is correct?
With IdP (Identity Provider) group auto-provisioning enabled in Enterprise Grid:
➡️ Members are automatically added to workspaces associated with their IdP groups
➡️ This happens without manual intervention
➡️ The exception is hidden workspaces - these won't appear for users automatically
This is the standard behavior for IdP-based provisioning in Slack Enterprise Grid
Why A is incorrect?
While members are automatically added, they can still leave workspaces unless specifically restricted
Auto-provisioning doesn't make workspaces mandatory/unleavable by default
Why B is incorrect?
There is no persistent notification that can't be dismissed
The provisioning happens silently in the background
Why C is incorrect?
There will be changes to the member's workspace list (unless it's a hidden workspace)
Auto-provisioning specifically exists to automatically manage workspace membership
Reference:
Slack's documentation on Enterprise Grid provisioning confirms this auto-provisioning behavior
IdP group provisioning specifically mentions the automatic workspace assignment
Key takeaway:
IdP group auto-provisioning automatically manages workspace membership in Enterprise Grid, with hidden workspaces being the only exception. This provides seamless access management at scale.
| Salesforce-Slack-Administrator Exam Questions - Home | Previous |
| Page 7 out of 40 Pages |