Hi @Chumnan_Pearpiw welcome to the community!
There’s no special requirements for an arbiter; they’re basically a node that helps with election voting, but do not store data like a normal secondary. Therefore all the requirements & recommendations put forth in the replica set connectivity page applies equally to secondaries as well as arbiters. Basically it boils down to: as long as all parts of a replica set can contact each other, it’s a valid configuration.
Having said that, if this is your first MongoDB deployment, I would bring your attention to possible performance issues with arbiters. MongoDB 5.0 changes the default write concern setting to “majority” from the old default of
w:1 in the past. While considerations are still being made with the presence of arbiters, in many cases it’s best to use a normal secondary node since it provides you with much better consistency guarantees and availability.