04 Define Users in Okta (Provisioning-LCM) Flashcards

1
Q

Demo 1: Lifecycle Management Demonstrate knowledge of what lifecycle management is in Okta

A

Lifecycle Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Demo 1A: Provisioning Concepts Demonstrate knowledge of what lifecycle management is in Okta

A

Provisioning Concepts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Demo 2: Demonstrate knowledge of when to use Okta user states and statuses

A

End user account states

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Demo 2A: Demonstrate knowledge of when to use Okta user states and statuses

A

Manage users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Demo 2B: Demonstrate knowledge of when to use Okta user states and statuses

A

Okta Essentials Module 2: Define Your Users in Okta

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Demo 3: Demonstrate knowledge of how to use app assignments, requests, and automations to provision applications to users

A

Access Request Workflow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Demo 3A: Demonstrate knowledge of how to use app assignments, requests, and automations to provision applications to users

A

Okta Essentials Module 5: Configure SSO and Provisioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Demo 3B: Demonstrate knowledge of how to use app assignments, requests, and automations to provision applications to users

A

Okta Essentials Module 7: Manage Access Request Workflows

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Demo 4: Demonstrate knowledge of how to manage group assignments and rules

A

Manage Groups

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Demo 5: Demonstrate knowledge of the various group types supported by Okta

A

Using Group Push

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Demo 5A: Demonstrate knowledge of the various group types supported by Okta

A

Manage Groups

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Demo 5B: Demonstrate knowledge of the various group types supported by Okta

A

Okta Essentials Module 4: Configure Groups

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Is “people” required in Okta?

A

Within Okta, people are one of the mandatory components. You cannot use Okta without configuring people or users within it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Why do you want to create groups/users in Okta?

A

You can create different types of users, Okta-master users, import users from a directory, or import users from applications. Creating different users provides them access to applications securely and easily. With users in Okta, you can then associate administrative permissions to users for assistance administering the Okta instance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How do you create accounts independent of an external directory service?

A

Import users into Okta and create groups.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How do you provide access to people outside of Okta?

A

Create groups that allow limited access.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Instead of “users” what does Okta refer to individuals as

A

People

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What are the 3 types of users in Okta?

A

a. Okta-Mastered b. Directory-Mastered c. Application-Mastered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

How does Okta allow access to different people?

A

While all people profiles contain core information, such as first name, last name, and email address, how the person accesses applications and authenticates to Okta depends on your directory service and Okta configurations.

20
Q

What are the characteristics of Okta-Mastered people?

A

a. They are created and maintained in Okta b. They are authenticated against Okta policy c. They are associated with Okta groups d. Provide an alternative login method separate from external diretories. They are governed by Okta user profile.

21
Q

What are the characteristics of Directory-Mastered people?

A

a. Has to be imported from an external directory. The people records are known as directory mastered.
b. These people are created and maintained in the external directory.
c. The directory has to be pulled into Okta using an agent.
d. It has to authenticated against the external directory
e. It has to be associated with directory or Okta groups.
f. It has to be governed by the directory user profile.

22
Q

What are the characteristics of an Application-Mastered people?

A

a. When imported from an app, the people records are known as application-mastered.
b. These people are being created and maintained in the application such as Workday or SF.
c. Pushed to Okta using a pre-defined Okta integration Network (OIN) application.
d. Authenticated against Okta or external directory
e. Governed by the application user profile.

23
Q

What are the things that administrators can do with Okta-mastered users with account and Password management?

A

a. Define authentication settings in Okta
b. Manage account unlocks and resets through the Okta Administrator app.
c. Can mass reset password

24
Q

What are the things that end users can do with Okta-mastered users with account and password management?

A

a. Can modify account information and change passwords on the account settings page
b. Can use the Forget password link to reset password

25
Q

What are the things that administrator can do with Directory-mastered users?

A

a. Define authentication settings in the directory service.
b. Manage all accounts changes through the directory services

26
Q

What are the things that end users can do?

A

a. Unable to modify account information on the account settings page
b. Ability to change or reset passwords determined by the administrator configuration.

27
Q

What is the password management for Okta-mastered users?

A

a. The pw policy settings enable you to define and enforce the use of strong passwords to help protect your company assets.
b. For Okta-mastered users, you can specify the character length, complexity req, pw age, and lockout athn settings in Okta.
c. You can use the Reset Password functionality to perform a bulk pw reset on all or specific Okta-mastered accounts.

28
Q

What is the password management for Directory-mastered users?

A

a. For directory-mastered users, the pw autN are configured in directory service server.

29
Q

Is enabling the AD PW Policy options default?

A

Enabling the AD PW Policy option in Okta, enable users to reset or change AD pw through the Okta interface, is not by default. The password policies are governed by the directory service server.

30
Q

For Directory Mastered Users, what is necessary to change accounts including status changes?

A

a. all account changes, including status changes, must be performed in the directory service.

For example, if an employee has left the company and their account is mastered in Active Directory, change the status in Active Directory.

b. The Okta Active Directory agent pulls the status update from Active Directory and pushes it to Okta. Okta then deactivates the user account.

31
Q

What does it mean when an account is “staged”

A

a. It reflects a new account has been created through the API, but not yet active.

32
Q

When an account has been provisioned, what much occur to change the status to active?

A

a. An Administrator can manually activate the account.
b. With JIT provisioning enabled, the user authenticating to Okta for the first time changes the account to active.

33
Q

Can you only suspend Okta-mastered users?

A

a. Yes, only OMU can be suspended.

34
Q

What does suspending an account mean?

A

a. You expect the user to return and don’t want them to have access while they are away.
b. If an account associated with an API token is suspended, the token cannot be used.

35
Q

What does deactivate account mean?

A

You are not expecting the user to return and you are beginning the process of be able to delete that account.

36
Q

What must happen before you delete a user?

A

a. You must first deactivate the user
b. You can deactivate an account through the Okta Admin app or API
c. After the account is deleted, admins can create a new Okta user with the same username as the deleted one.

37
Q

Which admin role can delete a user?

A

a. Super Admin
b. Org admin
c. Group Admin

38
Q

How long doe Okta logs last?

A

a. 6 months

39
Q

How do you create a user in Okta?

A

a. People > “Add Person”
b. Make sure the username is something.something@ – in the form of an email address.
c. Does not have to be a valid email address.

40
Q

When importing users via CSV, what are the options to activate a user?

A

a. Automatically activate a new user
b. Do not create a password and only allow login via IDP.

41
Q

What are the options to set password by user or admin?

A

a. Set by admin and Admin set the password and toggle of whether user must change the password on the first login.
b. Set by users and users set password with activation email sent to the user.

42
Q

What does “Password expired. User is not in one-time password mode?

A

a. Because we said to change the password ==> this is why it is in that mode.

43
Q

Your customer has 30 contractors that are going to be using Okta and they will be starting on Monday. Which feature can you use to quickly create all user records in Okta?

A

a. CSV import

44
Q

You are uploading a CSV file using the download template for your contractors, but Mike Bennette account received an error and was not created. After reviewing the data, what is the problem?

A

a. Log in is not the correct format –should be in the form of an email address.

45
Q

True/False. If there were other records in the CSV file, that were correctly formatted, they would have imported successfully regardless to the incorrect formatted entry.

A

a. True