AEP study plan

Sketch a normalized data model for a sample business case, separating record types from related reference data

Define record type relationships (one-to-many, many-to-many) and justify each cardinality in writing

Identify which fields should be primary keys, foreign keys, and lookup references

Build a small glossary of data-modeling terms and match each to a concrete example in your model

Create record types, fields, and relationships in a practice environment and load sample data

Write validations and field-level constraints that enforce your business rules

Design two process models that write to and read from your record types

Trace how a process variable maps to a record field and document the mapping

Model a multi-step approval process with gateways, assignments, and escalation paths

Configure task assignment using groups and dynamic assignees

Add error handling and a boundary path for a failed external call

Explain the difference between process variables, node inputs, and rule inputs in your own notes

Build a form that collects data and submits into your process

Apply conditional visibility and dynamic dropdowns driven by record data

Add validation and user feedback on the form

Connect a task to a record so the assignee sees context without extra navigation

Lay out a record list view with filters, sorting, and a detail view

Design a dashboard-style page using reusable interface components

Apply consistent layout, spacing, and labeling conventions across two interfaces

Write a short accessibility and usability checklist and apply it to your pages

Configure an integration that calls a REST endpoint and parses the response into process variables

Map integration errors to user-facing messages and retry logic

Describe when to use an integration object versus a connected system in your notes

Document authentication options for outbound calls and pick one for your practice integration

Define groups, roles, and object-level permissions for your practice app

Implement record-level visibility so users see only their own or their team's data

Audit your app for over-permissioned objects and correct at least two findings

Explain how authentication and authorization differ in your own words with examples

Review platform architecture concepts and write a one-page summary from memory

Deploy your practice app between two environments and document the deployment steps

Write and run a test plan covering process, interface, and security scenarios

Complete a timed mixed-domain practice set and log every missed concept

Build a personal weak-area list with a remediation action for each item