The only explanation that I can think of for PCTFREE is in the case where concurrent transactions are attempting to make chnages to a data block, but the first transaction causes the block to dip below the PCTFREE parameter...so the second (or other) trasaction would then be prevented from INSERTING on the block. But again, this doesn't prevent UPDATES or DELETES...so those transactions could continue "concurrently".

Certainly not a very straight forward question based upon the answer choices!