1Z0-102 Online Practice Questions and Answers

Correct Answer: ABC

B: For efficient security management, BEA recommends adding users to groups. A group is a collection of users who usually have something in common, such as

working in the same department in a company.

C: Example of group nesting:

Every user is a member of the everyone group.

The users group is nested within the everyone group.

Note: Security Providers - are modules that provide security service to application to protect Weblogic resource.

Types of security providers in WebLogic Server are

Authentication Provider, Authorization Provider, Auditing Providers, Credential Mapping Provider, Identity Asser- tion Provider, Principal Validation Provider,

Adjudication Providers, Role Mapping Providers, Certificate Lookup and Validation Providers, Keystore Providers and Realm Adapter providers

Incorrect answers:

D: There is no password for a group.

F: A keystore is a mechanism designed to store password-protected store private keys and trusted CA certificates. In the WebLogic Server security architecture, the WebLogic Keystore provider is used to access keystores. You cannot use a custom Keystore provider with WebLogic Server.

References: Securing WebLogic Resources, Users, Groups, And Security Roles

Correct Answer: C

Note: You can use the Administration Console to configure selected deployment descriptor element values for an EJB that is deployed as an exploded application. To configure editable deployment descriptor values for an EJB that is deployed as an exploded application:

1.

If you have not already done so, in the Change Center of the Administration Console, click Lock and Edit (see Use the Change Center).

2.

In the left pane of the Administration Console, select Deployments.

3.

In the right pane, click the desired EJB module.

4.

Select the Configuration > General tab.

Selected deployment descriptor elements for the EJB are listed.

5.

Enter new values for the elements you want change, and click Save.

6.

To activate these changes, in the Change Center of the Administration Console, click Activate Changes.

Not all changes take effect immediately--some require a restart

Reference: Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1, Configure deployment descriptor values

Correct Answer: BCD

B: select Force Shutdown Now to stop the server immediately without completing ongoing tasks.

D: Select When Work Completes to gracefully shut down the server A graceful shutdown gives WebLogic Server subsystems time to complete certain application

processing currently in progress.

Screenshot:

Incorrect answers:

A: You can shutdown a managed server without selecting "lock and edit".

E: The Administration server can also be shutdown.

Correct Answer: BCF

B: The Console Context Path is an advance configuration option. The context path that you want to use in URLs that specify the Administration Console. Note: Create a new WebLogic Server domain based on a template. Templates allow you to re-create an existing do- main for use in another context, such as migrating a domain containing an application under development to a pro- duction environment.

C: An Administration Console extension is a WAR file that contains the resources for a section of a WebLogic Portal Web application. When you deploy the extension, the Administration Console creates an in-memory union of the files and directories in its WAR file with the files and directories in the extension WAR file. Once the extension has been deployed, it is a full member of the Administration Console: it is secured by the WebLogic Server security realm, it can navigate to other sections of the Administration Console, and if the extension modifies WebLogic Server resources, it participates in the change control process.

Incorrect answers:

A: Exposing the console in your production environment might be security issue. In those cases you can either dis- able the console or hide it. Needless to say if you disable the console then your only option is to depend on com- mand-line and scripting tools for any other administration activity or to even enable the console back. But hiding will provide a level or security.

To disable the console:

In the admin console navigate to --> General --> Advanced Options --> Console Enabled. De-select that option to disable console (restart required).

To hide the cosole:

E: Access through a secure port is recommended, but not required:

The administration port requires all communication to be secured using SSL. By default, all servers in a do- main use demonstration certificate files for SSL, but

these certificates are not appropriate for a production environment.

Reference: Administration Console Online Help, Advanced Configuration Options Reference: Extending the Administration Console for Oracle WebLogic Server 11g Release 1

Correct Answer: BE

B: The Administration Server uses the machine definition in conjunction with the Node Manager application to start remote WebLogic Server instances.

E: By default, WebLogic Server attempts to create session state replicas on a different machine than the one that hosts the primary session state. You can further control where secondary states are placed using replication groups. A replication group is a preferred list of clustered servers to be used for storing session state replicas. Using the WebLogic Server Console, you can define unique machine names that will host individual server instances. These machine names can be associated with new WebLogic Server instances to identify where the servers reside in your system. Machine names are generally used to indicate servers that run on the same machine.

Reference: Administration Console Online Help, Machines Reference: Failover and Replication in a Cluster

Correct Answer: B

To configure file-based persistent storage for sessions:

In the deployment descriptor file weblogic.xml, set the persistent-store-type parameter in the session-descriptor element in the weblogic.xml deployment descriptor file to file. See session- descriptor.

Set the directory where WebLogic Server stores the sessions.

Reference: Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1, Using File-based Persistent storage http://docs.oracle.com/cd/E15523_01/web.1111/e13712/sessions.htm ()

Correct Answer: C

File persistence use less memory than in-memory replication, and does not need access rights to the company's database.

Note:

You use session persistence to permanently store data from an HTTP session object to enable failover and load balancing across a cluster of WebLogic Servers.

When your applications stores data in an HTTP session object, the data must be serializable. There are five different implementations of session persistence:

*

Memory (single-server, non-replicated)

*

File system persistence

*

JDBC persistence

*

Cookie-based session persistence

*

In-memory replication (across a cluster)

Incorrect answers:

A: Using in-memory replication, WebLogic Server copies a session state from one server instance to another. The primary server creates a primary session state on the server to which the client first connects, and a secondary replica on another WebLogic Server instance in the cluster. The replica is kept up-to-date so that it may be used if the server that hosts the servlet fails.

D: JDBC persistence stores session data in a database table using a schema provided for this purpose. You can use any database for which you have a JDBC driver. You configure database access by using connection pools.

Note: When you use memory-based storage, all session information is stored in memory and is lost when you stop and restart WebLogic Server.

Reference: Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server, Using Sessions and Session Persistence

Correct Answer: ACEF

A: Steps to Deploy Application using Administration Console

1.

Start the Admin Server and Managed Server.

2.

Navigate to Administration console http://localhost:7001/console and login.

3.

Navigate to Domain Environment > Deployments. Lock the console.

4.

Etc.

E: To enable the administration port for your domain:

1.

If you have not already done so, in the Change Center of the Administration Console, click Lock and Edit

2.

Shutdown all Managed Servers in the domain. You cannot enable the administration port dynamically on a Managed Server.

3.

Ensure that all servers in the domain are properly configured to use SSL.

4.

In the left pane of the Console, under Domain Structure, select the domain name.

5.

Select Configuration > General and select the Enable Administration Port check box to enable the SSL administration port for this domain.

6.

In the Administration Port field, enter the SSL port number that server instances in the domain use as the administration port. You can override an individual server instance's administration port assignment on the Advanced options portion of the Configuration: General page for the server instance.

7.

Click Save.

8.

To activate these changes, in the Change Center of the Administration Console, click Activate Changes.

Note: If you want to use the Administration Console to make configuration changes, you must first click the Lock and Edit button in the Change Center. When you click Lock and Edit, you obtain a lock on the editable hierarchy of Configuration MBeans for all servers in the domain (the edit tree). As you make configuration changes using the Administration Console, you click Save (or in some cases Finish) on the appropriate pages. This does not cause the changes to take effect immediately; instead, when you click Save, you are saving the change to the edit tree and to the DOMAIN_NAME/pending/config.xml file and related configuration files. The changes take effect when you click Activate Changes in the Change Center. At that point, the configuration changes are distributed to each of the servers in the domain. If the changes are acceptable to each of the servers, then they take effect. (Note, however, that some changes require a server to be restarted.) If any server cannot accept a change, then all of the changes are rolled back from all of the servers in the domain. The changes are left in a pending state; you can then either edit the pending changes to resolve the problem or revert the pending changes.

Incorrect answers:

G: There is no need to lock the configuration when you add a user (to the default authentication provider). Note: To create a new user in the embedded WebLogic LDAP server:

1.

Log in to the Oracle WebLogic Server Administration Console

2.

In Oracle WebLogic Server Administration Console, select Security Realms from the left pane and click the realm you are configuring. For example,myrealm.

3.

Select Users and Groups tab, then Users. Click New. etc.

Reference: Administration Console Online Help, Use the Change Center

Correct Answer: AD

A: Each server instance in your WebLogic environment must have a unique name, regardless of the domain or cluster in which it resides, or whether it is an Administration Server or a Managed Server. Within a domain, each server, machine, cluster, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.

D: The server name cannot be changed.

Incorrect answers:

B: Listen ports can be changed.

Change Weblogic Listen Port:

We need to use WLST (weblogic scripting tool) utility if we need to change from back- end.

Example:

wls:/offline/wl_server/Server/examplesServer> set(`ListenPort',10890); wls:/offline/wl_server/Server/examplesServer> updateDomain(); wls:/offline/wl_server/

Server/examplesServer> exit();

C: port is 7001. It does not need to be unique for each server. They all use the same Listen port by default. In Weblogic server default Listen

Correct Answer: BC

B: WebLogic Server supports SSL on a dedicated listen port which defaults to 7002. To establish an SSL connection, a Web browser connects to WebLogic Server by supplying the SSL listen port and the HTTPs schema in the connection URL, for example, https://myserver:7002.

C: Note: Enabling SSL under WLS 10.3

Steps to configure WLS for SSL:

1) Open the WLS console

2) Select from the Domain Structure -> (your domain) -> Environment -> Servers

3) Select the server from the Summary of Servers page you wish to configure for SSL.

4) Under the Settings for (server name) page, select the Configuration tab, then General tab (the defaults).

5) If WLS is running in production mode, select the Lock and Edit button.

6) Select the SSL Listen Port Enabled checkbox, and enter your preferred port in the SSL Listen Port.

7) Press the Save button.

8) If WLS is running in production mode, select the Release Configuration button.

Incorrect answers:

A: There is no such thing as SSL Listen address. Using a sloppy language it can be used as a synonym to SSL Listen Port. SSL Listen port do exist.

Reference: Oracle HTTP Server Attribute Descriptions