The more likely explanation is that the person manually googled all the landmarks of Sydney to get some vector images to cut and paste into a CAD program to extrude, and accidentally got the wrong one.
Sad that it's acceptable to just take artwork from wherever and paste them all into a new design.
I say "wherever" because if they were paying attention to the licences of their sources they'd see the artwork was named for a landmark wasn't in Sydney.
Although I guess if the rights holder never knows about it, nobody is going to enforce the rights, probably hard to even prove it by the time its been shrunk and cast into metal.
Considering that they had to rework things to not use the master key, I can understand the time and effort. From TFA, the DB Gateway handled all Cosmos requests, and used the master key to get an account’s private key and then forward the DB requests. If they had to rearchitect that gateway system, I’m sure it was no small task. Bear in mind, they probably approached this somewhat seriously since Cosmos powers lots of internal M$ tools like Teams and Copilot, not just customer applications.
They patched the vulnerability within 2 days. They spent 6 months rearchitecting their backend. It's a major service for themselves and tens of thousands of customers, you don't vibe code yourself a new database query execution engine overnight.
There is a very high volume of them being posted every day, and they are a significant % of the total. Also, writing is hard, LLM articles can be slop whilst also being better written than average.
reply