40. A third-party service can act in several customers' cloud accounts. How should each customer relationship remain distinct?
HardIdentity & access
Technical
Show model answer
Require the service to establish the intended customer context through the provider's supported delegation controls and narrowly scoped trust. A service identity alone may not distinguish which customer authorized a particular request.
Bind role selection and resource access to that verified relationship, log attributable activity and test that one customer's configuration cannot select another customer's authority. Avoid inventing a custom secret-sharing mechanism when a supported delegation pattern exists.
What interviewers listen for
- Bind delegation to the intended customer
- Restrict role and resource scope
- Test cross-customer authority separation