What is most likely NOT a characteristic of an integration test for a REST API implementation?

What is most likely NOT a characteristic of an integration test for a REST API implementation?
A . The test needs all source and/or target systems configured and accessible
B . The test runs immediately after the Mule application has been compiled and packaged
C . The test is triggered by an external HTTP request
D . The test prepares a known request payload and validates the response payload

Answer: B

Explanation:

Correct Answer. The test runs immediately after the Mule application has been compiled and packaged

*****************************************

>> Integration tests are the last layer of tests we need to add to be fully covered.

>> These tests actually run against Mule running with your full configuration in place and are tested from external source as they work in PROD.

>> These tests exercise the application as a whole with actual transports enabled. So, external systems are affected when these tests run.

So, these tests do NOT run immediately after the Mule application has been compiled and packaged.

FYI… Unit Tests are the one that run immediately after the Mule application has been compiled and packaged.

Reference: https://docs.mulesoft.com/mule-runtime/3.9/testing-strategies#integration-testing