What use cases are available for a Local Identity Directory? Note: There are 3 correct answers to this question.

Question

Options

• AMerging attributes
• BClassic use case
• CHybrid mode
• DProxy mode
• ES/4HANA use case

• A
  9% (2)
• B
  82% (18)
• E
  9% (2)

Explanation

A Local Identity Directory in SAP Cloud Identity Services (IAS) supports three primary deployment/configuration patterns: Classic mode (B), where IAS acts as the sole identity provider using only its local user store; Hybrid mode (C), which combines local users with federated users from corporate identity providers; and Proxy mode (D), where IAS forwards authentication to an upstream corporate IdP while still leveraging the local directory for user data and provisioning.

Option A (Merging attributes) is a feature/capability within these modes, not a standalone use case for the Local Identity Directory itself. Option E (S/4HANA use case) refers to a target application, not a recognized architectural use case category - S/4HANA can be integrated under any of the three valid modes.

Memory tip: Think of the three use cases as how IAS positions itself - it can stand alone (Classic), share the load (Hybrid), or step aside (Proxy). That's a deployment posture, not a feature (ruling out A) or a target system (ruling out E).

No community discussion yet for this question.