The answer is to configure branch protection rules in GitHub to require status checks, use secure variables in Azure DevOps, and enable secret scanning for your repositories. These three actions form a layered defense: branch protection enforces mandatory reviews and passing builds before merging, secure variables prevent sensitive data from being exposed in pipeline logs, and secret scanning automatically detects leaked credentials like API keys or tokens. On the Microsoft Cybersecurity Architect exam, this scenario tests your understanding of DevSecOps integration, often appearing in case studies where you must choose controls that balance security with developer velocity. A common trap is selecting options that disable code review or elevate pipeline privileges, which directly contradict least-privilege principles. Remember the mnemonic “BSS” for Branch protection, Secure variables, and Secret scanning—these three pillars ensure your CI/CD pipeline remains resilient against unauthorized changes and credential leaks.
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.
Which THREE actions should you take to secure a CI/CD pipeline using Azure DevOps and GitHub?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable secret scanning in GitHub to detect leaked credentials
Options A, D, and E are correct. Using secure variables, branch protection rules, and secret scanning are key security measures. Option B is wrong because disabling code review reduces security. Option C is wrong because running pipelines with admin privileges increases risk.
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.
✓
Enable secret scanning in GitHub to detect leaked credentials
Why this is correct
Secret scanning helps prevent accidental exposure of secrets in repositories.
Related concept
Authentication checks who the user is.
✗
Run all pipeline tasks with administrative privileges
Why it's wrong here
Running with admin privileges increases the attack surface.
✗
Disable pull request code reviews to speed deployment
Why it's wrong here
Disabling code reviews reduces security by allowing unreviewed code to be deployed.
✓
Store secrets in Azure Key Vault and use variable groups linked to Key Vault
Why this is correct
This ensures secrets are not hardcoded in pipeline definitions.
Related concept
Authentication checks who the user is.
✓
Configure branch protection rules in GitHub to require status checks
Why this is correct
Branch protection rules ensure that code meets quality and security checks before merging.
Related concept
Authentication checks who the user is.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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: Enable secret scanning in GitHub to detect leaked credentials — Options A, D, and E are correct. Using secure variables, branch protection rules, and secret scanning are key security measures. Option B is wrong because disabling code review reduces security. Option C is wrong because running pipelines with admin privileges increases risk.
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.