What is the first step in creating a custom RBAC role in Cortex?

Select the data scopes the role can access

Assign the role to a user group

Define the role name and description

Generate an API key for the role

A user in Cortex currently has the 'Analyst' role, which allows viewing incidents. The user is being promoted to a senior role that should also allow closing incidents. What is the correct way to update the user's permissions?

Create a new role with the additional permission and assign it to the user.

Modify the 'Analyst' role to include the 'Close Incidents' permission.

Assign the user a different role that already includes the 'Close Incidents' permission.

Add the 'Close Incidents' permission directly to the user's account.

A new hire joins the security operations team. The team uses a group-based access model in Cortex. The new hire should have the same access as other team members, which includes a custom role and access to the 'SOC' folder. What is the most efficient way to grant this access?

Add the new hire to the existing security operations group in the identity provider.

Create a new role for the new hire and assign it to the user.

Assign the existing role directly to the new hire and set the scope to 'SOC'.

Copy the role from another team member and assign it to the new hire.

In the Cortex tenant identity lifecycle, which action is typically performed FIRST when a new user joins an organization?

Assign the user to a role that grants access to all data scopes

Deactivate the user account to prevent access until onboarding is complete

Generate an API key for the user to enable programmatic access

Create a user account in the tenant and assign initial attributes

Which statement accurately describes how roles are assigned in a Cortex tenant?

Roles can be assigned to individual users or to groups, and a user can hold multiple roles

Each user is limited to exactly one role at any time

Roles are automatically assigned based on the user's email domain

Roles can only be assigned to groups, never to individual users

Palo Alto NetworksCertified Cloud Security Engineer

Domain 1Objective 4

1.4 Explain the Configuration and Management Lifecycle of User Identity, Roles, Permissions, and Access Controls Within a Cortex Tenant (e.g., Scope-Based Access Control [SBAC], Custom Role-Based Access Control [RBAC] Roles, API Keys) CLOUD-SECURITY-ENGINEER Practice Questions (Page 1)

Part of the Planning and Installation domain, which accounts for 12% of the CLOUD-SECURITY-ENGINEER exam.

22questions here

5free pages

8concepts

12%of the exam

Questions 1–5

1foundation · easy
What is the first step in creating a custom RBAC role in Cortex?
Select an answer first
2application · medium
A user in Cortex currently has the 'Analyst' role, which allows viewing incidents. The user is being promoted to a senior role that should also allow closing incidents. What is the correct way to update the user's permissions?
Select an answer first
3application · medium
A new hire joins the security operations team. The team uses a group-based access model in Cortex. The new hire should have the same access as other team members, which includes a custom role and access to the 'SOC' folder. What is the most efficient way to grant this access?
Select an answer first
4foundation · easy
In the Cortex tenant identity lifecycle, which action is typically performed FIRST when a new user joins an organization?
Select an answer first
5foundation · easy
Which statement accurately describes how roles are assigned in a Cortex tenant?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CLOUD-SECURITY-ENGINEER

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Palo Alto Networks. “CLOUD-SECURITY-ENGINEER” is a trademark of its owner, used for identification only.