最新的IBM WebSphere Portal 8.0 Deployment and Administration - LOT-923免費考試真題

A. wkplc_ldap.properties

B. wkplc_ldapdomain.properties

C. wkplc.properties

D. wkplc_ad.properties

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. 1.Install WebSphere Portal on the first node, configure the database, and use the ConfigEngine tasks to create a profile template.
2.Prepare the first node to communicate WebSphere Application Server Network Deployment, and use addNode and ConfigEngine tasks to configure the cluster and user registry.
3.Install WebSphere Portal on additional nodes and use the profile template to configure.
4.Use the addNode and ConfigEngine tasks to federate the additional nodes and complete the cluster setup.

B. 1.Install and configure WebSphere Portal as a stand-alone node for each cluster node.
2.Federate each portal server node to the WebSphere Application Server Network Deployment cell using the addNode command.
3.Create a portal cluster using the ConfigEngine tasks.
4.Configure the cluster members to use the same database and user registry.

C. 1.Use WebSphere Application Server Network Deployment to create a managed node for each portal node in the cluster.
2.Federate each of these nodes into the WebSphere Application Server Network Deployment cell using the addNode command.
3.Install and configure WebSphere Portal on each portal server node.
4.Use ConfigEngine tasks to configure the database, user registry, and create the cluster.

D. 1.Use WebSphere Application Server Network Deployment to create a cell and managed node for each portal node in the cluster.
2.Use the WebSphere Portal cluster profile template to install WebSphere Portal onto each node.
3.Use the ConfigEngine tasks to configure the nodes to use the same database and user registy.
4.Federate each of these nodes into the cluster by using the addNode and ConfigEngine tasks.

A. Realms can only be used with federated repositories when the same user DNs exist in all repositories.

B. Realms cannot be used in conjunction with federated repositories.

C. Realms can be used in federated repositories except that the base entries must not overlap (for example c=us in LDAP1 and c=uk in LDAP2).

D. Realms can only be used in federated repositories where the base entries overlap (for example c=us in LDAP1 and o=myco,c=us in LDAP2).

A. LDAP hostname:port

B. DNS Domain name

C. WMMRealm

D. DefaultWIMFileBasedRealm

A. 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.

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

C. 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.

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. None of the above

B. JSR 286 and IBM API

C. JSR 168 and JSR 286

D. JSR 168 and IBM API

A. wkplc_dbtype.properties, wkplc_dbdomain.properties and wkplc.properties

B. wkplc_comp.properties, wkplc_dbtype.properties, and db.config.properties

C. wkplc_comp.properties and wkplc_dbtype.properties

D. wkplc_comp.properties

A. Wires can be created between a source JSR 168 portlet and a target legacy IBM API portlet.

B. Wires can be either public (available to all users) or private (available to a single user).

C. A wire can only be created from one portlet to another portlet on the same page.

D. A page can have source and target portlets wires configured automatically.