Free Salesforce Slack Developer Practice Test Questions

Explanation:

The question describes an HR team that wants to send newsletters regularly to specific regional Slack channels but cannot automate the process themselves. The question asks how Block Kit Builder can help them. Block Kit Builder is a  visual prototyping tool provided by Slack that lets users drag and drop Block Kit elements (sections, dividers, images, buttons, inputs, and more) into a layout and see a live preview of how the message will look in Slack. As users build the message, the tool generates the corresponding  JSON payload in real time, which can then be copied and used in an app or pasted into a message-sending tool. This makes it significantly easier for non-developers, like an HR team, to  design and prepare a message before it is actually sent to a channel, without needing to write code or hand-craft JSON from scratch.

❌ Why Other Options Are Incorrect:

A. It lets you save and organize the message templates you use most often.
– This is false. Block Kit Builder does not provide a template library or save/organize feature; users typically copy the generated JSON and store it elsewhere.

C. It helps you test your message interactivity flows from end-to-end.
– This is false. Block Kit Builder previews the visual layout of blocks, but it does not execute or test end-to-end interactivity flows such as button clicks triggering app logic.

D. It can automatically convert a word processor document into Block Kit without knowledge of JSON.
– This is false. Block Kit Builder requires users to assemble blocks manually (or paste existing JSON); it does not import or convert word processor documents automatically.

📚 References:

Slack API Block Kit Builder documentation – Describes the tool as a visual prototyping environment for designing and previewing Block Kit messages while generating JSON.

Explanation:

The question asks about the purpose of the Slack MCP plugin mentioned in the developer docs. MCP stands for Model Context Protocol, an open standard that allows AI agents and LLM-powered tools to connect to external services and data sources in a structured way. The Slack MCP plugin exists to expose Slack's developer capabilities to these agentic tools, enabling agent-assisted development workflows. In practice, this means an AI coding assistant or agent can interact with Slack's platform — for example, to help scaffold apps, look up API methods, manage app configuration, or assist with building and deploying Slack apps — through the standardized MCP interface rather than through manual, ad-hoc integrations. .

❌ Why Other Options Are Incorrect:

B. To manage billing
– This is false. Billing and workspace administration are handled through Slack's admin and billing interfaces, not through an MCP developer plugin.

C. To replace the Slack CLI
– This is false. The Slack CLI remains the official tool for app development, and the MCP plugin complements rather than replaces it.

D. To handle OAuth exclusively
– This is false. While OAuth and authentication may be involved when an agent connects, the plugin's broader purpose is enabling agent-assisted development, not handling OAuth exclusively.

📚 References:

Slack Developer documentation on the Slack MCP plugin – Describes the Model Context Protocol integration as a way to enable AI agents and assistants to work with Slack's developer platform.

Explanation:

The question asks where a developer should look first to start building an AI agent for Slack. Among the four options, docs.slack.dev/ai/agent-quickstart is the only one that is a developer documentation resource specifically dedicated to building AI agents for Slack. The page is titled "Quickstart: Creating a Slack agent" and walks a developer through the entire process: installing the Slack CLI, authenticating with a workspace, scaffolding a project from the Support Agent sample app (Casey), choosing an agent framework (Claude Agent SDK, OpenAI Agents SDK, or Pydantic AI), configuring environment credentials, and running the app with slack run. This is exactly the "look first" destination for someone beginning agent development — it combines setup instructions, framework guidance, and next-step resources like the Slack MCP Server integration in one place.

Why Other Options Are Incorrect:

B. slack.com/pricing – This is Slack's pricing and plan-comparison page. It covers subscription tiers, feature limits, billing, and FAQs, not how to build an AI agent.

C. api.slack.com/legal – This is Slack's terms and policies page. It contains legal notices and cookie preferences, offering no developer or agent-building guidance.

D. app.slack.com/marketplace – This is the Slack App Marketplace for finding and installing existing apps. It is aimed at end users, not developers starting an agent project.

📚 References:

Slack Developer Docs, "Quickstart: Creating a Slack agent" – Provides step-by-step instructions for building an AI-powered Slack agent using the Slack CLI, Bolt, and supported agent frameworks (Claude Agent SDK, OpenAI Agents SDK, Pydantic AI).

Explanation:

The question asks about the relationship between Bolt and the Node/Python/Java Slack SDKs. Bolt is a framework that is built on top of the underlying Slack SDKs for each language, providing higher-level abstractions that make it faster and simpler to build Slack apps. In other words, the SDKs handle the low-level details of communicating with Slack's APIs — constructing HTTP requests, managing tokens, handling WebSocket connections for Socket Mode, parsing responses, and so on — while Bolt wraps those SDKs with an ergonomic, event-driven programming model. This layered design means a Bolt developer writes listeners like app.command(), app.action(), app.view(), and app.event() instead of manually handling raw HTTP requests and payload parsing.

❌ Why Other Options Are Incorrect:

A. They are unrelated products – This is false. Bolt is explicitly built on top of the Slack SDKs and depends on them at runtime; they are tightly related, not independent.

C. The SDKs replace Bolt entirely – This is false. The SDKs and Bolt serve different layers. The SDKs are the foundation; Bolt is the higher-level framework layered above them. Neither replaces the other.

D. Bolt only works without any SDK installed – This is false. Bolt requires the underlying SDK to function — for example, Bolt for Python installs and uses slack_sdk, and Bolt for JavaScript uses the Node Slack SDK packages. Bolt cannot operate without its SDK dependency.

📚 References:

Bolt for JavaScript documentation – States that Bolt is built on top of the Slack SDK for Node, using packages such as @slack/web-api and @slack/socket-mode.

Explanation

Socket Mode allows a Slack app to receive events and interactive payloads over a WebSocket connection instead of a public HTTP endpoint. When the app starts and calls apps.connections.open, Slack returns a WebSocket URL that is unique to that session — it is not a fixed or permanent address. Because the URL is generated fresh each time the app connects (and can change on reconnect), it is non-static and is created dynamically as the app is running. This makes option B the correct answer.

Why the other options are incorrect:

A. Socket Mode listens to a static WebSocket URL that is created dynamically as the app is running – The phrase "static WebSocket URL" is contradictory and incorrect. A static URL implies a fixed, unchanging endpoint, but Socket Mode URLs are unique per session and are not reused as a permanent address.

C. Socket Mode listens to a non-static WebSocket URL that is created at runtime – While "non-static" and "created at runtime" are both accurate descriptions, this option is incomplete compared to option B. The official Slack documentation emphasizes that the WebSocket URL is created dynamically while the app is running, and the wording in option B aligns more precisely with the documented behavior of the apps.connections.open flow.

D. Socket Mode listens to a static WebSocket URL that is created at runtime – This is incorrect because it combines two contradictory ideas. A URL cannot be both "static" (fixed and unchanging) and "created at runtime" in the way Socket Mode operates. Socket Mode URLs are non-static and session-specific.

Reference:

Slack Developer Documentation— Socket Mode overview, describing how apps call apps.connections.open to obtain a WebSocket URL and how that URL is dynamically generated per session.