What is the purpose of Federated Authorization?

Question

Options

• AEnforce access control policies within a single domain.
• BEnable single sign-on across multiple applications within the same domain.
• CShare user identity and access information across multiple domains.
• DAuthenticate users using a third-party authentication service.

• A
  8% (2)
• B
  4% (1)
• C
  85% (22)
• D
  4% (1)

Explanation

Federated Authorization enables organizations to share identity and access control information across trust boundaries - meaning different domains or organizations can recognize each other's users and honor their permissions without requiring separate accounts. This is the core value proposition: a user authenticated in Domain A can access resources in Domain B because both domains participate in a shared federation.

Why the distractors fail:

• A describes standard authorization (like RBAC/ABAC) within a single domain - federation's cross-domain element is entirely absent.
• B describes Single Sign-On (SSO), which is a benefit of federation but only within one domain; SSO alone doesn't require sharing across organizational boundaries.
• D describes third-party authentication (e.g., "Login with Google") - that's federated identity, not federated authorization, which is specifically about access rights, not just proving who you are.

Memory tip: Break it down - "federated" = multiple parties/domains working together, "authorization" = what you can do (not who you are). So Federated Authorization = sharing what users are allowed to do, across multiple domains. If the answer involves crossing domain lines with access policies, think C.

No community discussion yet for this question.