# Role-Based Access Control

Role-Based Access Control assigns permissions to roles that represent responsibilities and grants identities access through their authorized roles.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/role-based-access-control

> Role-Based Access Control (RBAC) separates permission definitions from individual users or workloads, making access easier to administer and review. In cloud environments, it supports consistent authorization across teams and accounts, but requires carefully scoped roles and controlled assignments to prevent excessive privileges.

Practice exams covering Role-Based Access Control: [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of Role-Based Access Control

RBAC centralizes permissions around responsibilities while depending on secure assignments, least privilege, lifecycle reviews, and complete authorization evaluation.

1. **Permissions organized by responsibility**: Define reusable roles around operational tasks rather than individual people. Keep permitted actions and resource scope explicit so a role name such as operator does not hide broad administrative access.
2. **Controlled role assignment and assumption**: Govern who can assign roles, change their permissions, or assume them. For cloud role sessions, evaluate the trust relationship separately from the permissions available after assumption.
3. **Least privilege and separation of duties**: Grant only the permissions needed for each responsibility and review combinations of assignments. Separate sensitive duties, such as approving a change and deploying it, where the control requires independent actors.
4. **RBAC and ABAC composition**: Use roles to define job capabilities and attributes to constrain which resources those capabilities apply to. Protect authorization-relevant tags and validate condition support for the specific API actions involved.
5. **Lifecycle management and auditability**: Review assignments after team changes and remove obsolete access. Record role assumptions and resource operations so engineers can connect actions to the responsible identity and session.
6. **Effective authorization evaluation**: Do not infer effective access solely from a role's attached permissions. Account for resource policies, explicit denies, session restrictions, organizational guardrails, and the platform's policy evaluation rules.

## Role-Based Access Control exam questions

Real practice exam questions on Role-Based Access Control, with the correct answer and its explanation.

### Question 1 (MLA-C02 (beta))

**Question:**

A company has two teams that use Amazon SageMaker AI. Model evaluators must invoke a designated staging endpoint but must not access the production endpoint. Production support engineers must inspect the production endpoint configuration by using DescribeEndpoint but must not invoke either endpoint. Employees sign in as IAM users and then assume roles. Access must be administered by job function rather than through individually maintained SageMaker policies.

The users currently have no SageMaker permissions. Only security administrators can modify IAM policies, roles, and team memberships. Which configuration meets these requirements?

**Correct answer:** Create an evaluator role allowing InvokeEndpoint only on the staging endpoint and a support role allowing DescribeEndpoint only on the production endpoint. Configure trust policies and team-group policies so that each team can assume only its designated role.

**Explanation:** This separates permissions by job responsibility and scopes each role to the required action and endpoint. Restricting both role trust and assumption permissions to the appropriate team prevents users from obtaining the other team's permissions.

### Question 2 (AIP-C01)

**Question:**

A company uses an Amazon Bedrock agent to help employees manage purchase orders. Purchasing analysts may view orders, while purchasing managers may view orders and approve payments. Both groups use the same application backend and agent. An action-group Lambda function calls an internal purchasing API that uses IAM authorization and supports separate read and approval permissions.

The backend validates enterprise identity tokens and can retrieve authoritative job-function assignments. Employees cannot call the purchasing API directly. However, employees can manipulate prompts and action parameters, so neither model output nor client-supplied role names can be trusted for authorization. The Lambda execution role currently permits both purchasing operations.

The company must enforce job-function permissions at the purchasing API, even when the agent proposes an unauthorized action. Which design meets these requirements?

**Correct answer:** Create separate reader and approver IAM roles with appropriately scoped API permissions. Remove direct purchasing API permissions from the Lambda execution role. Bind each action invocation to a server-validated employee identity, check the employee's authoritative job-function assignment, and assume only the corresponding authorized role before signing the API request.

**Explanation:** This separates permission definitions by business responsibility and controls role assignment using trusted identity and entitlement information. The purchasing API evaluates credentials for a role with only the appropriate permissions. Independent authorization before role assumption prevents prompts or generated action arguments from elevating an analyst to an approver.

### Question 3 (SOA-C03)

**Question:**

A company's CloudOps engineers use IAM users in a single AWS account. Each engineer performs routine monitoring and occasionally performs approved recovery work. During monitoring sessions, engineers must be able to inspect EC2 instances but must not be able to restart them. Engineers must deliberately switch to a separate session to perform recovery actions. Neither type of session may modify IAM resources.

The company wants to maintain permissions centrally by operational responsibility rather than maintain separate permissions for each engineer. An existing access-management process can authorize approved users to assume designated roles. The IAM users have no direct permissions to operate EC2 instances, and no other policies grant access.

Which configuration meets these requirements?

**Correct answer:** Create separate monitoring and recovery IAM roles. Give the monitoring role only the required EC2 inspection permissions and the recovery role only the required inspection and approved recovery permissions. Authorize approved engineers to assume the appropriate roles, and grant neither role IAM modification permissions.

**Explanation:** Separate roles maintain permissions by operational responsibility. Monitoring sessions cannot perform recovery actions, and engineers must assume the recovery role to obtain those permissions. Omitting IAM modification permissions from both roles satisfies the restriction because no other policies grant access.

### Question 4 (SCS-C03)

**Question:**

A company federates security personnel into a shared SecurityEntry IAM role by using AWS STS. Each SecurityEntry session receives a Duty session tag from an administrator-controlled identity provider attribute. The value is either Analyst or IncidentResponder. Users cannot change the Duty tag on their SecurityEntry sessions.

Users then call AssumeRole to obtain credentials for either an Investigation role or a Remediation role. Both destination roles currently trust SecurityEntry without conditions. SecurityEntry allows sts:AssumeRole on both roles. Investigation grants approved read-only permissions, and Remediation grants approved write permissions.

Analysts must be able to assume only Investigation. Incident responders must be able to assume both roles. Users control their AssumeRole request parameters, including RoleSessionName and requested session tags. The destination roles already permit sts:TagSession without tag-related restrictions. No transitive tags are involved, and no other policies restrict role assumption.

The company must retain the existing roles and permissions policies. Which change to the Remediation role's trust policy will enforce the required job-function restriction?

**Correct answer:** Add a StringEquals condition requiring aws:PrincipalTag/Duty to equal IncidentResponder to the statement that allows sts:AssumeRole.

**Explanation:** During role assumption, aws:PrincipalTag/Duty evaluates the trusted tag on the calling SecurityEntry session. Only IncidentResponder sessions satisfy the condition. A tag requested for the destination session does not replace the caller's principal tag during this evaluation. Investigation remains available to both job functions.

### Question 5 (DEA-C01)

**Question:**

A company stores customer records in an Amazon RDS for PostgreSQL database. The private.customer table contains customer_id, region, email, and tax_id columns. A database administrator owns the table and has created reporting.customer_summary, an ordinary view that exposes only customer_id and region. The view uses its owner's permissions to access the underlying table.

Analysts have individual database logins that inherit privileges from a NOLOGIN role named reporting_reader. Neither the logins nor reporting_reader currently has any schema or object privileges, and PUBLIC has no privileges on either schema or its objects. Analysts must query the existing view but must not read the underlying table directly or access email and tax_id.

Which configuration meets these requirements with the least privilege?

**Correct answer:** Grant reporting_reader USAGE on the reporting schema and SELECT on reporting.customer_summary. Do not grant access to the private schema or its table.

**Explanation:** USAGE allows analysts to access objects in the reporting schema, and SELECT permits querying the view. The ordinary view uses its owner's permissions for the underlying table, so analysts do not need direct table privileges. Their inherited role privileges expose only the columns included in the view.

### Question 6 (DOP-C02)

**Question:**

A company uses AWS IAM Identity Center to assign an ApplicationOperator permission set to an operations group in 90 AWS accounts. A platform pipeline manages the permission set through APIs. Security policy requires all permission changes to be deployed through Identity Center; the pipeline must not directly modify IAM roles in member accounts or replace existing account assignments.

The pipeline calls PutInlinePolicyToPermissionSet to add a required application operation. The call succeeds, and GetInlinePolicyForPermissionSet returns the updated policy. However, engineers who obtain new sessions still receive AccessDenied. Inspection shows that the IAM roles provisioned by Identity Center in the assigned accounts still contain the previous inline policy. All other authorization controls permit the operation.

Which pipeline change will deploy the updated permissions to all currently assigned accounts while meeting the security requirements?

**Correct answer:** Call ProvisionPermissionSet for the permission set with TargetType set to ALL_PROVISIONED_ACCOUNTS. Poll DescribePermissionSetProvisioningStatus until the operation succeeds, and investigate any provisioning failures.

**Explanation:** Updating the permission-set inline policy through the API changes its central definition but does not automatically update existing account roles. ProvisionPermissionSet deploys the current definition to the accounts where it is already provisioned. Monitoring the asynchronous result verifies that the rollout completes without replacing assignments or directly editing roles.

### Question 7 (DVA-C02)

**Question:**

A case-management application authenticates employees with an Amazon Cognito user pool. A Lambda backend already validates each access token and obtains its trusted claims. Administrators assign employees to the CaseReaders, CaseEditors, and CaseApprovers user pool groups. These job functions permit viewing, modifying, and approving cases, respectively.

An employee can belong to multiple groups and must receive the combined permissions of those groups. Employees must not gain permissions by modifying client requests. The developer must maintain permission definitions centrally by job function, without maintaining permission lists for individual employees.

Which implementation meets these requirements?

**Correct answer:** Maintain a server-side mapping from each user pool group to its allowed application operations. For every request, combine the permissions mapped to the validated token's cognito:groups claim and reject the operation unless that combination permits it.

**Explanation:** This implements role-based application authorization: administrators assign job-function memberships, and the backend centrally maps those memberships to permissions. Combining permissions supports employees with multiple roles, while server-side enforcement prevents clients from granting themselves access.

### Question 8 (SAA-C03)

**Question:**

A company centrally manages engineers' AWS account access through a workforce access portal. Engineers select an assigned account and job-specific permission set to open an AWS Management Console session. The company now wants engineers to run AWS CLI commands from their laptops with the same account assignments and permissions.

Engineers must authenticate through the existing workforce sign-in process. The company prohibits individual IAM users and long-term access keys and does not want to operate a custom credential broker.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Configure AWS CLI v2 profiles for IAM Identity Center by using aws configure sso. Have engineers run aws sso login and use the profile for the assigned account and permission set.

**Explanation:** AWS CLI v2 integrates natively with IAM Identity Center. Engineers authenticate through the workforce sign-in process, and the CLI obtains temporary role credentials for their assigned account and permission set. This preserves centrally managed access without IAM users, long-term access keys, or a custom credential broker.

## Practice Role-Based Access Control in a full exam

Questions on Role-Based Access Control in each practice exam, with every answer option and an explanation for each:

- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 15 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 8 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 7 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 2 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 2 questions
- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 1 question
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 1 question
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 1 question

## What is Role-Based Access Control

Role-Based Access Control (RBAC) organizes authorization around responsibilities rather than maintaining a separate permission set for every identity. Administrators define roles such as auditor, application operator, and database administrator, associate permissions with those roles, and authorize users or workloads to use them. Authentication establishes who an identity is; RBAC helps determine what that identity may do. Group membership commonly simplifies role assignments, but a group and a role are not necessarily the same object.

A practical design starts with job functions and operational tasks. An auditor might read configuration and audit records without changing infrastructure. An application operator might restart services and inspect logs without modifying identity policies. Scope matters as much as the permitted actions: an operator responsible for a development environment should not automatically receive equivalent access to production. Review role assignments when people change teams, and separate routine administration from emergency access.

Cloud platforms implement these relationships differently. In AWS, IAM roles have trust policies that define which principals may assume them and permissions policies that define allowed operations. AWS Security Token Service issues temporary credentials for role sessions. IAM Identity Center permission sets can provision IAM roles into assigned AWS accounts, allowing centrally managed workforce access. An IAM role is an identity mechanism, however, not proof that an authorization design uses RBAC: its policies can implement RBAC, attribute-based access control, or a combination.

RBAC and attribute-based access control (ABAC) answer different design questions. RBAC commonly grants access because an identity holds an approved responsibility, such as developer. ABAC evaluates attributes of the principal, resource, or request. For example, a developer role could allow supported operations only when the resource's Project tag matches the principal's Project tag. This hybrid approach retains role-based job permissions while using attributes to distinguish projects, reducing the need for a separate role for every project and responsibility combination.

Tag-based authorization requires governance, not just a condition in a policy. Restrict who can change authorization-relevant resource tags, principal tags, and session tags. Where supported, require appropriate tags during resource creation and constrain the supplied values. Otherwise, an identity might retag a resource or manipulate an attribute to gain unintended access. Check support for each service, action, resource type, and condition key; tag conditions do not apply uniformly to every API operation.

RBAC makes access reviews understandable, but fine-grained environments can produce role proliferation, while overly broad shared roles create excessive access. Role hierarchies are supported in some RBAC systems but should not be assumed across cloud providers. Separation of duties also requires explicit design: assigning both deployment and approval privileges to one person can defeat the intended control even if each role looks reasonable independently.

When troubleshooting AWS authorization, first distinguish failure to assume a role from failure to perform an operation after assuming it. Inspect the caller, trust relationship, required assumption permissions, session attributes, requested action, and target resource. Then evaluate relevant identity and resource policies, permissions boundaries, session policies, and organization policies. Boundaries and service control policies do not grant permissions, and applicable explicit denies override allows. Resource-based grants have additional evaluation nuances, so an attached role policy alone does not describe every possible access path. Test intended access and expected denials, and use audit records to confirm which session made the request.

## Learn Role-Based Access Control in lessons

12 short lessons on Role-Based Access Control in 7 certification courses.

- MLA-C02 (beta): Role-Based Access Control: scoped roles for ML workloads (Premium), https://app.blowstack.com/lessons/role-based-access-control-scoped-roles-for-ml-workloads-mla-c02
- AIP-C01: Role-Based Access Control: scoped enterprise roles (Premium), https://app.blowstack.com/lessons/role-based-access-control-scoped-enterprise-roles-aip-c01
- SOA-C03: Role-Based Access Control: scoped roles and controlled assignments (Premium), https://app.blowstack.com/lessons/role-based-access-control-scoped-roles-and-controlled-assignments-soa-c03
- SCS-C03: Attribute-Based Access Control vs Role-Based Access Control (Premium), https://app.blowstack.com/lessons/attribute-based-access-control-vs-role-based-access-control-scs-c03
- DEA-C01: Attribute-Based Access Control versus Role-Based Access Control (Premium), https://app.blowstack.com/lessons/attribute-based-access-control-versus-role-based-access-control-dea-c01
- DOP-C02: Attribute-Based Access Control versus Role-Based Access Control (Premium), https://app.blowstack.com/lessons/attribute-based-access-control-versus-role-based-access-control-dop-c02
