Score Higher on Verified Slack-Con-201 | Salesforce Certified Slack Consultant Exam Questions with Answers

The correct access level is By Request . The legal workspace should be discoverable to all members of the Enterprise organization, but access should require approval because the workspace contains confidential legal conversations. “By Request” fits that exact requirement: members can see that the workspace exists and request to join, while the appropriate workspace owners or admins can approve only legal team members or authorized users. Option A, Open, is too permissive because any eligible member could join without approval. Option C, Hidden, is too restrictive because the client specifically wants all org members to see that the workspace exists. Option D, Invite Only, allows controlled membership but removes the self-service request mechanism and is not as aligned with the requirement that the workspace be visible. The consultant should always map workspace access level to sensitivity and discoverability. Confidential-but-visible workspaces generally fit the By Request model.

Reference topic: Grid Design — workspace access levels, confidential workspace design, discoverability, approval-based access, and Enterprise Grid workspace governance.

==========

The correct answer is D . The requirement is to automatically sign users out of desktop and mobile Slack sessions every 30 days. Slack session duration is a security control, so it belongs under org security settings rather than SSO settings. The duration is configured in hours, and 30 days equals 720 hours. Option A uses the correct security-settings area but expresses the duration as calendar days rather than the tested configuration value. Option B and Option C are incorrect because they place the control under SSO settings, but the requirement concerns Slack session duration for desktop and mobile instances, not SSO configuration itself. The consultant must translate the business requirement into the correct administrative setting and format: org-level security setting plus 720-hour session duration. This supports the client’s security posture by limiting persistent sessions and requiring periodic reauthentication across Slack clients.

Reference topic: Policies and Settings — session duration, org security settings, reauthentication controls, Enterprise Grid security posture, and desktop/mobile session governance.

==========

The correct answer is B . If the identity provider supports both SSO and SCIM, both should be configured before launch. SSO provides secure authentication and allows users to access Slack through the organization’s identity system. SCIM supports automated user provisioning and deprovisioning, which is essential for launch readiness, user lifecycle management, and administrative efficiency. Option A is incomplete because SSO alone handles authentication but does not automate provisioning. Option C delays SCIM until after launch, which creates avoidable manual work and may produce onboarding inconsistencies. Option D is also incomplete because SCIM provisioning without SSO does not fully satisfy secure login and access requirements. For a first-time Slack launch, identity configuration is not optional cleanup work; it is foundational launch infrastructure. Configuring both SSO and SCIM before launch gives admins control over who gets access, reduces manual invites, supports lifecycle governance, and prevents avoidable access issues during rollout.

==========