Dave deployed an AppUI extension to an instance by mistake. How can he fix this?

Visual Builder Studio (VBS) provides a complete lifecycle management toolset for AppUI extensions. When an extension is deployed, it can be managed from the Environments tab within the VBS project. This interface allows a developer to view all deployed extensions for a specific environment and provides an explicit "Undeploy" action to remove an extension from the Fusion Cloud Apps instance. This is the standard, self-service procedure for correcting a mistaken deployment.

A. Oracle's quarterly updates apply to the base Fusion Cloud application and do not automatically remove custom extensions. Extension lifecycle is managed by the customer.
C. Opening a service request is for support issues, not for standard development lifecycle tasks like undeploying an application. This action is self-service within VBS.
D. Deployed extensions are not permanent. The ability to undeploy an extension is a fundamental feature of the development and deployment process in Visual Builder Studio.

1. Oracle Official Documentation - Developing Applications with Oracle Visual Builder Studio:

Source: Developing Applications with Oracle Visual Builder Studio

Chapter: "Deploying Your Visual Builder Extension"

Section: "Undeploy an Extension".

Content: The documentation explicitly states

"You can undeploy an extension that you no longer need from the Deployments tab of the Environments page." It then provides the step-by-step procedure: "In the navigation menu

click Environments. Select the environment where the extension is deployed. Click the Deployments tab. In the list of deployed extensions

find the extension you want to undeploy

click its Actions menu

and select Undeploy." This directly supports option B and refutes options C and D.