Slack-Dev-201 Exam Dumps - Salesforce Certified Slack Developer

Message shortcuts operate in the contextual action menu of an existing Slack message. Slack's official shortcut documentation specifies that message shortcuts appear in the context menus of non-ephemeral messages. Therefore, an ephemeral message cannot serve as the source message for a message shortcut, making B correct. This restriction follows from the underlying interaction model. Message shortcuts preserve context from the source message so an application can perform an action based on that message—for example, creating a ticket, escalating an incident, or sending content to an external system. Ephemeral messages have restricted visibility and lifecycle behavior and are excluded from this shortcut surface. Option D is incorrect because every shortcut invocation must be acknowledged promptly, regardless of how many shortcuts the app defines. Current Slack UX guidance requires shortcut requests to be acknowledged with an HTTP 200 response within three seconds. Option C is not a general rule; follow-up notification mechanics depend on the interaction payload and workflow. A's fixed limit of three message shortcuts is not the applicable platform rule represented here. This belongs to Design the Interactive Flow of Your App, particularly message shortcuts and contextual interactions.

Slack distinguishes between a development application installed only in its associated workspace and an application intended for installation across multiple workspaces. For a single-workspace application, Slack allows installation directly through the application's configuration without requiring the developer to implement a complete OAuth installation flow. Once an application is distributed to other workspaces, however, each installation must be explicitly authorized. Slack therefore requires the application to implement the OAuth 2.0 authorization-code flow and store the resulting installation information, including the applicable access tokens. OAuth is not required merely because an application has slash commands or a bot user. Those features require appropriate scopes and application configuration, but they do not independently dictate multi-workspace OAuth installation. OAuth is also not simply an optional additional security layer; it is Slack's authorization mechanism for obtaining workspace-specific authorization during distributed installation. The application typically sends the installer to Slack's authorization endpoint, receives a temporary authorization code through its configured redirect URI, exchanges that code through oauth.v2.access, and securely stores the resulting installation credentials. Therefore, C is correct and maps directly to Distribute Your App, particularly multi-workspace installation and OAuth-based authorization.

Under Slack's current SCIM documentation, Org Owner is the valid role for installing a SCIM application in an Enterprise organization. Slack requires an OAuth token carrying the admin scope for SCIM operations. Both Org Owners and Org Admins may subsequently use SCIM functionality to modify users, provided the token-generating account retains sufficient privileges. However, Slack explicitly distinguishes token usage from application installation: only an Org Owner can install the SCIM app on an Enterprise organization. Therefore, the supplied question is structurally defective because it instructs the candidate to “Choose 2 options,” while current official Slack SCIM requirements yield only one correct choice from the available options: D. An App Collaborator is an application-development role and does not confer Enterprise administration authority. Apps Admin and Moderator likewise do not satisfy SCIM installation requirements. Org Admin is relevant to SCIM administration and certain admin.* APIs, but is not sufficient for installing the SCIM application itself. The source bank marks C and D; that key should be corrected. This belongs to APIs for Managing Your Slack, particularly SCIM provisioning, administrative authorization, and Enterprise organization role requirements.

Option D accurately reflects Slack Connect behavior. Slack's official developer guidance explicitly states that messages sent through an incoming webhook into a Slack Connect channel are visible to all members of that shared channel, including users participating from external organizations. Option A is incorrect because the Events API can deliver events generated by external users participating in Slack Connect channels. Developers must therefore design applications to recognize that the actor may belong to another workspace. Option B is also incorrect: Slack specifically documents that shared channels do not cause duplicate event callbacks merely because the channel spans multiple workspaces. Developers should instead inspect authorization information in event payloads to determine where the application has authorization. Option C is overly broad. Incoming webhooks can send direct messages only under specific installation-team constraints; they cannot simply DM every external participant in a shared channel. Slack Connect therefore changes assumptions about workspace ownership, user identities, channel membership, and application authorization. Applications must distinguish the workspace where the app is installed from external workspaces represented in the shared conversation. This question belongs to Apps in the Slack Platform, particularly Slack Connect architecture and app behavior in externally shared channels.

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.