File share witness.

I have read that Disk witness is   compared to File share witness.

Consider a scenario of a two-node cluster: node A and node B. If Node A goes down, then Node B carries on running and makes updates to the cluster database, such as new resources added. It would update the timestamp of the Witness.log on the  witness.

Then Node B goes down and Node A tries to start. Node A would see the timestamp is in advance of its own database and realize its cluster database is stale, and so wouldn't start the cluster service. This prevents partition-in-time occurring, since Node A is out-of-date, which is a good thing, as you don't want the cluster to start out of date (that would mean different cluster states on different nodes). You can't start the cluster without Node B coming back or forcing quorum on Node A.

We are using one primary and one secondary (synchronous with read-only) and the other node is with Asynchronous which is at AWS.Since AWS is multi-site we have to use File share witness as we can't use disk witness for multi sites.

As per above the scenario,when the cluster fails,If we want to bring it back to node A  we may face an issue.

How the cluster works at that time?