Secondary node should not synchronize its local collections with Primary node in ReplicaSet

Scenario - I have created one primary node (with priority 2) and one secondary node (with priority 0). So I want a way, where my updates from the secondary node should not synchronize with the primary node but any crud operations in collections from the primary node should synchronize with the secondary node.

problem - When I am updating some record in the secondary node, that newly updated collection is also synchronized in the primary node, which is not expected(but somehow it is updating the primary node too). Is there any other way that my secondary node should only get updated with changes in the primary node but the reverse scenario should not happen?

How can I get this case implemented? Is this case really possible to implement?