Why Can't the Engineer Access New Team's Shared Folders?

An engineer moved to another team and is unable to access the new team's shared folders while still being able to access the shared folders from the former team. After opening a ticket, the engineer discovers that the account was never moved to the new group. Which of the following access controls is most likely causing the lack of access?

  1. Role-based Source Reference Answer
  2. Discretionary
  3. Time of day
  4. Least privilege

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The exam tests whether you can identify RBAC when user access is tied to group/role membership, and the trap is confusing it with least privilege or discretionary access.

This SY0-701 question tests understanding of role-based access control (RBAC) in a scenario where a user's group membership was not updated. The community consensus is that RBAC is the most likely cause of the access failure.

Choosing 'Least privilege' is a common mistake because it sounds related to insufficient permissions, but least privilege is a principle, not an access control model that would cause this specific group-membership issue.

Community Discussion (3 comments)

dbrowndiver 👍 6 Selected: A
Role-based is the correct answer because the issue arises from the engineer's account not being updated to include the new role associated with the new team's shared folders. Role-Based Access Control is the framework in place that determines access based on roles assigned to users, making it the most relevant explanation for the engineer's access issue.
Shaman73 👍 3 Selected: A
A. Role-based
Shaman73 👍 1
• A. Role-based

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Role-based access control (RBAC) assigns permissions based on the user's role or group membership. Since the engineer still has access to the old team's folders but cannot access the new team's folders, the account has not been associated with the new role. RBAC directly explains that the lack of access is due to the missing role/group assignment.

Why the Other Options Are Wrong

  • Discretionary (DAC) allows the resource owner to set permissions, which is not the issue here because the problem is systemic group membership, not owner decisions.
  • Time of day is a temporal constraint, not applicable since access is consistent and not time-based.
  • Least privilege is a security principle that says users should have minimal access needed; it does not cause access issues when moving teams, but rather is the reason for limiting access. The scenario is about the mechanism that grants access, which is RBAC.

Community Comment Notes

Comment [1] correctly explains that RBAC determines access based on roles assigned to users, and the account was not updated to include the new role. Other comments simply confirm answer A. There is no debate, and the vote is unanimous, supporting RBAC as the clear answer.

Official Reference

Exam Strategy

When a scenario involves group or role membership affecting resource access, immediately think RBAC. Look for phrases like 'account was not moved to the new group' to distinguish RBAC from the 'least privilege' principle, which is a design guideline rather than an access control mechanism.

Related Analysis

Practice All SY0-701 Questions

Access 100 questions with complete answers and detailed explanations.

View Full SY0-701 Practice Test →

← Back to SY0-701 Study Guide