Course Test

Please answer the questions below to complete the test.

Question 1

What is the correct mesheryctl command to import a Kubernetes manifest file named designs/microservices-demo.yaml?

Select one answer

mesheryctl design apply -f designs/microservices-demo.yaml

mesheryctl design import -f designs/microservices-demo.yaml -s "Kubernetes Manifest"

mesheryctl system import designs/microservices-demo.yaml

mesheryctl design upload --file designs/microservices-demo.yaml

Question 2

In the agent deploy loop, the human-in-the-loop checkpoint occurs between which two stages?

Select one answer

Between design generation and Git commit

Between Git commit and cluster apply, during the dry-run review

After cluster apply, during rollout monitoring

Before design generation, as a requirements sign-off

Question 3

Which of the following conditions should an agent use as pre-defined rollback triggers?

Select all that apply

Rollout does not complete within the expected time window

Application error rate rises above the defined threshold shortly after apply

A single pod restarts once during the rollout

One pod is in Pending state on a newly added node

Question 4

What tool does kubectl diff compare to produce its output?

Select one answer

The Git HEAD version of the file against the incoming manifest

The live cluster state against the incoming manifest

The Meshery design registry against the Kubernetes API server

The previous Deployment revision against the new one

Question 5

Why should kubectl rollout undo NOT be used as the sole rollback mechanism in a GitOps workflow?

Select one answer

It is slower than a Git revert and re-apply

It does not work on Deployments that use rolling update strategy

It restores cluster state but does not update the Git source of truth, creating a gap

It requires Meshery Operator to be running and will fail if MeshSync is down

Question 6

What information should an agent record after a successful deployment to make future rollbacks deterministic?

Select all that apply

The Git commit hash of the deployed design file

The Meshery Design ID returned after import

The rollout status for each Deployment

The names of all engineers who reviewed the dry-run diff