Option B sounds more logical to me. If the customer isn't responding after 30 minutes, I'd mark the session as customer Inactive first, just in case they come back or to meet any audit requirements. Ending it right away (A) feels a bit abrupt, and I think Salesforce best practice is to indicate inactivity before closing out. Some orgs might skip that extra step though, so let me know if I'm missing something!

Option C and this always messes with me. Salesforce loves to bury this-once you check "Use standard Salesforce sharing," the Data Categories don’t actually restrict article access anymore, it all goes off record-level sharing. Think C is right but the docs are annoyingly vague about impact.

Yep, I’d go with C here. Data category groups are designed to control article visibility based on user/division, and using the role hierarchy lets you map that directly to how teams should see content. Official study guides and practice questions highlight this approach for strong compliance needs. Think it’s the most secure fit, but open to other takes if anyone's seen something else.

B seems reasonable to me, since article categories can be restricted per division and you could tie sharing to that. If each division has its own category, wouldn’t that control who sees what? Maybe I’m missing a Knowledge-specific rule though.

This is the kind of labeling that always gets me. I don't think it's B, C makes sense since resellers are usually servicing end customers, so customer site should work here right? Not sure why everyone jumps to partner.

Pretty sure it's B in this case. Resellers act as partners so the Partner Experience site gives them the right level of access to accounts, cases, and dashboards. A or C don't really fit for external partners. Happy for other views if I missed something.

B . But does "resellers" only mean external partners, or do they also include end customers? If it's just partners, B is right, but if customers need the same access, C might make sense instead.

Not sure A is the only way here. Wouldn’t C (Email relay) also keep things in the firewall if configured right, or does that always send data out? Kinda fuzzy on how strict UC’s policy is.

Wouldn't File Preview (option B) be the best fit here? In Service Console, agents can usually use File Preview straight from the chat for common formats like PDF. Downloading (C) is a workaround but not as seamless. I think B matches what Salesforce recommends-correct me if this doesn't work with WhatsApp integration specifically.

Are WhatsApp file previews natively supported in the Service Console or only for certain channels? Not clear to me if B is always available here.

Pretty sure A could work for most reporting here, since custom report types are pretty flexible and cover user activity plus data categories. The only catch is some Knowledge search metrics might not be fully exposed in standard reports. If those metrics are available though, A makes sense imo? Open to other thoughts.

Not convinced it's B, I think A could handle those requirements too since custom reports are pretty flexible. Trap answer maybe?