Implementing Azure Functions

1. You notice that a function hosted on a Consumption plan is always slow to run first thing in the morning. After the first run, the function runs again as expected.

What is the most likely reason for this behavior?

1. A long-running function that started overnight needs to finish before processing the early morning request.
2. The Always on setting is turned off overnight and enabled at a scheduled time automatically.
3. The function instances scaled to 0 due to being idle, and it takes some time for a cold startup.

2. You’ve inherited responsibility for a function that someone else created. This function uses a timer trigger, and you need to identify the schedule on which this function triggers.

The trigger has been configured with the following NCrontab syntax: 0 0 */2 * * mon-fri.

What is the schedule on which this timer has been triggered?

1. Every 2 days between Monday and Friday (Monday, Wednesday,...