What is true about the client identifier?

Question

Options

• AThe client Identifier is automatically included In the audit trail.
• BThe client Identifier is automatically set by the SQL-Net layer.
• CA session can have multiple client Identifier values set simultaneously.
• DThe client Identifier cannot be changed during the session.

• A
  3% (1)
• B
  94% (32)
• D
  3% (1)

Explanation

Option B is correct because Oracle's SQL*Net (Oracle Net Services) layer automatically populates the CLIENT_IDENTIFIER attribute when a client establishes a connection, carrying client-side identity information through the network layer without requiring explicit application code to set it.

Why the distractors are wrong:

• A is false - the client identifier does not appear in the audit trail automatically; it must be explicitly configured via unified auditing policies or DBMS_AUDIT_MGMT to be captured.
• C is false - a session holds exactly one client identifier value at any given time; calling DBMS_SESSION.SET_IDENTIFIER overwrites the previous value, it does not stack them.
• D is false - the client identifier can be changed mid-session using DBMS_SESSION.SET_IDENTIFIER, which is precisely why it's useful in connection-pooling scenarios where a single session serves multiple application users.

Memory tip: Think of SQL*Net as the "automatic doorbell" - when a client knocks on the database door, SQL*Net announces who is there by tagging the session with a client identifier before you even write a line of application code.

No community discussion yet for this question.