Question 225 of 529
Software Development SecurityhardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to use attribute-based access control (ABAC) with service-specific policies. ABAC minimizes the risk of privilege escalation in microservices by evaluating fine-grained attributes—such as user identity, resource sensitivity, and environmental context—to grant permissions dynamically, which inherently limits the blast radius if a single service is compromised. In contrast, role-based access control (RBAC) with broad, global roles is too coarse for microservices, as a compromised service inherits all permissions tied to its role, enabling lateral movement. On the Certified Information Systems Security Professional CISSP exam, this question tests your understanding of access control models in distributed architectures, often appearing as a scenario where you must choose between granularity and simplicity. A common trap is selecting RBAC for its administrative ease, but remember that in microservices, “attributes shrink the blast radius, roles expand it.” Memory tip: ABAC = “Always Be Attribute-Checking” to contain privilege creep.

CISSP Software Development Security Practice Question

This CISSP practice question tests your understanding of software development security. 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.

A security architect is reviewing the access control model for a microservices architecture. Which approach minimizes the risk of privilege escalation from a compromised service?

Question 1hardmultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Use attribute-based access control (ABAC) with service-specific policies.

ABAC uses attributes (user, resource, environment) to grant fine-grained permissions, reducing the blast radius if a service is compromised. RBAC with global roles is too coarse. SSO does not address service-to-service. API keys are weak for authentication.

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 attribute-based access control (ABAC) with service-specific policies.

    Why this is correct

    ABAC allows context-aware, fine-grained policies to limit escalation.

    Related concept

    Authentication checks who the user is.

  • Implement role-based access control (RBAC) with global roles.

    Why it's wrong here

    Global roles are too coarse and may grant excessive privileges.

  • Use API keys for all service-to-service communication.

    Why it's wrong here

    API keys are vulnerable to theft and do not provide granular authorization.

  • Deploy a single sign-on solution.

    Why it's wrong here

    SSO addresses user authentication, not service-to-service authorization.

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 developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.

What to study next

Got this wrong? Here's your next step.

Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related CISSP questions on access control and AAA configuration.

Related practice questions

Related CISSP practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free CISSP practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this CISSP question test?

Software Development Security — This question tests Software Development Security — Authentication checks who the user is..

What is the correct answer to this question?

The correct answer is: Use attribute-based access control (ABAC) with service-specific policies. — ABAC uses attributes (user, resource, environment) to grant fine-grained permissions, reducing the blast radius if a service is compromised. RBAC with global roles is too coarse. SSO does not address service-to-service. API keys are weak for authentication.

What should I do if I get this CISSP 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 CISSP 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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

This CISSP practice question is part of Courseiva's free ISC2 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 CISSP exam.