The best recommendation is B . For daily Agile syncs in a remote environment, Slack should reduce repetitive manual coordination and move routine updates into the channel where the team already collaborates. A Workflow Builder template can automatically prompt team members to provide updates at the right time, standardize the format of responses, and keep progress visible to the whole team. This is more scalable and more productive than relying on a manager to ask for updates manually. Option A is directionally useful, but it lacks automation and consistency. Option C may be useful if the team already has a project-management tool that should be integrated, but the question asks for a Slack feature that improves the sync process itself. Option D keeps the team in a synchronous meeting pattern and does not solve the productivity problem as effectively as automated asynchronous updates. Workflow Builder is the strongest Slack-native answer because it supports repeatable, channel-based Agile communication.

Reference topic: Channel Strategy — Agile standups, Workflow Builder, asynchronous updates, project channels, and remote team productivity.

==========

The best answer is to host three sessions throughout the launch week to accommodate the company’s geographic spread. A live enablement plan must match the employee population, launch timing, and working time zones. Since the customer has users in San Francisco, New York, and London, one fixed session time creates an avoidable accessibility problem. Option C supports a tailored training experience because each regional audience can attend during reasonable working hours and ask questions relevant to their local usage patterns. Option A creates an uneven experience by training only one group before launch and delaying the others. Option B repeats the same session weekly but does not address regional time-zone needs. Option D trains before users can experience the live Slack environment, which can reduce relevance and retention. The Slack Consultant exam outline includes Learning and Enablement as a core domain, and the official prep trailmix separates enablement as a dedicated consultant workshop area.

Reference topic: Learning and Enablement — launch training, global user readiness, live training design, and adoption planning.

==========

The correct recommendation is to add the custom profile field directly from the org admin dashboard and publish the change. The requirement is simple: all members should be able to add their favorite dessert in their Slack profile. This is not an identity-provider-driven attribute and does not require SCIM provisioning. SCIM-managed fields are appropriate for controlled identity attributes such as title, department, manager, or other directory-owned values that should be synchronized from the identity provider. “Favorite Dessert” is a user profile enrichment field, not a controlled identity field. Option A is incorrect because updating from SCIM would make the field dependent on an external identity source. Option B is incorrect because “update from API” is not the right administrative setup for this ordinary profile field use case. Option C starts in the wrong place because the field does not need to originate in the IDP. Option D correctly uses Slack profile configuration at the org level and publishes the field so it becomes available to members.

Reference topic: Policies and Settings — profile configuration, custom profile fields, SCIM-managed fields, and org-level profile governance.

==========