You’re developing an application onto AWS which is based on the Microservices. These Microservices will be created based on AWS Lambda functions. Because of the complexity of the flow of these different components, you need some way to manage the workflow of execution of these various Lambda functions. How could you manage this effectively now and for the future addition of Lambda functions to the application?

Answer options:

A.Consider creating a master Lambda function that would coordinate the execution of the other Lambda functions.
B.Consider creating a separate application hosted on an EC2 Instance which would coordinate the execution of the other Lambda functions.
C.Consider using Step Functions to coordinate the execution of the other Lambda functions.
D.Consider using SQS queues to coordinate the execution of the other Lambda functions.

Answer – C
The best way to manage this is to use Step Functions. The AWS Documentation mentions the following about Step Functions.
AWS Step Functions is a web service that enables you to coordinate the components of distributed applications and microservices using visual workflows. You build applications from individual components that perform a discrete function, or task, allowing you to scale and change applications quickly. Step Functions provide a reliable way to coordinate components and step through the functions of your application. 
Options A and B are invalid. Even though feasible, it would just bring too much of effort and maintenance into the entire system.
Option D is invalid because this is good in managing the messaging between distributed components of an application.
For more information on Step Functions, please refer to the below Link-
https://docs.aws.amazon.com/step-functions/latest/dg/welcome.html