Typical steps in change control will have:

• Understanding the change
• Analyzing its impact on project parameters/constraints like Cost, Schedule, Scope, Quality..
• Develop options. Like if additional scope affects schedule, then do a schedule compression.
• Contact change control board for approvals - they can either approve or reject
• Get customer buy in if needed
• Communicate the change to all the relevant stakeholders and re-baseline

Read this post for more details http://pmzilla.com/change-request-customer-towards-end-project 

In the above PMZILLA admin post (Anatomy of change), the Understand the change is nothing but the 'Evaluate the change request from customer, this involves discussion with team as well.

Most importantly any change depending on the question what is being asked (exam question) you need to make your judgement whether you should go for the first step of 'change request anatomy'  or you have to go to the options, or you have to go to Change control board etc. You need to pick the best possible option asked or what is next in sequence you might have been asked.

One thing to remember is Understanding the change wouldn't be always correct for simple raeson what is being really asked in question you should understand...

Regards

CN Patil