CCSP Cloud Application Security Practice Question
A company wants to enforce that all API calls to its cloud services are authenticated and authorized. Which design pattern should be implemented?
⚠ Common exam trap
Watch out — candidates often confuse authentication (verifying identity) with authorization (granting permissions) and choose a method like API keys or basic auth that only authenticates, failing to address the authorization requirement explicitly stated in the 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
✓
Implement OAuth 2.0 with scopes
OAuth 2.0 with scopes is the correct design pattern because it provides a standardized, token-based authorization framework that allows fine-grained access control to API resources. Scopes define specific permissions (e.g., read, write) and are validated by the resource server, ensuring that each API call is both authenticated (via the access token) and authorized (via the scopes). This aligns with the principle of least privilege and is widely adopted for securing cloud APIs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Implement OAuth 2.0 with scopes
Why this is correct
OAuth 2.0 with scopes satisfies the requirement by issuing access tokens that carry granular permissions, letting the resource server validate both caller identity and the specific operations each token authorises. Scopes constrain what an authenticated client may do, delivering authentication and fine-grained authorisation for every API call without exposing credentials.
- ✗
Use API keys with IP whitelisting
Why it's wrong here
Static API keys with IP whitelisting authenticate the calling host, not the user or application, and keys are long-lived bearer credentials vulnerable to replay if leaked. OAuth 2.0 with scoped tokens is the correct pattern when per-caller authorisation and delegated access must be enforced.
- ✗
Allow basic authentication over HTTPS
Why it's wrong here
Basic authentication transmits reusable username and password credentials on every call, providing authentication but no scoped, revocable authorisation. OAuth 2.0 token-based authorisation is required when granular permissions and delegated access must be enforced across API consumers.
- ✗
Use shared secrets with HMAC
Why it's wrong here
Shared secrets with HMAC verify message integrity and origin for a pre-shared key holder, but cannot express per-user authorisation scopes or support revocation. OAuth 2.0 with bearer tokens is the pattern when authenticated, authorised access must be enforced per API consumer.
Go deeper
Related to this question
About these practice questions
This CCSP question is part of Courseiva's 934-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CCSP 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 CCSP exam.