An organization is using Amazon API Gateway to provide a public API called "Survey" for collecting user feedback posts about its products. The survey API has "DEV" and "PROD" stages and consists of one resource "/feedback" which allows users to retrieve/create/update single feedback posts.
A version-controlled Swagger file is used to define a new API that retrieves multiple feedback posts. To add the new API resource "/listFeedbackForProduct" the developer makes changes to the Swagger file defining an API, uploads the file to the organization's version control system, and uses the API Gateway Import API feature to apply the changes to the Survey API. After successful import, the developer runs the tests against the DEV stage and finds that resource "/listFeedbackForProduct" is not available.
What is MOST likely the reason for resource not being available?

A. Even though the Swagger import was successful, resource creation failed afterwards.
B. There is a propagation delay of several minutes in creating API Gateway resources after import.
C. The developer needs to restart the API Gateway stage after import in order to apply the changes.
D. The developer needs to create a new deployment after import in order to deploy the changes.