What is required to centrally administer a user's master record using Central User Administration? Note: There are 3 correct answers to this question.

Question

Options

• AAn ALE distribution model
• BAn RFC destination to the target system
• CAn RFC destination to the target client
• DAn existing master record in the target client for the user
• EAn entry in transaction BD54 for the child system

• A
  85% (34)
• B
  10% (4)
• D
  5% (2)

Explanation

Central User Administration (CUA) relies on ALE (Application Link Enabling) technology to distribute user master records, so an ALE distribution model (A) is mandatory - it defines what data gets sent and to which child systems. Communication with a child system happens at the client level in SAP (a system can host multiple clients), so an RFC destination to the target client (C) is required, not merely to the system. Finally, an entry in BD54 (E) registers the child system as a logical system, which ALE requires to identify and address distribution targets.

Why B is wrong: An RFC destination to the "target system" is too broad - SAP operates on clients, and CUA needs connectivity to a specific client, making C the correct granularity. B and C sound similar but differ at the system vs. client level.

Why D is wrong: CUA's entire purpose is to create and maintain user records centrally and push them to child clients - no pre-existing record is needed in the target client. Requiring one would defeat the point.

Memory tip: Think "ACE" - ALE model (the blueprint), Client RFC (the pipe), Entry in BD54 (the address book). CUA needs to know what to send (A), know how to reach the right client (C), and know the child system's logical name (E).

No community discussion yet for this question.