KCNA Cloud Native Application Delivery Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Run `kubectl scale` deployment, then check pods are created, then verify deployment status, then monitor rollout, then adjust resources if needed.

  Why this is correct

  This is the correct order because you first issue the scale command to change the replica count, then verify that new pods are created, confirm the deployment's status shows the desired number, monitor the rollout for any issues, and finally adjust resource limits if necessary.

• ✗

  Check pods are created, then run `kubectl scale` deployment, then verify deployment status, then monitor rollout, then adjust resources if needed.

  Why it's wrong here

  This is incorrect because you cannot check pods before scaling; pods only exist after the scale command is executed.

• ✗

  Run `kubectl scale` deployment, then verify deployment status, then check pods are created, then monitor rollout, then adjust resources if needed.

  Why it's wrong here

  This is incorrect because verifying deployment status before checking pods can lead to confusion; you should confirm pods are created first to ensure the scaling operation is effective.

• ✗

  Monitor rollout, then run `kubectl scale` deployment, then check pods are created, then verify deployment status, then adjust resources if needed.

  Why it's wrong here

  This is incorrect because monitoring the rollout before scaling makes no sense; you must initiate scaling first.

Go deeper

Related to this question