DRBD diskless quorum vs DRBD "handlers" and "fencing" in two-node Pacemaker storage metro-cluster

DRBD
1

Hello

There is two-node shared-nothing DRBD-based sync replication active/standby Pacemaker storage metro-cluster.
DRBD replication links are directly (no switch) connected.
Configuration with Corosync quorum and DRBD diskless quorum are running on additional qdevice host.
Heuristics (parallel fping) and STONITH/fencing - fence_ipmilan and diskless sbd (hpwdt, /dev/watchdog).

Data consistency and integrity is absolute priority during any node/network breaks.

In such setup, should I add to DRBD resource files “handlers” and “fencing”,

handlers {
      fence-peer "/usr/lib/drbd/crm-fence-peer.9.sh";
      unfence-peer "/usr/lib/drbd/crm-unfence-peer.9.sh";
    }

and

fencing resource-and-stonith; or fencing resource-only

Or is it unnecessary and may even be counterproductive ?