When the node is restarted to replay all of the oplog entries up to the desired point-in-time, the oplog application will need to skip applying entries for collections not restored. An applyOps oplog entry can contain multiple oplog entries referencing multiple collections. This is how committed multi-document transactions are structured. Oplog entries on collections not restored will need to be skipped. The same needs to be done when foreign oplog entries are inserted.