Salesforce Slack-Dev-201 - Salesforce Certified Slack Developer

Block Kit layouts are represented as structured JSON objects and arrays when interacting directly with Slack APIs. Each block is represented as an object containing a `type` field together with properties appropriate to that block. Multiple blocks are normally placed inside a `blocks` array in the visual order in which Slack should render them. For example, a section block can contain a text composition object and an accessory such as a button. Slack's Block Kit documentation explicitly describes application interfaces as specially structured JSON. Language SDKs and Bolt frameworks may provide native-language objects, classes, or dictionaries that make construction more convenient, but those structures ultimately correspond to Slack's JSON payload representation. XML, YAML, and CSV are not the API representation used for Block Kit layouts. Therefore, C is correct.

Slack's standard Bolt quickstart supports starter projects for Python and JavaScript. The Slack CLI workflow lets a developer create a sample application using Bolt for Python or Bolt for JavaScript and then run that project in a development workspace. Both frameworks provide higher-level abstractions for common Slack application patterns, including event listeners, interactive actions, Web API clients, acknowledgments, and context-aware utilities. Slack also maintains Bolt for Java as an official framework, but the particular starter-template choice described by the standard quickstart is Python or JavaScript. Ruby, Go, C#, PHP, Rust, and Swift are not the two out-of-the-box starter choices represented in this question. Therefore, B correctly identifies Python and JavaScript as the standard Bolt starter-template languages in the Slack CLI quickstart.

The `say()` utility is commonly injected into Bolt listener functions to send a message back into a Slack conversation. In Bolt for Python, Slack demonstrates listener functions such as `def message_hello(message, say):`, where calling `say()` sends a message to the conversation in which the triggering event occurred. The helper abstracts the underlying `chat.postMessage` operation and automatically uses relevant conversation context, although developers can also explicitly specify a channel when required. `reply()` and `send()` are not standard injected Bolt listener utilities for this purpose, while `respond_to()` is not a documented Bolt listener parameter. Slack's Bolt framework intentionally provides context-aware utilities such as `say`, `ack`, `respond`, and `client` to simplify common interaction patterns. Therefore, option C correctly identifies the standard reply helper used by Bolt listeners.

A Slack application distributed across multiple independent workspaces must implement an OAuth installation flow. Slack explicitly states that enabling installation on other workspaces allows the application to generate access tokens for each workspace and applicable user authorization. Bolt's current OAuth documentation likewise explains that each app installation issues unique access tokens and installation information that the application must store securely and retrieve when processing requests. This is fundamentally different from a single-workspace application, which can receive one access token through direct installation without implementing the full distributed OAuth flow. Independent workspaces do not normally share one universal token. Organization-wide Enterprise installations are a distinct model and can use an organization-level authorization, but that does not invalidate the standard multi-workspace distribution behavior tested here. Therefore, A is correct.

Slack's current quickstart recommends using a developer sandbox when a developer does not already have a suitable Slack workspace for application development. A developer sandbox provides an isolated environment where an app can be installed, tested, and iterated without disrupting a production workspace. Slack CLI includes sandbox-related tooling, and the quickstart treats the sandbox as the preferred development environment for users who lack an existing workspace. A paid Slack plan, Enterprise Grid organization, or verified domain is not a prerequisite simply to begin a Slack CLI project. Strictly speaking, Slack documentation frames the sandbox as the recommended development workspace rather than a universal technical requirement in every circumstance; however, among the supplied choices, B is unequivocally the intended and correct answer.

A Slack app manifest is a reusable, declarative representation of an application's configuration. Slack describes manifests as portable configurations that can define major application settings, including display information, features, OAuth scopes, event subscriptions, interactivity settings, and other platform capabilities. A manifest can be used to create, configure, copy, and reproduce Slack applications without manually re-entering every setting through the app-management interface. This is particularly useful for teams maintaining multiple environments or applications with similar configurations. Manifests can also be stored in source control so collaborators can review and track configuration changes alongside application code. They are unrelated to billing invoices, API error logs, or Slack user permission groups. Therefore, option B accurately captures both the declarative nature and primary purpose of a Slack app manifest.

Slack's documented macOS and Linux installation method uses the official shell installer hosted on Slack's downloads domain. The command `curl -fsSL https://downloads.slack-edge.com/slack-cli/install.sh | bash` retrieves the installer securely and runs it through Bash, installing the Slack CLI and making the `slack` command available for development. Slack's current CLI installation documentation presents this command as the supported installation path for macOS and Linux. The alternatives do not represent the official installation command in the Slack Developer documentation: Slack CLI is not installed through the listed npm or pip commands, and `brew install slack` does not correspond to Slack's documented CLI installer. Therefore, option B is the verified installation command for the environments named in the question.

When a Bolt project is being developed locally through the current Slack CLI, `slack run` can watch application files and automatically restart the local application development server when supported source files change. Slack documents this behavior for Bolt for Python and Bolt for JavaScript projects. Python projects normally watch `.py` files, while JavaScript projects watch `.js` files unless the developer customizes the watch configuration. This live-reload capability shortens the development cycle because developers can modify application logic and have the running process restarted without manually stopping and relaunching it after every edit. The Slack workspace itself is not restarted, the user's browser is unaffected, and OAuth tokens are not regenerated merely because source code changes. Therefore, B is correct.

users.info provides the information required for both localization dimensions. Slack's user object contains timezone properties including tz, tz_label, and tz_offset. These values allow an application to schedule or render time-sensitive functionality according to the user's configured timezone rather than assuming the server's timezone or attempting to derive timezone information from HTTP headers. For language localization, users.info supports the include_locale=true parameter. When requested, Slack can include the user's locale, represented by an IETF language code. The app can then select translated strings and culturally appropriate presentation based on that locale. users.profile.get is intended for retrieving profile information and custom profile fields; it is not the preferred mechanism described by Slack for this combined localization requirement. HTTP request headers are also inappropriate for determining the Slack user's configured timezone because they represent network/request metadata rather than the user's Slack preference. Accordingly, D combines the appropriate API method with the two relevant user attributes. In implementation, the developer must remember to request locale explicitly using include_locale=true. This aligns with Design a Great User Experience, especially internationalization, localization, time-zone awareness, and tailoring application behavior to the individual Slack user.

The `slack run` command starts a Slack app in the local development environment and supports the install-and-test workflow against a selected workspace. Slack CLI uses the project's configuration to run the application locally, and current development tooling can watch supported source files and restart the running process when code changes. This enables an iterative development cycle in which the developer edits code, runs or reloads the local app, and immediately tests behavior inside Slack. `slack deploy` serves a different lifecycle purpose for supported hosted applications, while `slack start` and `slack serve` are not the standard commands documented for this workflow. Consequently, B is correct: `slack run` is the command Slack's quickstarts use to run the application locally and make it available for live workspace testing.