Home labs & practical projects

Pilot a group-based application access change

A project to do with your own tools, with guidance on what to create and capture.

Vendor environment Suggested time: 2–3 hoursYour own authorised environment

What you could create

An administrator must move a test application from individual assignments to a group-based model while preserving the intended access boundary.

Example evidence format

Project evidence map (example)

Assignment change planScope and inputs

Lifecycle test results and audit observationsDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Assignment change plan	Show the inputs, scope and decisions behind this record. Removing group membership produces the intended access outcome.
Lifecycle test results and audit observations	Include the evidence supporting your conclusion. The transfer case does not accumulate obsolete application access.

What you'll need

Vendor environment

Use an authorised Okta training tenant, a test application and three test identities. Confirm feature availability and save the starting assignments.

Project record

Keep the working files for assignment change plan and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

Access may require a licence, trial or training subscription. Confirm availability and permitted use before committing; no free tenant is assumed.

Use an authorised training tenant with test identities and synthetic data. If access is unavailable, document the plan and label it untested.

Suggested milestones

1
Plan and investigate
Define the target group and assignment rules.
2
Develop your approach
Pilot membership changes for a joiner, transfer and removal case.
3
Verify and explain
Inspect sign-in and lifecycle events, then document rollback and review ownership.

Evidence worth keeping

Keep clear, organised evidence of your design and any testing you carry out.

1
Assignment change plan
Show the inputs, scope and decisions behind this record. Removing group membership produces the intended access outcome.
2
Lifecycle test results and audit observations
Include the evidence supporting your conclusion. The transfer case does not accumulate obsolete application access.

Label design proposals and observed results clearly.

Explain your work

Use these prompts to reflect on your decisions and what you learned.

Which part of your assignment change plan needed the most judgement?
What observation or assumption changed your approach?
What would you improve, and what have you not verified?

Describe this as a personal project in your portfolio.

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

A useful starting point

Use an authorised Okta training tenant, a test application and three test identities. Confirm feature availability and save the starting assignments.

What a good result looks like

Removing group membership produces the intended access outcome.
The transfer case does not accumulate obsolete application access.

Finish the project

Remove test identities, policies and data, restore the initial configuration, and check trial expiry or renewal settings.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.