You’ve identified errors in the logs for a specific Deployment, pinpointing the issue to the Pod named 'ad-generator'. Your team cannot replicate the error in other environments and believes that accessing the container directly for a brief period would help diagnose the root cause. What action should they take to run commands inside the container?

Real Exam

Execute the command kubectl run ad-generator /bin/bash to initiate a shell session within the container.

14.9%

Use the command kubectl exec -it -- /bin/bash to start a shell session on the container.

14.9%

Initiate a shell session on the container by running kubectl exec -it ad-generator -- /bin/bash.

61.4%

Launch a shell session on the container with the command kubectl run.

8.9%

Google Associate Cloud Engineer