Salesforce Updated Slack-Dev-201 Exam Questions and Answers by priya

App Home is the strongest primary surface because the requirement involves persistent management of structured, user-specific information. Employees must repeatedly return to the application to create, edit, and review timesheet data rather than perform only a single transient action. Slack defines App Home as a private one-to-one space between a user and an application. Its Home tab remains available in a predictable location and retains its interface until the application republishes or updates it. Slack specifically recommends App Home for personalized dashboards, task views, user-specific information, settings, and persistent application workflows. A timesheet application can therefore display the employee's current pay period, submitted entries, outstanding hours, approval status, and actions for adding or modifying records. Individual edit/create operations could subsequently open a modal, but the modal would be a supporting interaction surface rather than the application's principal workspace. Messages are better suited to notifications and conversational interactions. Threads organize message-based discussion and do not provide an appropriate persistent management dashboard. Therefore, A correctly follows Slack's surface-selection guidance. This question belongs to Design a Great User Experience, especially persistent personalized interfaces and selection of the appropriate Slack surface.

A Slack app initially created for one development workspace cannot simply be installed into unrelated workspaces. To support multi-workspace installation, the application must implement the Slack OAuth authorization flow and enable distribution. A key prerequisite is configuring an OAuth Redirect URL. After an installing user authorizes the requested scopes, Slack returns a temporary authorization code to this redirect URI. The application's server then exchanges that code using oauth.v2.access for installation credentials. Slack's official distribution documentation also requires the developer to enable application distribution from the app-management interface. Historically the setting is described as Activate Public Distribution; current documentation may refer more generally to app distribution or unlisted distribution. Marketplace publication is not required merely to make an application installable by other workspaces. An unlisted distributed application can be shared directly with selected customers through its installation flow. Option C contains a serious security defect because workspace and user IDs must not be hard-coded. Option D does not establish multi-workspace authorization. Therefore, A provides the minimum architecture required for cross-workspace installation. This maps directly to Distribute Your App, particularly OAuth, redirect URLs, and distributed installations.

Applications published in the Slack Marketplace must meet Slack's formal listing and review requirements. These requirements extend beyond functional API behavior and cover presentation, privacy, support, security, and overall user experience. Slack requires Marketplace listings to include high-quality visual presentation, including a recognizable, high-resolution application icon. The listing must also provide descriptive information explaining what the application does, which problems it solves, and how users interact with it inside Slack. Slack's current Marketplace guidelines separately define both short and long descriptions. Most importantly, Marketplace applications must provide a clearly accessible privacy policy explaining how third-party data is collected, used, retained, transferred, or deleted and how users can make privacy-related requests. A private single-workspace application does not undergo Slack Marketplace listing review. Merely implementing bot functionality does not trigger these listing requirements either. An unlisted publicly distributed app can be installed across workspaces using OAuth, but it is not automatically subject to the complete Marketplace listing presentation process. The original question uses the older term Slack App Directory. Slack's current official terminology is Slack Marketplace. This belongs to Distribute Your App, specifically Marketplace submission and listing requirements.

Slack explicitly requires an OAuth token containing the admin scope to access the SCIM API. Therefore, C is directly supported by the current SCIM documentation. For an Enterprise organization, Org Owners and Org Admins can perform SCIM operations after the app has been established, but Slack specifically states that only an Org Owner can install the SCIM app. That makes A insufficiently accurate as written if interpreted as independently establishing the SCIM integration. Slack also enforces privilege boundaries. A token generated from an Admin account can operate on members and other Admins with equal or lower privileges, but it cannot modify Owner accounts. Therefore B is false. SCIM requests must send the access token in an HTTP Authorization header using the Bearer scheme. Slack does not prescribe placing the SCIM credential in a URL query string; doing so would also be an inferior security practice because URLs are more likely to be logged by intermediaries. On Enterprise, the SCIM token must be obtained from installing the application at the organization level, not merely within one workspace. This question maps directly to APIs for Managing Your Slack, particularly SCIM authentication and Enterprise provisioning.