Salesforce Certified MuleSoft Integration Foundations free question 2 / 10 · Domain 1: Identify the roles, responsibilities, and lifecycle of an integration project
An organization builds teams in Anypoint Platform with one team per region and, under each, child teams for job functions. Which statement about the permissions of a child team matches the Teams documentation?
- The child team inherits its parent team's permissions and cannot be given any additional ones
- The child team's permissions are worked out from whatever each of its members holds as an individual
- The child team inherits all of its parent team's permissions, and more can be added for its members' duties
- The child team is granted its permissions from scratch, and it is managed separately from its parent team
Show the answer and explanation
Answer: C
Why this is correct
The section 'Permissions Structure' explains that teams are hierarchical and that every child team inherits permissions from its parent team. It then says you can add permissions to the inherited set to give each child team more specialized permissions that reflect the members' responsibilities. A regional team's permissions therefore flow down to its job-function child teams, which can then be extended. This cascading structure is why the documentation calls managing users and permissions scalable.
Why the other options are wrong
"The child team is granted its permissions from scratch, and it is managed separately from its parent team" … Teams have a cascading permissions structure, so a child team does not start from nothing. It inherits what its parent team has.
"The child team inherits its parent team's permissions and cannot be given any additional ones" … The documentation lets you add permissions to the inherited set, giving each child team more specialized permissions that reflect its members' responsibilities.
"The child team's permissions are worked out from whatever each of its members holds as an individual" … Permissions for a team are assigned to the team, and members get them through membership. They are not derived from what each member happens to hold individually; individual permissions are a separate option for users outside teams.
Teams versus individual permissions
The documentation also says an Organization Administrator can assign permissions to individual users without a team. Teams are the structured way, mirroring the organization by region or job function, while individual grants are the exception.