Salesforce Certified Slack Developer Exam Prep Questions

About the Salesforce Certified Slack Developer Credential

The Salesforce Certified Slack Developer certification highlights your ability to build powerful custom applications on the Slack platform. It demonstrates your knowledge of Slack APIs and your skill in planning, designing, and delivering effective Slack apps that drive collaboration and productivity.

Who Should Take This Exam

This certification is a great fit for developers who:

• Have hands-on experience creating Slack apps and working with Slack’s APIs.

• Understand Slack’s structure, app components, and JSON objects.

• Are comfortable with event-based API protocols (JSON over HTTP and WebSockets).

• Know at least one programming language (commonly Node.js, Python, or Java).

• Have experience developing and deploying web applications to cloud platforms.

While six months of practical experience building Slack apps is recommended, there are no formal prerequisites to sit for the exam.

Exam Details

• Format: 60 multiple-choice/multiple-select questions

• Time: 90 minutes

• Passing Score: 67%

• Exam Release Version: Summer ‘24

• Cost: USD 200 (retake fee: USD 100) + local taxes

• Delivery: Proctored exam, either online or at a testing center

• Materials: No reference materials allowed during the exam

Purpose of This Guide

This guide is here to help you prepare effectively for the Salesforce Certified Slack Developer exam. Inside, you’ll find the target audience, exam objectives, recommended preparation resources, and tips for exam success. Combining real-world experience with practice tests and study will give you the best chance of passing on your first attempt.

Exam Outline

The Salesforce Certified Slack Developer Exam measures a candidate’s knowledge and skills related to the following objectives.

Apps in the Slack Platform: 7%

• Recommend how to automate and enhance operations on a Slack workspace.

• Recommend when to use Slack’s different surfaces (user touchpoints including App home, modals, and messages) for a range of use cases.

• Identify when to set up a team to collaborate on a Slack app.

Design the Interactive Flow of Your App: 20%

• Build common workflows (business processes) and use cases for Slack apps.

• Recommend an app design that interacts effectively with Slack's architecture.

• Handle possible user entry points for an app's workflow.

• Recommend when to use different Slack components and features (such as incoming webhooks, slash commands, shortcuts, interactive components, and bots) for common use cases.

• Build a user interface (UI) for your app's surfaces using Block Kit.

Design Your Workflows: Spotlight on Slack's APIs: 13%

• Recommend when to implement Slack's different application programming interfaces (APIs) for different use cases.

• Implement the Web API in your app.

• Implement the Events API in your app.

• Discriminate between Socket Mode and HTTP-based event delivery.

• Differentiate between current Slack terms and legacy language in the APIs.

• Process rate limits throughout the Slack platform.

Design a Great User Experience: 8%

• Build a great user experience that aligns with Slack’s commitment to make work life simpler, more pleasant, and more productive.

Design for Security: 19%

• Design for security.

• Implement the OAuth installation flow.

• Request the appropriate scopes for your app's use case.

• Request the appropriate tokens for your app's use case.

• Identify the steps you could take to make your app communicate securely in Slack.

• Store and retrieve data and tokens safely.

Design for Scale: 9%

• Design your app to match the unique platform architecture, features, and roles of Enterprise Grid.

• Describe the characteristics of an Enterprise Grid Sandbox.

• Recommend when to add support for channels that are shared externally with Slack Connect.

Tools: 5%

• Recommend when to use sample code and external resources.

• Recommend when to use the Bolt development framework to build Slack apps.

• Explain the purpose and value of Block Kit Builder.

• List some use cases for Slack Developer Tools (SDT).

APIs for Managing Your Slack: 12%

• Recommend when to use an Admin API to automate a Slack workspace or org administration.

• Use the SCIM API to manage Slack users and user groups.

• Monitor workspace events with the Audit Logs API.

• Recommend when to use the Discovery API for data-loss prevention, compliance archiving, or eDiscovery.

• Identify the required user role to generate a token to use APIs to automate a Slack workspace or org administration.

Distribute Your App: 7%

• Examine why you would want to contain an app to a single workspace.

• Share an app with other workspaces.

• Differentiate between a single workspace app, a distributed app, and a published App Directory app.

• Explain the best practices, expectations, and processes to submit an app to the Slack Directory.