SLACK-ADMINISTRATOR practice question 25 of 30

[Integration and Automation] Slack is on the Business+ plan and currently authenticates users via username and password. Your company uses Google…

Full set: 210 questions

[Integration and Automation] Slack is on the Business+ plan and currently authenticates users via username and password. Your company uses Google Workspace (formerly G Suite) as 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 options
A:

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:

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:

C. Build a custom SAML connection with Slack in order to use the Google Workspace Id, and apply rule-based access.

D:

D. Configure Google Workspace SAML-based SSO with Slack, and send out binding emails to existing users to connect their accounts with your IdP.

Correct answer
Correct Answer:
D. 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

The correct procedure is to configure SAML-based Single Sign-On (SSO) using Google Workspace as the identity provider (IdP). This allows the security team to manage access to Slack from the Google Workspace Admin console, assigning the application to specific users or groups (rule-based access). For the existing users who authenticate with a username and password, the administrator must send "binding emails." This allows users to link their existing Slack accounts to their Google SSO credentials, ensuring a seamless transition without creating duplicate accounts.

Why Incorrect

A. "Google Workspace Auth" refers to OAuth 2.0 ("Sign in with Google"), which does not offer the same level of administrative control as SAML SSO.
B. Creating a new workspace is disruptive and unnecessary. SSO can and should be configured for the existing workspace to retain history and continuity.
C. Slack provides a standard, pre-built application for Google Workspace SAML. Building a custom connection is not required and is overly complex.

References

1. Slack Help Center, "Set up SAML single sign-on with Google". This guide details the steps to "Configure Google Workspace SAML-based SSO with Slack."

2. Slack Help Center, "Guide to single sign-on settings". This article explains the process for migrating existing members, stating: "After you've enabled SSO, members will need to bind their accounts... Slack will send them an email with a link to do so."

Scroll to Top