Backend interview prep

Start

Spring Data JPA Auditing Interview Questions and Answers

Master Spring Data JPA Auditing with interview questions covering @CreatedDate, @LastModifiedDate, @CreatedBy, @LastModifiedBy, AuditorAware, @EnableJpaAuditing, auditing lifecycle, and production best practices.

Introduction

Most enterprise applications must track who created a record, when it was created, who modified it, and when it was modified.

Examples include:

  • Banking transactions
  • Customer accounts
  • Insurance claims
  • Employee records
  • Healthcare systems
  • Financial audits

Without auditing, developers must manually populate audit fields in every service method.

Spring Data JPA provides Auditing to automate this process.

Typical audit information includes:

  • Created Date
  • Last Modified Date
  • Created By
  • Last Modified By

Spring Data JPA Auditing Architecture

flowchart LR

Application --> Repository

Repository --> Auditing

Auditing --> Hibernate

Hibernate --> Database

Q1. What is Spring Data JPA Auditing?

Answer

Spring Data JPA Auditing automatically maintains audit information for entities.

Instead of manually setting timestamps and usernames,

Spring updates audit fields automatically during persistence operations.

Benefits

  • Less boilerplate code
  • Consistent audit information
  • Easier compliance
  • Better maintainability

Q2. How do you enable Auditing?

Enable auditing using

@EnableJpaAuditing

Example

@Configuration

@EnableJpaAuditing

public class

JpaConfig{

}

This activates Spring Data JPA auditing support.

Q3. What is @CreatedDate?

@CreatedDate stores the entity creation timestamp.

Example

@CreatedDate

private LocalDateTime

createdDate;

Spring automatically sets this field when the entity is first persisted.

Q4. What is @LastModifiedDate?

@LastModifiedDate stores the latest update timestamp.

Example

@LastModifiedDate

private LocalDateTime

lastModifiedDate;

The field is updated automatically whenever the entity changes.

Audit Timeline

flowchart LR

Create --> CreatedDate

Update --> LastModifiedDate

Q5. What are @CreatedBy and @LastModifiedBy?

These annotations track the current user.

Example

@CreatedBy

private String

createdBy;

@LastModifiedBy

private String

modifiedBy;

Spring retrieves the current user from an AuditorAware implementation.

Q6. What is AuditorAware?

AuditorAware supplies the current authenticated user.

Example

public class

AuditUser

implements

AuditorAware<String>{

    @Override

    public Optional<String>

    getCurrentAuditor(){

        return Optional.of(

        "admin");

    }

}

In production, this usually integrates with Spring Security.

Q7. How does Auditing work?

Workflow

  1. Entity is created or updated.
  2. Spring detects the lifecycle event.
  3. Auditing fields are populated.
  4. Hibernate generates SQL.
  5. Database stores audit values.

Auditing Flow

flowchart LR

Entity --> AuditingListener

AuditingListener --> CreatedDate

AuditingListener --> ModifiedDate

AuditingListener --> CreatedBy

AuditingListener --> ModifiedBy

AuditingListener --> Database

Q8. Can auditing be shared across entities?

Yes.

Create a base entity.

Example

@MappedSuperclass

public abstract

class AuditEntity{

}

Child entities inherit the audit fields.

Benefits

  • Reusability
  • Consistency
  • Less duplication

Q9. What are common auditing use cases?

Typical scenarios

  • Customer creation
  • Fund transfers
  • Loan approvals
  • Employee management
  • Compliance reporting
  • Regulatory auditing

Auditing is mandatory in many financial and healthcare systems.

Q10. Auditing Best Practices

Use Base Audit Entity

Share audit fields across entities.

Use LocalDateTime

Prefer Java Time API over Date.

Integrate with Spring Security

Retrieve authenticated users dynamically.

Keep Audit Fields Immutable

Never modify creation information after persistence.

Use Database Time Zones Consistently

Prefer UTC for distributed systems.

Banking Example

flowchart TD

CustomerService --> CustomerRepository

CustomerRepository --> Auditing

Auditing --> CreatedDate

Auditing --> CreatedBy

Auditing --> ModifiedDate

Auditing --> ModifiedBy

Hibernate --> PostgreSQL

Every customer record automatically stores complete audit information.

Common Interview Questions

  • What is Spring Data JPA Auditing?
  • How do you enable auditing?
  • What is @CreatedDate?
  • What is @LastModifiedDate?
  • What is @CreatedBy?
  • What is @LastModifiedBy?
  • What is AuditorAware?
  • How does auditing work?
  • Why use a base audit entity?
  • Auditing best practices?

Quick Revision

Annotation Purpose
@EnableJpaAuditing Enable auditing
@CreatedDate Creation timestamp
@LastModifiedDate Last update timestamp
@CreatedBy User who created the entity
@LastModifiedBy User who last modified the entity
AuditorAware Supplies current user
@MappedSuperclass Shared audit fields
EntityListener Updates audit fields
LocalDateTime Recommended timestamp type
UTC Preferred timezone

Auditing Lifecycle

sequenceDiagram
Application->>Repository: save(entity)
Repository->>Auditing Listener: Before Persist
Auditing Listener->>Entity: Set CreatedDate
Auditing Listener->>Entity: Set CreatedBy
Repository->>Hibernate: INSERT
Hibernate->>Database: Persist Entity
Database-->>Repository: Success
Application->>Repository: update(entity)
Repository->>Auditing Listener: Before Update
Auditing Listener->>Entity: Set LastModifiedDate
Auditing Listener->>Entity: Set LastModifiedBy
Repository->>Hibernate: UPDATE

Production Example – Banking Loan Management System

A banking application manages loan applications.

Requirements

  • Record who created the loan application.
  • Record when it was created.
  • Record every modification.
  • Track the employee approving or rejecting the loan.
  • Maintain complete audit history for regulatory compliance.

Implementation

@MappedSuperclass
@EntityListeners(AuditingEntityListener.class)
public abstract class AuditEntity {

    @CreatedDate
    private LocalDateTime createdDate;

    @LastModifiedDate
    private LocalDateTime lastModifiedDate;

    @CreatedBy
    private String createdBy;

    @LastModifiedBy
    private String lastModifiedBy;
}

The application implements AuditorAware<String> to retrieve the currently authenticated employee from Spring Security.

flowchart LR

LoanService --> LoanRepository

LoanRepository --> AuditingEntityListener

AuditingEntityListener --> AuditorAware

AuditorAware --> SpringSecurity

AuditingEntityListener --> Hibernate

Hibernate --> PostgreSQL

Every loan record automatically stores complete audit information without requiring manual coding in service methods.

Key Takeaways

  • Spring Data JPA Auditing automatically manages audit fields for entity creation and updates.
  • @EnableJpaAuditing enables auditing support for the application.
  • @CreatedDate and @LastModifiedDate automatically maintain timestamps.
  • @CreatedBy and @LastModifiedBy track the authenticated user responsible for changes.
  • AuditorAware integrates with authentication systems such as Spring Security to supply the current user.
  • A shared @MappedSuperclass is the recommended approach for common audit fields across multiple entities.
  • Use UTC and the Java Time API (LocalDateTime, Instant, or OffsetDateTime) for consistent timestamp management.
  • Auditing is essential for regulatory compliance, traceability, troubleshooting, and enterprise data governance.