C . Had something like this in a mock, and DMS (option C) was correct for MySQL migrations with tight downtime and secure transit. BigQuery Data Transfer isn’t meant for this kind of DB migration, and batch insert would be disruptive. Not 100% but feels right here.
Does "minimal disruption" mean zero downtime, or is a short maintenance window acceptable? That could change if Database Migration Service (C) is the clear choice, since it supports continuous replication for near-zero downtime migration.
I don’t think it’s B or D. The real key is the service account, since that’s what actually does the API call to BigQuery when the job runs. Attaching IAM to the project or instance group would be too broad and not follow least privilege. Bit of a common trap, but C is right from what I know. If someone disagrees, curious to hear their reasoning!
I think D fits best since PAYG is flexible and saves cost when the servers aren't running all week. BYOL (C) is more for cases where you have long-term licenses or compliance needs. I think some people get tripped up thinking you must reuse licenses, but that's not required here. Disagree?
I think it's Cloud Vision API since that's the one for image object detection. BigQuery ML and AutoML Tables are more for structured data, not images. Not totally sure if AutoML Video could do images too but pretty sure C fits best here. Agree?
I think A makes more sense here, since preemptible instances are much cheaper and work well when your jobs can handle interruptions. The workload isn't tied to SLAs and each scene is under 12 hours, so preemptibles fit perfectly. Not totally sure though if D would ever beat A unless there's a strict job concurrency need. Agree?
Why do Google always give these cheesy migration names? Realistically, with a year left on the datacenter lease, wouldn't you want to modernize your stuff on-prem first rather than just tossing everything straight into GKE? Or is there some use case where you'd still go for C or D here?
Yeah B is the one. Since they've got the datacenter lease covered for another year, they can take their time to modernize VMs to containers on-prem first, then move later. Less pressure and lets them improve before migrating. Pretty sure that's what "Improve and Move" is aiming for here.
C or D for me. Since the team only has basic ML skills, I was thinking Cloud SQL (D) might be the right fit because it's database-oriented and familiar to them. But reading closely, just having a database doesn't help with ML modeling directly, so maybe C (TensorFlow) is better if they want to actually build models. Not totally confident though-anyone see it differently?
I don't think it's D. Cloud SQL is just a managed database, doesn't actually let you build ML models within SQL itself. BigQuery ML seems like a trap here, but I get why folks mix them up since both involve SQL skills. Anyone else see it different?