For any business process that needs to run at a specific time interval (in this case, "once a week"), a Scheduled flow is the standard tool. A scheduled flow allows the Platform Administrator to define a frequency (Daily, Weekly, or Once) and a start time57. The flow can then query all relevant Account records and perform the logic of counting open cases and updating the parent record autonomously58. Record-triggered flows (Option B) are inappropriate here because the count needs to happen on a schedule rather than being triggered by an individual record edit59. Autolaunched flows (Option C) must be called by another process, such as a button or Apex, and do not have their own timing mechanism60. "Automation event triggered flow" (Option D) is not a standard type of flow used for recurring batch processing

The "Minimum Access - Salesforce" profile is a very restrictive standard profile designed to provide no access by default, adhering to the principle of least privilege. One of the specific permissions that is not included in this profile is the Lightning Experience User permission. Without this system permission, users will be defaulted to the Salesforce Classic interface (or potentially blocked from any UI if no other access is granted). To resolve this, the Platform Administrator should either edit the custom profile or, preferably, create a Permission Set that includes the "Lightning Experience User" checkbox and assign it to the affected users. This "unlocks" the modern Lightning interface for them. Options B and C relate to the design of specific pages, but they are irrelevant if the user isn't even allowed to enter the Lightning environment. Option A refers to a different feature set entirely and does not address basic UI access.

To facilitate the discussion of "sensitive records" where even the existence of the group must be hidden from non-members, a Chatter Unlisted Group is the appropriate solution. Unlike a Private Group (Option B), which can be seen in searches and lists even if the content is hidden, an Unlisted Group does not appear in search results and requires an explicit invitation to join. This ensures that only members know the forum exists, meeting the highest privacy requirement. Public Groups (Option C) are visible to everyone and are not suitable for sensitive discussions42. "Private Chatter Channel" (Option D) is not a standard term for this type of collaboration group. Unlisted groups must be enabled in Chatter Settings before they can be created by administrators.

In this scenario, the two teams are "peers" in the role hierarchy (both reporting to the same manager). In a private sharing model, peers cannot see each other's records by default. To grant lateral access between these specific groups, an Owner-based Sharing Rule is the most effective solution. The administrator can create a rule stating that any records owned by members of "Role: Sales Team A" should be shared with members of "Role: Sales Team B" with specific access levels (e.g., Read/Write). Hierarchical sharing (Option C) only grants upward visibility to the Manager role, not across to the other team34. Manual sharing (Option D) is inefficient for an entire team35. Criteria-based sharing (Option A) is used when record field values determine access, whereas this requirement is based specifically on who owns the records36.

Agentforce is designed to handle multi-step processes that require reasoning and adaptation. Unlike traditional automation (like Workflow or simple Bots) that follows a linear, "If-This-Then-That" path, an Agentforce agent uses generative AI to understand user intent and choose the best sequence of actions to reach a goal. If a customer's request changes mid-conversation or requires the agent to check multiple systems and make a judgment call, the agentic loop allows it to adapt its behavior in real-time. Single-step processes (Option A) or tasks without decision-making (Option D) are better handled by standard Flow or Macros, which are more cost-effective for simple tasks. Static document generation (Option B) is a fixed output task. Agentforce's true value lies in managing the "gray areas" of business processes where human-like flexibility is needed.