Pre-Order Your Salesforce Certified Slack Consultant Slack-Con-201

The correct answer is Executive sponsor . The executive sponsor owns senior-level business accountability for the engagement. This role provides strategic direction, resolves escalations that exceed the authority of the project team, and makes or approves critical business decisions that affect scope, priorities, risk, adoption, and organizational alignment. Option B, product owner, may guide business requirements, backlog decisions, and day-to-day solution priorities, but that role does not usually carry the senior authority needed for executive escalations or cross-functional business decisions. Option C, communications lead, owns launch messaging and communication planning, not critical decision-making. Option D, Slack admin, handles administrative configuration, user support, policies, settings, and operational tasks in Slack, but admins do not normally provide executive direction to the project. In a properly governed Slack implementation, escalation paths and decision rights must be explicit. The executive sponsor is the role that gives the project authority, removes business blockers, and ensures the Slack launch remains tied to enterprise goals.

Reference topic: Delivery and Migration — project team roles, executive sponsorship, escalation ownership, decision authority, and implementation governance.

==========

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 correct answer is D . The requirement is to automatically sign users out of desktop and mobile Slack sessions every 30 days. Slack session duration is a security control, so it belongs under org security settings rather than SSO settings. The duration is configured in hours, and 30 days equals 720 hours. Option A uses the correct security-settings area but expresses the duration as calendar days rather than the tested configuration value. Option B and Option C are incorrect because they place the control under SSO settings, but the requirement concerns Slack session duration for desktop and mobile instances, not SSO configuration itself. The consultant must translate the business requirement into the correct administrative setting and format: org-level security setting plus 720-hour session duration. This supports the client’s security posture by limiting persistent sessions and requiring periodic reauthentication across Slack clients.

Reference topic: Policies and Settings — session duration, org security settings, reauthentication controls, Enterprise Grid security posture, and desktop/mobile session governance.

==========