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.

The correct recommendation is Monthly . Guest and channel cleanup is an operational governance activity, not a one-time launch task. Slack environments evolve quickly: projects end, external partners change, guest access expires, channels become inactive, and sensitive collaboration spaces may no longer require the same membership. A monthly cleanup cadence is frequent enough to reduce access risk and channel clutter without creating excessive administrative burden. Option A is weak because ad hoc cleanup is reactive and usually happens only after a problem occurs. Option B may be too frequent for most organizations and can create unnecessary admin overhead unless the environment is unusually high-risk. Option D is not frequent enough; annual reviews allow stale guest access and unused channels to accumulate for too long. The point of guest and channel cleanup is to keep collaboration intentional, secure, and manageable. This cadence should be owned through the governance structure and executed by the appropriate admin or owner roles.
Reference topic: Governance Structure (Owner and Admin Roles) - operational governance cadence, guest lifecycle management, channel cleanup, and administrative accountability.

The correct answer is D . An Enterprise Grid organization can have only one Org Primary Owner . This is the highest-level ownership role for the Enterprise organization and is distinct from Org Owners, Org Admins, Workspace Owners, and Workspace Admins. The number of workspaces in the grid does not change the number of Org Primary Owners. In this scenario, the organization has four workspaces - Social, Finance, Marketing, and Operations - but that does not mean there are four Org Primary Owners. Option A incorrectly maps one Org Primary Owner per workspace. Option B has no basis in the role model. Option C is wrong because the organization cannot define an arbitrary number of Org Primary Owners. The Primary Owner concept exists to provide a single ultimate accountable owner for the Enterprise organization, while additional administrative responsibility can be delegated through Org Owner, Org Admin, Workspace Owner, and Workspace Admin roles.
Reference topic: Governance Structure (Owner and Admin Roles) - Org Primary Owner, Enterprise Grid role hierarchy, ownership accountability, and admin delegation.

The correct answer is B . After an Enterprise Grid migration, users may belong to different workspaces inside the same grid. A public channel is discoverable only to members who have access to the workspace where that channel exists, unless it is made available as a multi-workspace or org-wide channel. In this scenario, some users can find and join the training channel, while others cannot. That pattern strongly indicates the channel itself is public, but it lives in a workspace that not all attendees belong to. Option A is possible in isolated cases, but it would not explain a consistent split across attendees. Option C is irrelevant because Slack Connect is used for collaboration with external organizations, not internal training-channel discovery.
Option D would prevent users from joining through search unless invited, but it would generally affect all attendees who were not invited. The training setup should either invite all participants or place the training channel in a workspace accessible to the full training audience.

The correct answer is B . A major reason for moving to Enterprise Grid is to centralize governance across multiple workspaces. Enterprise Grid allows an organization to manage policies, security controls, identity settings, app governance, and administrative structures at the organization level instead of managing each workspace independently. This becomes important when a company has several Slack workspaces and wants consistent controls, standardized access, centralized compliance, and a unified operating model. Option A is incorrect because Slack Connect is not exclusive to Enterprise Grid; it can be used on paid Slack plans, so it is not the strongest reason for a grid migration. Option C is also not specific to Enterprise Grid because workflows and app integrations are available outside Grid. Option D describes a type of migration scenario, but it is not the core business reason a client would pursue Enterprise Grid. The exam is testing whether the consultant understands the strategic value of Grid: enterprise-scale governance and centralized administration across workspaces.
Reference topic: Delivery and Migration - Enterprise Grid migration rationale, centralized policies, shared settings, multi-workspace governance, and enterprise administration.