Question 79

Explanation

The correct answer: Federated access control relies on the concept of trust between different organizations or domains. In this model, a user's authentication process in one domain is trusted by another domain without the need to re-authenticate when accessing resources. A trusted third party (often an identity provider) vouches for or authenticates the user, and other entities (service providers) trust this authentication. A common example is Single Sign-On (SSO) solutions across different web services. The incorrect answers: Role-based access control (RBAC) is an approach where permissions are assigned to specific roles, and users are assigned roles. It's not based on the concept of a trusted third party for authentication. Instead, it centralizes permissions around roles within the system. In rule-based access control, access is granted or denied based on a set of rules, often defined by system policies. These rules can include aspects like time of day, the network source of a request, or other conditions. This model doesn't inherently rely on a trusted third party for authentication. Multi-factor authentication (MFA) is a method that requires a user to provide multiple types of credentials to authenticate their identity. This often includes something they know (like a password), something they have (like a smart card or a token), and something they are (like a fingerprint). MFA does not revolve around the concept of a trusted third party.