While making some changes to relocate our production standby database, I first set our primary log_archive_dest_state_2 to DEFER.
Then, i confirmed it was set as DEFER.

Next, I shutdown our standby database and relocated all of its files to new locations, alter the database for locations, and started it back up in mount mode.

Then, I went back to our primary database and attempted to reset the log_archive_dest_state_2 to ENABLE.
Even though it accepted my command, when I checked it, I found that the value was set to "RESET" (instead of ENABLE).

I confirmed logs were working normally and all was well with no gap.

I suspect this all has something to do with our DG Broker which is a lot more trouble than it is worth, especially since we don't use FSFO and we only have one Standby database.

Thank you. That sounds about as good of an answer as I can imagine.
I think since we are not using DG Fast Start Failover, there is not much advantage to using the DG Broker since we only have one standby database.
It causes more grief than it does benefit.
Thanks again.