Okta Certified Administrator · Part II

Administrator Roles

20% of Part II — permission scoping, not just access.

Administrator Roles

Task 4: Create an API Token

4 tasks · this deck covers task 4 of 4 — the last one in this task set

The Task

"Create an API token"

This exact task already has a full course deck — built for Part I's API Functions section, where it's an exam concept. Here it shows up again as something you actually have to click through and do.

The Connection — Full Deck Already Exists

Rather than re-teach the same facts twice, this is a pointer to the deck that already covers it in full: inherited permissions, the service-account best practice, the 30-day lifecycle, and network zone/IP restrictions.

↳ Full deck: API Functions, Module 1 (API Tokens with Correct Permissions)

Why It's Here Too

The reason this shows up under Administrator Roles specifically: creating an API token is itself an admin action tied to whichever admin's account creates it — the same "who created it" logic that governs custom admin roles and their permissions in this use case.

One Line To Remember

Creating an API token is the same task already fully taught in API Functions, Module 1 — go there for the complete facts (inherited permissions, service-account best practice, 30-day lifecycle, zone/IP restrictions). It reappears here because token creation is itself an admin-role-governed action.

Sources: help.okta.com — API.htm (full deck: API Functions Module 1)

✓ Administrator Roles — 4 of 4 courses complete (labs still to come)