Slack recommends making help accessible where users naturally interact with an application. For conversational applications, Slack's onboarding guidance specifically recommends replying when users request help in the application's DM and responding appropriately when the app is @mentioned. An app mention often indicates that a user either intends to invoke the application or needs guidance, making B directly aligned with Slack's recommendations. The application's Home tab is also an appropriate persistent location for support information and interactive help controls. Current Slack Marketplace UX guidance explicitly recommends making help and support easily accessible as part of the application experience and specifically cites placing support information in the app Home tab. Because Home tabs support Block Kit interactivity, a help button can provide an obvious, reusable entry point to assistance, making C appropriate. A feedback workflow does not directly provide operational help. Message shortcuts are intended primarily for actions associated with an existing message rather than general application assistance. Sending users unsolicited DMs containing prominent external URLs is also less consistent with Slack's preference for helpful, contextual, non-spammy onboarding. This maps to Design a Great User Experience, covering onboarding, discoverability, App Home, and contextual support.

Slack Web API responses conventionally include a top-level Boolean `ok` property indicating whether the requested operation succeeded. A normal successful response contains `"ok": true` together with any method-specific data, such as a user object, channel information, timestamps, or other returned values. When an API operation fails, Slack generally returns `"ok": false` together with an `error` field identifying the failure condition. Slack explicitly advises callers to evaluate the `ok` value rather than assuming that a syntactically valid response represents success. For example, the official `users.info` method documentation shows a successful response containing `"ok": true` and an unsuccessful response containing `"ok": false`. Slack Web API operations do not normally return CSV files, redirects, or HTML documents as their standard JSON success response. Therefore, A is correct.

Slack's current architecture guidance explicitly favors HTTP Request URLs for production applications when Socket Mode is not required. WebSockets are stateful, which makes them more complex to scale horizontally and more susceptible to connection interruptions, network partitions, and transient disconnections. Slack describes Socket Mode as particularly convenient for local development, on-premises integrations, environments behind firewalls, or applications unable to receive inbound HTTP traffic. For maximum application-connectivity reliability, Slack recommends HTTP for production applications and advises developers to continue using HTTP request URLs when their deployment does not specifically require Socket Mode. Socket Mode also does not replace the Web API; applications commonly receive events over Socket Mode and then invoke Web API methods to perform actions. Therefore, B accurately reflects Slack's present production-scale guidance.

Block Kit Builder is Slack's visual prototyping environment for designing and previewing Block Kit layouts. It allows users to add, rearrange, and configure blocks while simultaneously reviewing the associated JSON representation and seeing how the completed layout will render. For the HR newsletter use case, the team can therefore construct and visually review a formatted message before the application or automation sends it to the required regional channel. Slack describes Block Kit Builder as a tool for choosing, configuring, arranging, and previewing blocks across Slack surfaces. Option A overstates its function: Block Kit Builder is not fundamentally a template-management repository for organizing recurring newsletters. Option C is also too broad. The builder can expose example interaction payloads and validate message composition, but it does not execute an application's complete backend interactivity workflow end-to-end. Option D is unsupported; it does not automatically convert arbitrary word-processing documents into production-ready Block Kit structures. Therefore, B accurately describes its intended role: prepare and preview the Slack UI/message composition before deployment. This belongs to Tools, specifically Block Kit Builder and visual prototyping of Slack application surfaces.

The `slack create` command is used to create a new Slack application project from a supported template. Slack CLI can prompt the developer to choose a starter project, or a template can be supplied directly, after which the command creates the local project directory and required project files. Slack's current quickstarts use `slack create` as the standard starting point for Bolt-based development in JavaScript or Python. This command is distinct from `slack run`, which executes the application locally, and from deployment or configuration commands used later in the lifecycle. `slack init`, `slack new`, and `slack bootstrap` are not the documented Slack CLI commands for scaffolding a new project. Therefore, option C correctly identifies the supported project-creation command.

An incoming webhook is a simple mechanism for sending messages from an external system into a predefined Slack destination. When an incoming webhook URL is created, Slack associates that URL with a specific user and a specific channel. Current documentation states explicitly that the generated URL is tied to one channel. The webhook therefore works particularly well when an external service has a straightforward requirement such as sending alerts, notifications, or status information into one predetermined channel. The integration makes an HTTP POST containing a JSON message payload to the webhook URL. Option A conflicts with the fundamental behavior of a single incoming webhook URL. To support multiple destinations, separate webhook URLs or more flexible Web API methods may be required. Option D is also incorrect because incoming webhooks intentionally provide less destination flexibility than methods such as chat.postMessage. Slack specifically notes that an incoming webhook cannot override its configured destination channel, username, or icon through the message payload. Consequently, C accurately represents the architectural reason for selecting an incoming webhook. This maps to Design Your Workflows: Spotlight on Slack's APIs, particularly choosing between webhooks and Web API messaging methods.

Slack's current Agent quickstart guides developers through creating an AI-powered Slack agent. The official quickstart uses a sample support agent named Casey and demonstrates building the application with the Slack CLI and Bolt frameworks while integrating supported AI agent frameworks such as the Claude Agent SDK, OpenAI Agents SDK, or Pydantic AI. The resulting agent can interact through direct messages, app mentions, App Home, modals, reactions, and threaded responses. Developers begin by installing the Slack CLI, authenticating with a workspace, and creating the agent project using the provided sample template. This is application-development guidance for Slack's AI agent platform, not billing, workspace theming, or Block Kit Builder extensions. Therefore, B precisely matches the purpose of the Agent quickstart.

The `slack login` command authenticates the Slack CLI with a development workspace. During this process, the CLI guides the developer through authorization so subsequent commands can operate in the selected Slack environment. This is a prerequisite for common development tasks such as creating, running, and installing a Slack app through the CLI. Slack's quickstart documentation explicitly instructs developers to run `slack login` after installing the CLI and before starting the app-development workflow. The other options are not the documented authentication command: `slack auth`, `slack connect`, and `slack workspace add` do not perform the standard CLI login flow described by Slack. Therefore, B is correct because `slack login` is the supported command for connecting and authenticating the Slack CLI to a workspace.

In Bolt for Python, `@app.message(...)` registers a listener for messages matching specified text or a regular-expression pattern. For example, `@app.message("hello")` can invoke a listener when an incoming message contains the expected text. Bolt handles the event routing and supplies useful listener arguments such as the message payload, `say`, `client`, and other context values. By contrast, `@app.event` is used to subscribe a listener to a specific Slack event type rather than to filter messages by text. `@app.listen` and `@app.on_message` are not the standard Bolt for Python decorators documented for this use case. Therefore, B is correct: `@app.message` is the framework feature specifically intended for listening to message content that matches a configured string or pattern.

A message posted to an authorized conversation is a standard example of activity that can generate an Events API notification. Slack provides specific message event subscriptions for different conversation types, including `message.channels`, `message.groups`, `message.im`, and `message.mpim`. The exact events an application receives depend on its subscribed event types, granted OAuth scopes, and access to the relevant conversation. Slack's own Events API walkthrough uses a message posted in a channel containing a bot as a canonical example: Slack sends the event to the application, the server acknowledges it, and application logic can then respond using a Web API method such as `chat.postMessage`. A user's local clock, browser-tab changes, and ordinary billing renewal are not Events API event triggers represented by these developer subscriptions. Therefore, A is correct.