nerdexam
IBM

C1000-141 · Question #37

What must an Attribute be in order for it to be audit enabled?

The correct answer is B. Persistent. Persistent attributes store their values in the database, which is a prerequisite for audit logging - you can only track changes to data that is actually saved. An attribute must be Persistent (B) because the audit mechanism records before-and-after values of stored data; if…

Application Configuration

Question

What must an Attribute be in order for it to be audit enabled?

Options

  • ARequired
  • BPersistent
  • CUser Defined
  • DNon-persistent

How the community answered

(43 responses)
  • A
    5% (2)
  • B
    84% (36)
  • C
    2% (1)
  • D
    9% (4)

Explanation

Persistent attributes store their values in the database, which is a prerequisite for audit logging - you can only track changes to data that is actually saved. An attribute must be Persistent (B) because the audit mechanism records before-and-after values of stored data; if nothing is persisted, there is no record to audit.

Why the distractors are wrong:

  • A (Required): Whether a field is mandatory has no bearing on whether its changes can be tracked - optional fields can be audited too.
  • C (User Defined): System-defined attributes can also be audit-enabled; the creator of the attribute does not determine audit eligibility.
  • D (Non-persistent): This is the opposite of correct - non-persistent attributes exist only in memory and are never written to the database, making it impossible to maintain an audit trail.

Memory tip: Think "Persist to Audit." If data isn't saved to the database (persisted), there's nothing for the audit log to capture. Non-persistent = no storage = no audit.

Topics

#audit trail#persistent attributes#attribute configuration#database auditing

Community Discussion

No community discussion yet for this question.

Full C1000-141 Practice