Slack modals are opened through the `views.open` Web API method using Bolt's built-in API client. After a shortcut, slash command, button click, or another qualifying interaction, Slack supplies a `trigger_id`. The application acknowledges the incoming interaction and promptly exchanges that trigger through `views.open` together with a valid modal view payload. In Bolt for JavaScript, this is commonly represented through the client's `views.open` interface; Bolt for Python exposes the corresponding `client.views_open()` method. The important platform primitive is therefore `views.open`, regardless of the language-specific SDK naming convention. A `trigger_id` must be used quickly because it has a short validity period. Neither `app.modal()` nor `app.popup()` nor `client.modal.show()` is Slack's documented method for opening modal views. Therefore, B is the correct answer.

A global shortcut is designed for exactly this entry-point requirement. Global shortcuts expose application functionality independently of a particular message or channel context, enabling users to launch an application's workflow from broadly accessible locations in Slack. Slack specifically describes global shortcuts as suitable for workflows that can operate without the context of an existing channel or message. After the shortcut is invoked, Slack sends the app an interaction payload containing a trigger_id. The application can acknowledge the invocation and use that trigger_id to open a modal. The modal can then present the required multi-question form. On submission, the application can process the captured fields, transmit the data to the backend system, and use Slack's messaging API to publish the appropriate information to #benefits-us. A message shortcut requires an existing message context, which this use case does not require. A reaction similarly depends on a message. An incoming webhook provides a mechanism for posting information into Slack but does not provide an application entry point for opening an interactive form. This is a direct example of Design the Interactive Flow of Your App, particularly selecting the correct user entry point and connecting shortcuts to modal workflows.

Slack recommends transmitting OAuth access tokens through the HTTP `Authorization` header using the Bearer authentication scheme. A typical request therefore includes a header such as `Authorization: Bearer xoxb-...`, where an `xoxb-` value represents a bot token. When using JSON request bodies for write methods, Slack explicitly requires the token to be transmitted as a bearer token in this header. Keeping credentials in headers also avoids exposing sensitive tokens through URLs, browser history, intermediary logs, or query-string processing. Slack does permit token transmission as an encoded POST body parameter in some cases, but the Authorization header is the preferred mechanism. `X-Slack-Token`, browser cookies, and the `Referer` header are not the documented authentication mechanisms for ordinary Slack Web API calls. Therefore, A is the verified answer.

Slack specifically recommends testing applications in an Enterprise organization sandbox because Enterprise environments introduce behaviors that cannot always be reproduced accurately in a standalone workspace. Slack's Developer Program provides fully featured Enterprise organization sandboxes specifically for development and testing. Applications must also account for workspace migration periods. During migration into an Enterprise organization, Web API and other platform interactions may temporarily become unavailable. Slack provides the grid_migration_started and grid_migration_finished Events API events so applications can detect this lifecycle transition. Official guidance recommends pausing relevant API/platform activity when migration begins and resuming it after migration finishes. Discarding an existing application is unnecessary because ordinary Slack applications can be adapted for Enterprise behavior. Polling channel IDs is not an appropriate migration strategy. Likewise, reinstalling applications solely to obtain new access tokens is not the fundamental requirement when a workspace becomes part of an Enterprise organization. The critical architectural principle is to test Enterprise-specific behavior and implement migration-aware event handling instead of assuming a standalone-workspace environment will remain stable throughout migration. This directly addresses Design for Scale, especially Enterprise organizations, migration resilience, and testing applications under Enterprise-specific conditions.

The Slack CLI is Slack's official command-line development tool for creating, running, and managing Slack app projects. It supports the standard local development workflow used in Slack's current quickstarts, including creating a project from a template, authenticating with a development workspace, running the app locally, and opening app configuration. The command-line workflow is integrated with supported Slack SDKs and Bolt starter projects, so developers can move from scaffolding to testing without manually assembling the entire project structure. The alternatives listed are not Slack's official app-development command-line tool: there is no standard npm create-slack or pip slack-init workflow, and Bolt Studio is not the CLI product. Therefore, A correctly identifies Slack CLI as the official tool for command-line app development.

A modal is a focused application surface that appears over the Slack interface and maintains the user's attention until it is submitted or dismissed. Slack describes modals as alert boxes, pop-ups, or dialog-style interfaces used for focused interactions. Applications commonly use them to collect structured information, present temporary details, configure settings, or guide a user through a task. Modal content is constructed using Block Kit blocks and interactive elements, including text inputs, select menus, buttons, and date pickers. Modals are typically opened after an explicit user interaction by calling `views.open` with a valid `trigger_id`. They are not scheduled background processes, authentication tokens, or organization-wide announcement mechanisms. Therefore, option B accurately describes the purpose and presentation model of a Slack modal.

The `divider` block is the Block Kit component specifically designed to create a visual horizontal separation between adjacent pieces of content. Slack describes it as a content divider comparable to an HTML horizontal rule, allowing developers to organize messages, modals, and Home tabs into clearly separated visual sections. Its JSON representation is intentionally simple and normally requires only `"type": "divider"`, although a `block_id` can optionally be supplied. The alternatives `separator`, `line`, and `rule` are not valid Slack Block Kit block types. Dividers should be used where visual grouping improves readability rather than as substitutes for meaningful content structure. Slack officially supports divider blocks across messages, modals, and Home tabs. Therefore, A is the verified answer.

Enterprise Grid is Slack's enterprise architecture for organizations that need centralized governance across multiple Slack workspaces. Workspaces can exist within one Enterprise organization while organization-level administrators manage identity, policies, applications, security, and other administrative functions across the broader environment. Slack's current Enterprise documentation continues to describe Enterprise Grid organizations as containing multiple workspaces, and migration tooling allows standalone workspaces to be incorporated into an Enterprise organization. Enterprise functionality also enables organization-level application installation, Admin APIs, centralized app-management policies, and other large-scale administrative capabilities. Enterprise Grid is therefore not a pricing utility, UI theme, or authentication token type. Among the available options, B correctly captures its architectural purpose as Slack's offering for large organizations operating multiple managed workspaces.

Slack's `admin.conversations.*` methods provide Enterprise administrators with programmatic control over channels across an organization. Official Slack documentation lists methods for creating, deleting, archiving, unarchiving, and renaming channels, inviting users, searching channels, and changing channel visibility. For example, `admin.conversations.rename` can rename public or private channels, `admin.conversations.invite` adds users to channels, and `admin.conversations.search` searches conversations across an Enterprise organization. These methods require appropriate Admin API scopes and organization-level authorization and may additionally depend on the installing administrator's Channel Management permissions. They do not compile Bolt application code, construct Block Kit layouts, or issue app-level tokens; those functions belong to entirely different parts of Slack's developer platform. Therefore, A accurately represents the administrative channel-management capabilities of this API family.

Option B provides the strongest Slack-platform architecture because the process requires individualized status tracking, integration with an external system of record, recurring reminders, and escalation when employees remain noncompliant. Slack apps are specifically intended to automate tasks and connect Slack with external business systems. The application can determine each employee's compliance state externally and send targeted Slack notifications only where action is required. A quarterly announcement workflow is insufficient because it treats every employee identically and cannot distinguish completed from outstanding obligations. It also lacks an escalation mechanism. Option C unnecessarily places compliance training and acceptance inside Slack even though the scenario identifies an external system of record. That creates duplicated state and introduces additional governance concerns around which system represents the authoritative acceptance record. Slack's application-design guidance also cautions against noisy broad notifications. Targeted communication is preferable where a service concerns an individual user, and manager escalation can be generated only for unresolved cases. This maps to Apps in the Slack Platform, particularly recommending how Slack applications can automate organizational operations and integrate existing business processes with external systems.