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

The correct answer is C. The pre-migration report specifically flags the issue under Duplicated and Illegal Usernames, so the immediate defect to resolve is the duplicated username. Because the same username exists in both migrating workspaces but the email addresses are different, Slack cannot treat the records as the same clean identity without addressing the username conflict. Changing one of the usernames removes the duplicate username condition before the migration proceeds. Option A is too destructive and could remove a legitimate user account. Option B is irrelevant because converting the user to a multi-channel guest does not resolve duplicate or illegal username status. Option D may be relevant to identity hygiene in other migration scenarios, especially when preventing duplicate users through SSO alignment, but the question’s report category is specifically username duplication. The consultant should distinguish between user identity matching and username validity. Here, the recommended remediation is to make the usernames unique so the migration report no longer flags the user under duplicated or illegal usernames.

The correct answer is A . The discovery finding tells you that Slack maturity is uneven across the organization. The IT department already uses Slack, so those users may understand channels, threads, reactions, search, notifications, apps, and basic etiquette. The rest of the organization, however, will be new to Slack and will require more foundational onboarding, communication guidance, and enablement. This affects deliverables because training, support resources, communications, channel strategy, and launch messaging must account for two populations: existing users and new users. Option B is unsupported because the scenario mentions IT only, not a marketing-specific support need. Option C is incorrect because org-wide channels can still be adopted; they may actually become important for launch communications. Option D is too rigid. Separate governance sessions are not required solely because maturity levels differ. The right consultant behavior is to tailor deliverables so experienced Slack users are not slowed down by overly basic material while new users are not overwhelmed by advanced assumptions.

==========

The correct answer is B . A security-focused discovery question should expose whether the client has different risk profiles across departments, roles, data types, or user populations. Asking whether some groups need more restrictive permissions or access than typical employees directly uncovers security and governance requirements that affect workspace access levels, private channel strategy, guest access, Slack Connect rules, app approvals, retention, DLP, eDiscovery, and administrative role design. Option A is useful for collaboration mapping, but it does not directly identify security concerns. Option C belongs to support-process discovery, not security discovery. Option D is relevant to external collaboration and Slack Connect governance, but it is narrower than the broader security requirement in the question. Security discovery must identify populations that require stronger controls, such as legal, finance, HR, executives, regulated teams, contractors, or teams handling confidential data. This answer gives the consultant the clearest path to designing appropriate policies, permissions, and access boundaries.

Reference topic: Discovery — security requirements gathering, restricted access groups, permission design, and governance-driven discovery.

==========