A thrush-hollow partner product should not auto-issue keys when someone clicks Subscribe. What product setting should the developer enable?
Select an answer to reveal the explanation.
Short Explanation
Don’t auto-hand out thrush-hollow keys—set the product so an administrator must approve the subscription first.
Full Explanation
When a thrush-hollow partner product must not auto-issue keys on Subscribe, enable subscription approval so an administrator reviews and approves the request before a key is issued. That product-level setting gates partner onboarding, lets staff verify contracts or billing status, and avoids uncontrolled key sprawl without rewriting every backend.
Entra Conditional Access on every backend Function may strengthen identity posture for signed-in users but is not the APIM product setting that stops automatic key issuance at subscribe time on the developer portal. Automatic subscription approval for all portal guests is the opposite of the requirement and hands out keys immediately. Anonymous access with no product subscription removes the key-issuance control entirely and leaves the partner API open.
Exam caveat: approval is configured on the product—identity Conditional Access and APIM subscription approval solve different layers and are not interchangeable answers on the exam.
Operational check: set the thrush-hollow product to require subscription approval, submit a test Subscribe from the developer portal, confirm the subscription stays pending and the key is not usable until an admin approves, then approve and verify subsequent gateway calls succeed.