i understand preemptible as a no-go because of "must be restarted if interrupted" here meaning "starting from scratch" . So C seems right

Preemptible will be perfect for a batch job that takes less than 24 hours. But it's not in this case.

Option C is correct, bcoz the job is running for more than 30 hours

Correct Answer is C

Job runs for 30 hours and must be restarted if interrupted are "indirectly proportional" to "Preemptible" Ans: C

Preemptible VMs are cheaper, but they will not be available beyond 24hrs

C is the correct answer, Install the workload in a compute engine VM, start and stop the instance as needed, because as per the question the VM runs for 30 hours, process can be performed offline and should not be interrupted, if interrupted we need to restart the batch process again. Preemptible VMs are cheaper, but they will not be available beyond 24hrs, and if the process gets interrupted the preemptible VM will restart.

C is the correct answer

The preemptible instance in GKE is same as Compute Engine Instance. They have same behavior that will be last for 24 hours. Also, see the key here "...and must be restarted if interrupted.". That means the job will start from the scratch again if the preemptible instance terminated. So, you will just wasted your preemptible instances because the job will never be finished. https://cloud.google.com/kubernetes-engine/docs/how-to/preemptible-vms#overview

Option D will achieve the goal here. If a preemptible VM goes down in 24 hours a new one will be built for running the batch process through the instance group configuration.

A preemptible VM is an instance that you can create and run at a much lower price than normal instances. However, Compute Engine might stop (preempt) these instances if it requires access to those resources for other tasks. Preemptible instances are excess Compute Engine capacity, so their availability varies with usage. If your apps are fault-tolerant and can withstand possible instance preemptions then preemptible instances can reduce your Compute Engine costs significantly. For example, batch processing jobs can run on preemptible instances. If some of those instances stop during processing, the job slows but does not completely stop. Preemptible instances complete your batch processing tasks without placing additional workload on your existing instances and without requiring you to pay full price for additional normal instances. Hence, the correct answer is: Build an instance template configured to launch a Preemptible VM. Provision a managed instance group (MIG) from the template you just created. Adjust the Target CPU Utilization setting.

A - D are not possible because: For example, preemptible VMs can only run for up to 24 hours at a time (https://cloud.google.com/compute/docs/instances/preemptible) I agree with C

The answer is C. Many people are saying D but this is incorrect. Preemptible instances are finite Compute Engine resources, so they might not always be available. If there is a long running job that must be restarted, it does not make sense to use preemptible VMs as if there are no resources available, we will not be able to even run or restart the job. Thus, C is correct.

auto restart not in Prem VM

It should be C Because a Preemptible VM can't run more than 24 hours

Answer is C - Since it is run on premise server, the expectation is to run it on Compute Engine. - Preemptible VMs are not an option as it runs for 24 hours only continuously. The batch job takes 30 hours and expects it to be restarted incase of interruptions. (Note it is restart & not resume)

If your apps are fault-tolerant and can withstand possible instance preemptions, then preemptible instances can reduce your Compute Engine costs significantly. For example, batch processing jobs can run on preemptible instances.