Q: 10
A multinational corporation is planning to migrate its entire IT infrastructure to a cloud environment. The company has several business-critical applications that require high availability, scalability, and robust security measures. They need to ensure that the cloud infrastructure components selected can support these requirements effectively. Which of the following cloud infrastructure components is most critical for ensuring high availability, scalability, and robust security for the company’s business-critical applications?
Options
Discussion
Option B is the advantage that comes up most in the official guides and practice tests for cloud security. Assigning roles instead of fiddling with individual permissions saves a ton of admin work, especially as user numbers grow. I think that's what they're looking for here, but let me know if anyone reads it differently!
Option B, A is a trap, RBAC doesn't mean full access just easier management of permissions.
Gotta be B, that's what RBAC is about. Assigning permissions by role cuts down on repetitive admin work and mistakes. Makes managing big cloud setups way smoother. If I've missed something let me know!
B tbh, that's the core purpose of RBAC. You assign roles instead of setting up every single permission for each user, way less effort for admins. Pretty sure that's what they're testing for here, unless I'm missing something.
Its B, since RBAC makes managing permissions way easier than setting them for every user.
Maybe B here since assigning roles instead of individual permissions is why RBAC makes life easier in cloud IAM setups.
B
I went with A. I thought giving users access to all resources could be seen as an advantage if the org wants fewer restrictions, especially in less sensitive setups. Not fully convinced now re-reading it, but that's what made sense to me initially. Anyone else consider A?
Pretty sure B is right here since RBAC is all about giving permissions through roles instead of assigning them to each user. Makes it much easier to manage, especially in complex cloud setups. Open to other takes if I'm missing something.
A
Be respectful. No spam.
