Question 160
At Aspen Digital, a regulatory evidence review uncovers the following situation affecting client advisory systems and shared files: A partner consultant needs temporary collaboration in Microsoft 365 but is provisioned as an ordinary permanent internal employee. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity. This is the relevant proof because it tests whether the selected corrective action (Invite the collaborator through the appropriate Microsoft Entra external guest identity workflow) addressed the initiating problem (A partner consultant needs temporary collaboration in Microsoft 365 but is provisioned as an ordinary permanent internal employee) in Aspen Digital's client advisory systems and shared files environment, not merely whether a task was marked complete.
Incorrect Answers
An expired collaboration entitlement no longer permits a partner sign-in while approved external users retain access. This is useful evidence for a different situation (An external collaboration project requires automatic partner access removal but has no guest identity governance owner) and action (Establish guest account ownership, appropriate expiry and periodic access review in Entra). For the reported issue at Aspen Digital, it does not establish the required outcome: The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity.
A replacement compute resource uses the same authorized identity without creating a new embedded credential. This is useful evidence for a different situation (A cloud deployment recreates its compute resource every day but needs a workload identity that persists independently of that resource) and action (Use a user-assigned managed identity when the identity needs an independent lifecycle across supported resources). For the reported issue at Aspen Digital, it does not establish the required outcome: The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity.
The trusted pipeline gets only its configured permissions and an untrusted token issuer fails the exchange. This is useful evidence for a different situation (A CI pipeline exchanges external workload tokens with Entra by uploading a reusable password into each build job) and action (Configure supported workload identity federation for token trust instead of embedding reusable pipeline secrets). For the reported issue at Aspen Digital, it does not establish the required outcome: The external account is recognizable as a guest and its access can be reviewed or withdrawn without altering the partner's home identity.