Is a Non-Repeatable Read possible when using the Read Committed isolation level?

Yes, a Non-Repeatable Read situation is possible at the Read Committed isolation level.

Read Committed guarantees that a transaction only sees committed changes but does not protect against data read at the start of the transaction being changed by other transactions before it completes.

Example of Non-Repeatable Read:

1. Transaction A reads a row from the database.
2. Transaction B modifies this row and commits the changes.
3. Transaction A reads the same row again and sees the modified data.

Thus, data within a single transaction can change between reads, which is called a Non-Repeatable Read.