The correct answer is to use a validate JWT policy to authenticate partners and a rate-limit by key policy to control request rates. This combination works because the validate JWT policy verifies the identity and claims of external partners through JSON Web Tokens, ensuring only authorized callers reach your APIs, while the rate-limit by key policy enforces per-subscriber or per-key request quotas to prevent abuse. On the Microsoft Cybersecurity Architect exam, this scenario tests your understanding of how Azure API Management policies enforce both authentication and throttling at the gateway level, often appearing as a distractor where subscription keys or OAuth alone are offered as simpler but insecure alternatives. A common trap is assuming subscription keys provide sufficient security—they do not, as they can be easily shared or stolen. Remember the mnemonic “JWT for who, key for how many” to keep the two policies distinct: validate JWT controls authorization, rate-limit by key controls usage.
SC-100 Practice Question: Design security solutions for applications and data
This SC-100 practice question tests your understanding of design security solutions for applications and data. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your organization uses Azure API Management (APIM) to expose APIs to external partners. You need to ensure that only authorized partners can access the APIs and that the API requests are rate-limited to prevent abuse. What should you implement?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a validate JWT policy to authenticate partners and a rate-limit by key policy to control request rates.
Option D is correct because APIM policies can validate JWT tokens for authorization and use rate limiting policy to control request rates. Option A is wrong because subscription keys alone are not secure for partner authentication. Option B is wrong because OAuth 2.0 with API keys is not standard; APIM supports OAuth via policies. Option C is wrong because Client certificates are another method but not combined with rate limiting as effectively as policy.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Use a validate JWT policy to authenticate partners and a rate-limit by key policy to control request rates.
Configure client certificate authentication and set a global rate limit in the APIM service.
Why it's wrong here
Client certs are secure but rate limit at service level is not granular per partner.
✗
Require a subscription key for each partner and configure IP whitelisting.
Why it's wrong here
Subscription keys are easily compromised; IP whitelisting is not flexible for partners.
✗
Use OAuth 2.0 tokens and store partner API keys in Azure Key Vault.
Why it's wrong here
OAuth 2.0 is good, but API keys are not standard with OAuth; APIM can validate tokens directly.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SC-100 question in full detail.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related SC-100 questions on access control and AAA configuration.
Design security solutions for applications and data — This question tests Design security solutions for applications and data — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Use a validate JWT policy to authenticate partners and a rate-limit by key policy to control request rates. — Option D is correct because APIM policies can validate JWT tokens for authorization and use rate limiting policy to control request rates. Option A is wrong because subscription keys alone are not secure for partner authentication. Option B is wrong because OAuth 2.0 with API keys is not standard; APIM supports OAuth via policies. Option C is wrong because Client certificates are another method but not combined with rate limiting as effectively as policy.
What should I do if I get this SC-100 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related SC-100 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SC-100 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SC-100 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.