You think about it right. From the doc:
Changed in version 2.6: Indication of a problem with a record containing j: true for mongod or mongos working with the --nojournal parameter causes an error. Previous versions would ignore j: true.
You can only assume that you get some kind of error when you try to configure it as described.
source share