최신IBM WebSphere Portal 8.0 Deployment and Administration - C9520-923무료샘플문제

A. Cooperative portlets communicate by using properties that are produced and consumed by portlet actions.

B. JSR 286 portlets require an additional WSDL deployment descriptor which defines portlet actions.

C. An administrator can use cooperative portlet support with either IBM, JSR 168, or JSR 286 portlets.

D. Cooperative portlets represent an IBM-specific API for publish/subscribe communication between portlets.

A. It is designed to be used alongside any other user-defined search collections.

B. It is a special purpose collection, created by default, when IBM Web Content Manager is enabled and allows for search using the Authoring portlet.

C. It is the same as the default PortalContent Collection used in IBM WebSphere Portal.

D. There is no default collection in WebSphere Portal 8.0 called JCRCollection1.

A. LDAP properties (whether federated or stand-alone) begin with ldap, but federated LDAP uses the validate-federated-ldap task for LDAP validation, whereas stand-alone LDAP uses the validate-standalone-ldap task for LDAP validation. Both use the wp-modify-ldap-security task for establishing LDAP connection.

B. Administrators must select the Federated LDAP check box in the IBM WebSphere Integrated Solutions console.

C. Federated LDAP properties begin with federated.ldap, whereas stand-alone LDAP properties begin with standalone.ldap in the wkplc.properties file. Different configuration tasks are used both for LDAP validation and establishing an LDAP connection.

D. Federated LDAP properties begin with federated.ldap whereas stand-alone LDAP properties begin with standalone.ldap in the wkplc.properties file, but both still use the validate-ldap configuration task for validation and the create-wp-ldap task for creating the LDAP repository.

A. A, B and D

B. B and C

C. All types of portal resources can be scoped to a particular Virtual Portal

D. Scoping means making portal resources available uniquely and separately to individual Virtual Portals and their users

E. Separation between Virtual Portals cannot be achieved by scoping the portal resources of the Virtual Portals

F. The user population can be scoped to one or more specific Virtual Portals

A. She can set up a unique installation where each farm has a unique installation or she can set up one instance that is shared between multiple farm instances.

B. She can clone installations where each farm is not a unique installation or she can set up one instance that is shared between multiple farm instances.

C. She can clone installations where each farm is not a unique installation or she can set up multiple instances that are shared between multiple farm instances.

D. She can set up a unique installation where each farm has a unique installation or she can set up multiple instances that are shared between multiple farm instances.

A. This task requires that WebSphere Portal is customized with the search API.

B. IBM WebSphere Portal 8.0 only uses an external search system.

C. Cooper can use tags for better search results.

D. Only IBM Web Content Manager content can be categorized with the categorize function.

A. Markup JavaScript code Static JavaScript configuration Dynamic JavaScript configuration CSS

B. CSS Dynamic JavaScript configuration Static JavaScript configuration JavaScript code Markup

C. CSS Static JavaScript configuration Dynamic JavaScript configuration JavaScript code Markup

D. Static JavaScript configuration Dynamic JavaScript configuration JavaScript code Markup CSS

A. Portal and content caches across all four server instances are replicated seamlessly.

B. Using a shared installation, all four server instances that become a part of the portal farm can be installed on different operating systems.

C. Session persistence is enabled by default on all four server instances..

D. All the server instances need to be configured such that they have an identical security configuration and user repository, such as LDAP.

A. Reverse the parameter order for store.puma_default.puma.commonname for the Puma Store service.

B. Scott cannot modify the way WebSphere Portal generates common names.

C. Change the common name order in the User Administration portlet on the Users and Groups page.

D. Reverse the parameter order for store.puma_default.puma.commonname for the Validation service.