Explanation: By default, all Grails applications are equipped to support internationalization.

Explanation: Inside an application /grails-app/i18n/ folder, you can find series of *.properties files used to define messages in 12 languages.

Explanation: The values declared in these *.properties files allow Grails applications to display messages based on a user’s languages preferences or an application default language.

Explanation: Since the explicit configuration of an application locale takes precedence over a user’s browser language preferences, there is no default configuration present in an application resource.groovy file.

Explanation: You should define an explicit configuration inside an application /grails-app/conf/spring/resource.groovy file, only if you want to coerce users into using a specific language locale.

Explanation: JSP page first imports the Groovy tag library and later declares statements using the Groovy g:message tag.

Explanation: The g:message tag can also be used in GSP pages views, but note that it’s not necessary to import the tag library explicitly, since it’s available by default on all Grails GSP pages.

Explanation: Grails is designed to use a RDBMS as a permanent storage system.

Explanation: HSQLDB is a database that is automatically started by Grails upon deploying an application (i.e., executing grails run-app).

Explanation: Every time an application is restarted in development and testing environments, HSQLDB loses all its data since it’s configured to operate in memory.

Explanation: You can configure Grails to use another RDBMS by modifying an application DataSource.groovy file, located under the grails-app/conf directory.

Explanation: Grails relies on the standard Java JDBC notation to specify RDBMS connection parameters, as well as on the corresponding JDBC drivers provided by each RDBMS vendor, to create, read, update, and delete information.