My response was in the Memory Mode context. It doesn't matter what mode Intel Optane PMem is operating in (Memory Mode, App Direct, or Mixed), it is a non-volatile media that retains the data written to it. Memory Mode volatility is achieved by generating new encryption keys at power-on or reboot time. Hence, it appears to the observer to operate like volatile DRAM. The alternative would be to have the BIOS zero the entire memory address range, which could take hours on very large memory systems, and nobody wants a system reboot time that long. There's really not much difference between Memory Mode and AppDirect from a PMem operational perspective. Either we automatically rotate the encryption keys (Memory Mode) or we don't (App Direct). The memory address layout of DRAM and PMem is handled by training the memory controller using the requested goal configuration.
The same principle applies to disks. If I create a file system on a disk, write some data to it, then re-create the file system, the data I previously wrote initially appears to be gone at the file system level, but I can trivially access the old data by reading the contents of the raw disk. However, if I encrypted the disk, create a file system, write data, then re-encrypted the disk with new keys, and finally create a new file system, there's no way I could access the previously written data.
HTH
Steve