you have described a typical simple transactional replication scenario, so this sounds like your best bet.

log shipping will make the mumbai db unusable whilst the log so being loaded, so unless you don't mind mumbai users being kicked off when logs are restored this is out.

snapshot off of a mirrored databases could be done, it all depends on latency you require, If you want minimal latency then transactional replication is way to go.

If you are happy with mumbai data being say a day old then you have many options:

snaphot replication daily

snaphot of a mirrored database

log shipping but restore all logs once a day

restore a full database backup nightly

of those restore a full backup nightly is the simplest and the way I would go, setting the db to read_only in mumbai.

If using replication remember there are limitations such as having a primary key on all replicated tables.