Exam Associate Cloud Engineer topic 1 question 240 discussion

Here's why option D is the most appropriate: ->Compute Engine: Compute Engine provides virtual machines (VMs) that closely resemble traditional on-premises servers. It allows you to migrate your existing application as-is to the Google Cloud platform. ->Instance Scheduling: You can schedule the VM instance to start and stop at specific times, such as midnight, to align with your existing processing schedule. This ensures that the application runs at the required time, similar to the on-premises setup. ->Minimal Effort and Cost: The "lift and shift" approach minimizes the need for code modifications or containerization, reducing migration complexity. It also allows you to use the same binaries and configurations as your on-premises setup, saving development effort. You only pay for the VM's compute resources when it's running, making it cost-effective.

This one is a tough one. Ill consider this in my answers: Cost --> Both are more the same (the process will run at the same frequency) Effort --> Create the image in A takes more effort then to option D. With this in mind ill choose D. (before i was choosing A).

Pretty easy, containers designed for something light, 1gb-16gb is not light minimal effort -> lift and shift

D - perfect solution, but expensive! Cloud run maximum execution limit time 60 mins (very close to the 45 mins..risky!) The maximum execution limit time for the cloud function is 9 mins (less than 45)

For my 2c I think I would have selected A, but D is a possibility. A because in the long run Cloud Run should cost less than D I believe, as it would take less CPU time through a period of time if data is from 1-16GB. D could be because it potentially requires "less" effort compared to CR.

I think the answer is C. Cloud Run is ideal for applications that have short running times and variable workloads, like this data analytics application. Also, Lifting and shifting the application to a VM on Compute Engine would require to manage the VM by a person, including tasks like patching the operating system, managing security updates, and scaling the VM. This is more effort than using Cloud Run.

I vote for D.

D is the correct answer.

D is the correct answer as it requires the minimoal effort

A is correct answer.

minimal effort is to lift and shift to VM minimal cost is to use schedule to start and stop the instance

Things to consider: 1. can cloud functions run binary file? 2. Data file size varies from 1 to 16 GB. so how to determine the VM spec?

i've made mistake, should be D

lift and shift is less effort and cost, you don't have to pay for refactoring or creating image.

I would choose D because I want to migrate this application to Google Cloud with minimal effort and cost. Cloud Run requires to create a container image and this means some kind of development and testing.

A seems to be the less disruptive solution with lower costs