For this question, refer to the Dress4Win case study. Considering the given business requirements, how would you automate the deployment of web and transactional data layers?
A.
Deploy Nginx and Tomcat using Cloud Deployment Manager to Compute Engine. Deploy a Cloud SQL server to replace MySQL. Deploy Jenkins using Cloud Deployment Manager.
B.
Deploy Nginx and Tomcat using Cloud Launcher. Deploy a MySQL server using Cloud Launcher. Deploy Jenkins to Compute Engine using Cloud Deployment Manager scripts.
C.
Migrate Nginx and Tomcat to App Engine. Deploy a Cloud Datastore server to replace the MySQL server in a high-availability configuration. Deploy Jenkins to Compute Engine using Cloud Launcher.
D.
Migrate Nginx and Tomcat to App Engine. Deploy a MySQL server using Cloud Launcher. Deploy Jenkins to Compute Engine using Cloud Launcher.
agreed, A. For those saying C, the question is about "automating the deployment" in line with the business requirements. Going from MySQL to datastore might be a good idea long term, but it won't make automating the deployment to the cloud any easier or smoother. Automate the deployment to Cloud SQL because it's a natural fit, and once that's working, re-assess the requirements to decide if it's worth the hefty lift of shifting from MySQL to a NoSQL Document DB.
The requriements also specify:
"Easily create non-production environment in the cloud.
Implement an automation framework for provisioning resources in cloud.
Implement a continuous deployment process for deploying applications to the on-premises datacenter or cloud."
So A is better.
Not A, B - I would not deploy Jenkins with Deployment Manager, if I can do so with Cloud Marketplace (new name of Cloud Launcher, follow https://cloud.google.com/launcher/).
Not C - you cannot replace a relational DB with Datastore
Check if D makes sense - migrate to App Engine is "optimize architecture for performance in the cloud", MySQL is in Cloud Marketplace (I would choose Cloud SQL even if I had to take 16 vCPU to get 128 GB) and Jenkins is also in Cloud Marketplace
Thinking about it a second time: If the business requirements are a distraction and the scope of the case study (""For the first phase of their migration to the cloud, Dress4Win is moving their development and test environments. They are not sure which components of their architecture they can migrate as is and which components they need to change before migrating them.") is more relevant, then it's A. You can deploy Nginx, Tomcat, Jenkins with Cloud Deployment Manager (even if it's not the best idea) and it fit's the scenario of only creating dev and test environments more or less identical to on-prem prod. The question is strange.
For me is D:
- Deploy NGINX and and Tomcat to App Engine, so both can scale up and down automatically
- Deploy MySQL server using Cloud Launcer (nowadays called Marketplace)
- Deploy Jenkins to Compute Engine using Cloud Launcher (nowadays called MarketPlace): Here literally they are choosing an instance (a compute instance to do so through MarketPlace) https://cloud.google.com/architecture/using-jenkins-for-distributed-builds-on-compute-engine.
Answer A can not be. it talks about SQL Server, why to bring that? Plus the way they want ton tackle Jenkins installation makes no sense if you already have MarketPlace. Also I'm ok that compute instances for NGINX and Tomcat could fit, BUT it doesn't talk about MIG or not MIG. It is not ensuring right declaration to have MIG and scale them up down through it will be in place.
Answer is D.
A. Deploy Nginx and Tomcat using Cloud Deployment Manager to Compute Engine. Deploy a Cloud SQL server to replace MySQL. Deploy Jenkins using Cloud Deployment Manager.
D. With produciton parity, you cant replace MySQL with 128 GB of memory with Cloud SQL as there is no such image available. I have checked it. MySQL has to go on GCE with PD
I would go for either go for B or D.
D is better because it is scalable better than B as B has no details if it is going to use MIG or just fleet of tomcat servers for web apps.
I think B is a valid response, please check:
https://cloud.google.com/blog/products/it-ops/google-cloud-launcher-simplifies-running-third-party-apps-in-the-cloud
and
https://medium.com/@PeetDenny/automated-provisioning-of-jenkins-on-google-cloud-c297b2e0be2
the question and the answers are so confusing. what is "Cloud Launcher"? Never heard of it.
Only A does not mention that launcher thingy. I can only choose A.
After reading the question more and kind of linking back to question one, i think it's asking how to "automate the deployment" of web and transactional data layers". In that case, I think focus on deployment automation of existing technology might be a better than mapping new cloud technology in this case? so, A might be a better fit?
the answer is A because datastore is nosql db and in business requirements it is clarly sais that improve bussiness agility and speed innovation through rapid provisoning of new ressources
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
jcmoranp
Highly Voted 4 years, 3 months agonitinz
2 years, 11 months agocetanx
3 years, 6 months agotartar
3 years, 5 months agoJphix
3 years agoEroc
Highly Voted 4 years, 3 months agoSSQX
3 years, 10 months agoAyzen
3 years, 9 months agouser263263
Most Recent 1 week, 1 day agouser263263
1 week, 1 day agorrope
1 month, 1 week agotheBestStudent
1 month, 4 weeks agotuan072090
4 months, 3 weeks agojoe2211
2 years, 2 months agovictory108
2 years, 6 months agoMamthaSJ
2 years, 7 months agogosi
2 years, 9 months agoAusias18
2 years, 10 months agovruizm
2 years, 11 months agobnlcnd
3 years agoWira
2 years, 10 months agopawel_ski
2 years, 10 months agoybe_gcp_cert
3 years agoybe_gcp_cert
3 years agoMndwsk
3 years, 1 month agoSKSKSK
3 years, 2 months agohomer_simpson
3 years, 3 months ago