Setup standalone with all the data from cluster, mongodb
As per MongoDB documentation Replica Set Arbiter An arbiter does not have a copy of data set and cannot become a primary. Replica sets may have arbiters to add a vote in elections for primary. Arbiters always have exactly 1 election vote, and thus allow replica sets to have an uneven number of voting members without the overhead of an additional member that replicates data.


  Changed in version 3.6: Starting in MongoDB 3.6, arbiters have
  priority 0. When you upgrade a replica set to MongoDB 3.6, if the
  existing configuration has an arbiter with priority 1, MongoDB 3.6
  reconfigures the arbiter to have priority 0.


Primary with a Secondary and an Arbiter

A three member replica set with a two members that store data has:

One primary.
One secondary member. The secondary can become primary in an election.
One arbiter. The arbiter only votes in elections.


Since the arbiter does not hold a copy of the data, these deployments provides only one complete copy of the data. Arbiters require fewer resources, at the expense of more limited redundancy and fault tolerance.