Salesforce-Slack-Administrator Exam Dumps : Salesforce Certified Slack Administrator (Slack-Admn-201)

Slack best practices recommend:

"Pre-approving key apps ensures fast adoption while restricting high-risk apps maintains security compliance."

Admin API (B) is more technical and unnecessary at launch. Individual requests (C) create friction. Pre-approving apps and restricting non-common ones (D) isn't optimal unless based on risk evaluation.

(Reference: Slack Administration Study Guide - App Management Best Practices)

===========

—

The scopes mentioned allow the following:

channels:write — allows the app to create, archive, or modify public channels.

chat:write:user — allows the app to send messages on behalf of a user.

According to Slack’s API documentation:

"channels:write grants permission to manage public channels, while chat:write:user grants permission to send messages as a user rather than as the app."

Uploading files would require the files:write scope, and accessing group DMs would require groups:read or groups:history, neither of which are mentioned.

(Reference: Slack Administration Study Guide - App Scopes and Permissions)

Slack’s SCIM API documentation states:

"SCIM provisioning can be used to sync user attributes, like department, title, and location, from an Identity Provider to Slack profiles."

Analytics API (A) and Custom Profile API (C) focus on reporting or manual updates, not syncing at scale. Manual field creation (D) does not automate the syncing.

(Reference: Slack Administration Study Guide - SCIM Attribute Syncing)

===========

—