Checkpoint challenge
Original, scenario-based practice. Never modeled on actual exam questions. It’s written in the “What I Would Architect” style: the point is making your judgment visible, not picking a letter. This challenge comes at the end of chapters 6 to 10, the record-sharing tools you configure by clicking. My walkthrough is Checkpoint 1: Steve Trucking’s Internal Users, What I Would Architect, so try it first.
Scenario
Section titled “Scenario”Steve Trucking is a last-mile delivery company. Big-box Retail Partners sell appliances, TVs and furniture; Steve Trucking’s two-person crews deliver them to the Retail Partners’ customers, the Recipients. Read the Steve Trucking brief, sections 1 to 8. Leave section 9 (the late changes) alone; they come at the end of the course.
This checkpoint is only about Steve Trucking’s own staff. Retail Partner users in the portal, the crews on their phones and the Recipients come later in the course.
What’s already decided
Section titled “What’s already decided”The data model comes from the Data Architect course, and you don’t need to redesign it:
- Retail Partner: an Account. Under it, a child account for each distribution center (DC), with Parent Account filled in: nine DC accounts today.
- Partner staff: Contacts under their DC’s account.
- Delivery: a Work Order, carrying its DC account. Its items are Work Order Line Items; its visit is a Service Appointment. The Recipient’s name, phone and address are fields on the Work Order.
- Manifest: one custom object,
Manifest__c, the partner’s list of deliveries for a day. - Cases: Recipient questions and partner claims, linked to the DC account.
- Opportunities: Retail Partner contract renewals and new DC bids.
- Integrations: each Retail Partner’s integration has its own user, and it creates the Work Orders from the manifests.
- Field Service: each DC is a service territory.
The internal users
Section titled “The internal users”| Who | How many | Their job |
|---|---|---|
| Dispatch coordinators | 45, across nine DCs | Steve Trucking staff who work inside a Retail Partner’s DC: receive manifests, plan routes, dispatch trucks, handle exceptions |
| Regional managers | 3: Phoenix, Dallas, Atlanta | Run the three DCs in their region, one for each Retail Partner |
| Customer care agents | 60 | Answer Recipients and Retail Partners, for every partner |
| Operations, finance and sales | 40 | Invoicing, crew incentives, contracts and new DC bids |
| Leadership | a few | Everything, over five years |
Requirements
Section titled “Requirements”- S2. A Retail Partner must never see another Retail Partner’s deliveries, pricing, volumes or Recipients.
- S4. Recipient addresses, phone numbers and delivery notes are personal data.
- R10. Coordinators plan routes for their DC, assign trucks and crews, and see every truck’s progress in one screen.
- RP2. Leadership sees volume, on-time, claims and revenue by Retail Partner, DC and crew.
- RP3. Coordinators see the day’s progress and exceptions for their DC.
- O1 and O3. Three times today’s volume in five years, and a new Retail Partner or DC in weeks, not months.
Your task
Section titled “Your task”- The defaults (chapter 6): set the internal org-wide default for Account, Contact, Opportunity, Case, Work Order, Service Appointment and
Manifest__c. For each, say why, and who it’s hiding records from. - The coordinators (challenge SV2): a coordinator works inside one Retail Partner’s DC. Should they see other DCs? Other Retail Partners? Argue it from S2 and from where they sit. Then say how they get the deliveries they need, with which mechanism.
- The role hierarchy (chapter 6): draw it for access, not as an org chart. Coordinators, regional managers, customer care, back office, sales and leadership. Where does each integration user sit, and why?
- Who owns what (chapters 6 and 8): who owns the Work Orders, the DC accounts, the cases and the opportunities? What does each choice open, and for whom?
- The groups, rules and teams (chapters 7 to 9): which public groups, which sharing rules (owner-based or criteria-based), which teams? Count the rules, and say what happens to the count when Steve Trucking wins its tenth DC. Do you need territories?
- What the data model shares on its own (this chapter): list every place Salesforce opens a record by itself in your design: implicit sharing, Controlled by Parent, the role’s child access, and the overrides. Then list the places a reader might expect it to and it doesn’t.
Write each decision as both options, then your choice: “in my professional opinion…”
Discussion
Section titled “Discussion”My walkthrough is Checkpoint 1: Steve Trucking’s Internal Users, What I Would Architect. Compare your reasoning, not just your boxes. Where you chose differently, can you say what you’d gain and what you’d give up?