A Java EE 6 application can describe its components through annotations in the code, through deployment descriptors, or through both. At installation time the product scans the application's classes, reads the annotations, and merges that information with whatever the deployment descriptors state, producing the metadata it uses at run time. That metadata is stored with the installed application, so a change to a descriptor, or to any element that changes how annotations are interpreted, is not picked up simply by changing a file in place or by restarting the application, because the stored result of the earlier scan remains in effect. To make the product repeat the scan and rebuild the metadata, the administrator reinstalls the application, which is option C.
Option A, updating files through the administrative console, is a way of delivering changed files, but it does not by itself guarantee a rescan of annotated classes. Option B, restarting, reloads the code but reuses the existing metadata. Option D, editing server.xml, targets the server configuration, and the file does not hold the application's deployment descriptor or its annotation metadata.
After reinstalling, administrators should confirm the intended components were discovered, for example by checking the module and servlet listings in the console, and should preserve bindings and mappings by supplying them again or using a saved binding file. In clustered environments the new version is synchronised to every node before the application starts.
[Reference: Updating enterprise applications; Annotation scanning and metadata-complete deployment descriptors; Installing enterprise applications.]