Free Liferay Certified Professional Developer LRP-614 Exam Practice Test

A portlet can be assigned to a category in the Add Application menu using:

• liferay-display.xml
  
• liferay-portlet.xml
  
• liferay-category.xml
  
• liferay-menu.xml
  

Language hooks cannot be used to add new language keys.

• True
  
• False
  

Only an Ext plugin can:

• Override language keys
  
• Modify the initialization parameters of a core portlet
  
• Create a model listener
  
• Override a JSP
  
• Override Liferay services
  

The descriptor liferay-hook.xml defines the location to override a core JSP using:

• <url-pattern>
  
• <custom-jsp-global>
  
• <custom-jsp-dir>
  
• <jsp-override>
  
• <include-and-override>
  

The recommended way to add a custom class to Liferay's startup process is to:

• Create a portal-ext.properties file in the Liferay Home directory that adds the custom class to global.startup.events, and add the custom class to the deployed Liferay application
  
• Create an Ext plugin that replaces the value of global.startup.events with the custom class, and add the custom class to the plugin
  
• Create a portal-ext.properties file in the Liferay Home directory that replaces the value of global.startup.events with the custom class, and add the custom class to portal-impl.jar
  
• Create an Ext plugin that adds the custom class to global.startup.events, and add the custom class to the plugin
  

To display the language key 'add-part'' use:

• <liferay-ui: locale key= 'add-part' />
  
• <liferay-ui: language key= 'add-part' />
  
• <liferay-ui;message key = 'add-part' />
  
• <aui-ui: message key ='add-part' />
  

The following code:GetterUtil.getlnteger('one')returns:

• 0
  
• 1
  
• The code throws a java.lang.ArithmeticException
  
• The code throws a com.liferay.portal.kernel.exception.SystemException
  

Portlets that extend MVCPortlet require annotations on action methods.

• True
  
• False
  

The location of the XML file that determines permissions for a portlet plugin is configured by:

• The VM argument 'resource-actions-configs'
  
• The portlet property 'resource.actions.configs'
  
• The init parameter 'resource-actions-configs'
  
• A portal property 'plugin.resource.actions.configs'
  

The recommended way to cleanly redeploy an Ext plugin is to:

• Remove the plugin WAR file from the server and redeploy
  
• Set ext.redeploy .enabled to''true''
  
• Remove the ext-plugin-[nameof plugin],xml file in the deployed Liferay application and redeploy
  
• Start from a clean instance of the server and redeploy