Explanation:

✅ Correct Options

A. Your delivery company has multiple workspaces in its Slack Enterprise Grid plan for each of its subsidiaries, and you need to be able to assign users to specific workspaces.
Correct. SCIM integrates with identity providers (like Okta, Azure AD, etc.) and can automatically assign users to the right workspaces based on attributes like department or location. This is efficient in multi-workspace orgs where centralized automation reduces admin burden.

E. Your environmental services company plans to launch Slack to all employees in a single day and sunset its former communication platform.
Correct. SCIM supports bulk provisioning, allowing thousands of accounts to be created at once. This is ideal for big-bang rollouts where speed and automation are critical. Without SCIM, manual onboarding would be slow and error-prone.

❌ Incorrect Options

B. Your pet food company works closely with a packaging supplier, and you want all employees of the companies to communicate seamlessly in Slack.
Not correct. SCIM is for internal user lifecycle management, not external partners. For external collaboration, the solution is Slack Connect, not provisioning employees of another company.

C. You need to preserve all users' apps and integrations (bot users, slash commands, incoming webhooks, etc.) when they are deprovisioned.
Not correct. SCIM handles user account lifecycle (provisioning/deprovisioning), but does not preserve integrations or bots after deactivation. That requires separate configuration or re-assignment.

D. You are the Slack admin for a multinational networking corporation and want users to have Slack accounts only if they plan to use the accounts.
Not correct. SCIM automatically provisions accounts for all users in your identity provider, whether they plan to use them or not. This scenario suggests a manual or request-based system, not SCIM.

📖 Reference: Slack Help – Manage members with SCIM provisioning

Explanation:

✅ Correct Option:
A. Org Owners and Org Admins decide who can manage multi-workspace channels in this situation.
Correct. Multi-workspace channels are managed at the Enterprise level, since they impact multiple workspaces. Only Org Owners or Org Admins can grant the permissions for Workspace Owners like Clint to manage these channels. This prevents accidental organization-wide changes by local admins who may not have visibility into how shared channels affect the rest of the company.

❌ Incorrect Options:

B. Only Org Owners can manage multi-workspace channels.
Not correct. Org Owners are the highest authority, but Org Admins also share responsibility for many organization-wide settings, including multi-workspace channels. Saying only Org Owners ignores the valid authority Org Admins have in this area.

C. The Sales Workspace Primary Owner can give multi-workspace channel permissions to Clint.
Not correct. Even though Primary Workspace Owners can grant permissions within their workspace, they cannot grant organization-level permissions like multi-workspace channel management. That requires intervention from the Grid-level team (Org Admins/Owners).

D. A Workspace Owner, who already has multi-workspace channel permissions, can give them to Clint.
Not correct. Permissions are not transferable peer-to-peer between Workspace Owners. These roles are centrally managed at the organization level, meaning Clint must receive approval directly from Org Owners or Org Admins.

📖 Reference: Slack Help – Manage multi-workspace channels

Explanation:

A. True (CORRECT ANSWER)
Claiming domains ensures all workspaces created under those domains automatically inherit the Enterprise Grid's configured policies for security, compliance, and data governance across the entire organization.

B. False Incorrect because domain claiming is precisely how Slack enforces that all workspaces under an enterprise's domains comply with the Grid's centralized policy configurations and admin controls.

Explanation:

✅ Correct Option:

A. Delegate a Workspace Admin from each business unit to handle everyday tasks, such as member requests.
This is correct because Enterprise Grid is designed for distributed administration. Org Owners manage Slack at the strategic, organization-wide level, while Workspace Admins manage local, everyday operations like adding members, handling channel requests, or approving apps. This reflects how different business units operate independently, while still staying aligned under Grid-wide governance.

❌ Incorrect Options:

B. Delegate an Org Admin from each business unit to handle everyday tasks, such as member requests.
Incorrect because Org Admins have too much authority for routine work like member requests. Org Admins can change policies or manage multiple workspaces, which doesn’t reflect the decentralized, unit-specific model the company is aiming for.

C. Create a multi-workspace channel for selected members to manage all admin requests for the organization.
Incorrect because creating a multi-workspace channel for admin requests is just a communication tool, not an administrative delegation method. It doesn’t solve the need for localized authority per workspace.

D. Delegate an Org Owner from each business to handle everyday tasks, such as member requests.
Incorrect because Org Owner is the highest possible role, reserved for a very limited number of individuals. Assigning multiple Org Owners just for handling simple admin tasks like user requests is excessive and risky for security.

📖 Reference: Slack Help – Roles and permissions

Explanation:

✅ Correct Option
C. Manage single sign-on (SSO) settings.
This is correct because SSO is an organization-wide authentication setting that impacts all workspaces within the Enterprise Grid. Only Org Owners have the authority to configure or modify these centralized identity and security policies, since they govern how every member logs in and accesses Slack. Workspace Owners, while powerful within their workspace, do not have jurisdiction over authentication systems that span across the entire organization.

❌ Incorrect Options

A. Set message retention policies.
This is incorrect because Workspace Owners can set retention policies within their own workspace if permitted. While Org Owners can enforce org-wide retention rules, Workspace Owners retain limited but legitimate authority in this area. Therefore, it is not something uniquely restricted to Org Owners.

B. Reset all members' passwords.
This is incorrect because password resets are handled by the identity provider or by users themselves. Slack Org Owners don’t have a global button to reset everyone’s password, especially when SSO is enabled. This is not an Org Owner–only feature.

D. Turn on approved apps.
This is incorrect because app approval can be delegated. Both Org Admins and sometimes Workspace Owners (depending on settings) can manage which apps are available. It’s not a power limited exclusively to Org Owners.

📖 Reference:
Slack Connect guide: Work with external organizations