Question 420
A user presents decentralized identity claims and the business wants trustworthy verification. What outcome proves the design enforces the requested boundary?
Explanation
Correct Answer
A correct test must show that an untrusted issuer's otherwise plausible credential is rejected. The underlying reason is Decentralized identity requires trusted issuer verification and proof validation.
Incorrect Answers
That test would support a different case: A guest invitation is accepted but a cross-tenant access policy still denies application access. Cross-tenant policies can restrict collaboration independently of invitations. The present control must instead show that an untrusted issuer's otherwise plausible credential is rejected.
The proposed evidence relates to another situation: A partner's project access should expire when the project closes despite the tenant keeping the guest identity. External access lifecycle should not rely solely on manual offboarding. The architect needs verification that an untrusted issuer's otherwise plausible credential is rejected.
This observation evaluates An external consulting team must reach a specific application without receiving internal employee identities. B2B authorization supports external collaboration without broad internal accounts. It does not establish the required result: an untrusted issuer's otherwise plausible credential is rejected.