MENU
In a federated identity arrangement using a trusted third-party model, who is the identity provider and who is the relying party?
Suggested Answer: D
Get Premium CCSP Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
In a trusted third-party model of federation, each member organization outsources the review and approval task to a third party they all trust. This makes the third party the identifier (it issues and manages identities for all users in all organizations in the federation), and the various member organizations are the relying parties (the resource providers that share resources based on approval from the third party).
14 comments · newest first
EL
Eloisa
11 months ago
I thought the identity provider was always the users, not a third party!
MA
Marjory
11 months ago
Each member organization is not the identity provider, that's incorrect.
MA
Macy
12 months ago
Wait, so the relying party is just the member organizations? Seems off.
FE
Felton
12 months ago
I think it's option D, sounds right to me.
JU
Judy
12 months ago
It's definitely a third party for identity provider!
CA
Carlee
1 year ago
I feel like option D makes the most sense, with the third party being the identity provider and the member organizations as the relying parties.
AI
Aimee
1 year ago
I’m a bit confused. Is the identity provider always a third party, or can it be one of the organizations too?
CO
Cory
1 year ago
I remember practicing a question like this, and I think the relying party is the one that relies on the identity provider for authentication.
FL
Flo
1 year ago
I think the identity provider is the trusted third party, but I'm not sure about the relying party. It feels like it could be the member organizations.
BE
Belen
1 year ago
Hmm, I'm a bit confused by this question. I'm not sure how the team member hierarchy type change would affect the existing targets. I'll need to think this through carefully.
KI
King
1 year ago
I'm feeling pretty confident about this one. The key is using the right tools for the right data - the NPSP Data Importer for program data and the Data Import Wizard for client data. Options A and B are the way to go.
ST
Stefania
1 year ago
I'm not too sure if Column would only provide specialized care. Feels like it could be a mix, but I might lean towards B being limited.
XO
Xochitl
1 year ago
I've got a good feeling about this one. The QEMU clue points to virtualized devices, so I'd say network devices and IoT/embedded devices are the way to go. Those are the most likely to have a comparable response to the one described in the question.
AL
Alesia
1 year ago
I remember discussing how primary data can be costly, and that could definitely be a downside.