Operations Hub Software study plan

Map the full Operations Hub feature surface (records, pipelines, workflows, reporting, permissions) into a one-page inventory you can annotate as you learn.

Define the core data model in your own words: objects, properties, associations, and how records relate across the platform.

Set up a free trial or sandbox environment and create at least three custom objects with five properties each.

List the ten terms you are least confident about and write a one-sentence definition for each from primary documentation.

Build a working pipeline with at least four stages and move ten sample records through every stage.

Configure property validation rules and required-field logic, then deliberately trigger each rule to confirm the error behavior.

Import a small CSV of records, resolve at least two mapping conflicts, and document what broke and why.

Draft a short written explanation of when to use a custom object versus extending an existing one.

Create at least three automation workflows with different trigger types (record created, property changed, scheduled).

Add branching or conditional logic to one workflow and test both the true and false paths.

Intentionally create a looping or conflicting automation and diagnose the failure using logs.

Write down the execution order and any limits that govern how automations run.

Design and build two reports and one dashboard that answer specific business questions you define in advance.

Apply filters, groupings, and calculated properties, and verify each output against manually counted sample data.

Configure user roles and permissions, then test access as at least two different user personas.

Review weeks 1-3 notes and rewrite any definition you can no longer explain without looking.

Connect the platform to at least one external data source or integration and sync sample records both directions.

Diagnose and fix one failed sync, documenting the root cause and the resolution steps.

Explain data hygiene practices: deduplication, field normalization, and record ownership rules.

Practice describing the sync architecture out loud in under three minutes without notes.

Complete a timed 60-question practice set covering the full domain and log your score per topic area.

Rank your five weakest topic areas by error rate and build a targeted review list for each.

Re-read primary documentation only for those weak areas and rewrite your notes into flashcards.

Re-run any hands-on exercise from weeks 2-5 that touches a weak area.

Complete a second timed practice set and compare per-topic scores against week 6 to confirm improvement.

Build one end-to-end scenario from scratch (objects, pipeline, automation, report, permissions) in under 90 minutes.

Teach two concepts aloud to an imaginary colleague, recording yourself to catch gaps in explanation.

Eliminate any remaining weak area that still scores below your target threshold.

Take a final full-length timed practice exam under realistic conditions and review every missed question.

Re-derive the ten highest-risk facts from memory and check each against documentation.

Skim your entire notebook and consolidate it into a single one-page pre-exam sheet.

Confirm logistics: exam format, timing, allowed materials, and environment requirements.