The correct answer is A Kubernetes object that runs finite batch workloads until a specified number of pod runs succeed.

A Job creates one or more Pods that run to completion and it tracks successful pod terminations until the configured number of completions is reached. It is intended for finite batch tasks such as migrations, data processing, and one time work rather than for services that remain running.

The Job controller supports fields such as completions, parallelism and backoffLimit and it respects Pod restart policies like OnFailure or Never. When the required number of successful runs is achieved the Job is marked complete and it stops creating new Pods.

Cloud Run is a managed serverless container platform for running stateless services and it is not a Kubernetes object that manages finite batch pods. It is therefore not the correct choice for describing a Kubernetes Job.

A container image stored in a registry such as example.com describes an image artifact rather than a Kubernetes resource. A Job may use a container image to run its Pods but the image itself is not a Job.

A resource used to define a long running scalable service like a web frontend describes objects such as Deployments or Services and not a Job. A Job is for finite work and it does not manage ongoing scaled replicas in the same way a Deployment does.

Full AWS Practitioner Certification Question