1z0-133 Practice Exam Questions with Answers Oracle WebLogic Server 12c: Administration I Certification

The minimum heap size for a 64-bit JVM is 64 Megabytes

For performance reasons, the minimum heap size and maximum heap size should be the same value

The parameter value was entered incorrectly. The correct value is: “-Xms32m –Xmx150m”

The parameter value was entered incorrectly. You must enter memory parameter values in Kilobytes

The parameter value was entered incorrectly. The correct value is: “-Xms:32meg – Xmx:150meg”

Simple Connection Access Node

Single Correlated Anonymous Network

Simple Connection Address Name

Single Client Access Name

Create tables in the data store.

Execute SQL scripts in WebLogic server’s server/lib directory.

Populate the database tables with external LDAP users.

Test the connection to a back-end database.

Allocate tablespace for the data store.

This scenario is not possible. You must use the JDBC store to recover transactions from a crashed server.

This scenario is not possible. You must use clustered managed servers to recover transactions from a crashed server.

This scenario is common, and so the default configuration of the default store works.

Before the crash, you need to update the path to the default store for the managed server. The path should be to some shared storage location.

After the crash, obtain a copy of the managed server’s default store from the administration server. Move it to the same relative location on the new hardware before starting the managed server there.

You do not have to lock the configuration to create Log Filters

Log Filters are created at the domain level

The administration console assists in the creation of Log Filter expressions

You can apply a Log Filter to the server log, but not to standard out

You are using the Configuration Wizard to configure a script-based Node Manager.

The configuration Wizard prompts you to change the default Node Manager configuration values.

The configuration Wizard bypasses all Node Manager Configuration.

You are using the configuration Wizard to configure a Java-based Node Manager.

You must manually copy the Node Manager files generated by the configuration Wizard into Node Manager home.

Tunneling enabled

Listen address

Listen port

Outbound enabled

Channel weight

Launch the JDBCDiagnostics utility.

Verify the Dependencies attribute of the data source.

View the target server’s JNDI tree in the console.

Verify that the application and data source have the same target.

Create a Node Manager and enroll it with the domain

Create a domain using a custom template

Assign virtual IP addresses to all servers

Distribute domain files across multiple machines

Create a dynamic cluster of five servers

Option A

Option B

Option C

Option D

Option E

In Persistent Stores, create a new JDBC store and select the option “Use existing store”

The new domain name needs to be the same as the old domain it’s replacing

Duplicate the JMS and persistent store configuration in the new domain

The storage needs to be file based and not JDBC based

Set the prefix for the JDBC store table to the domain name

The proxy will pin a client to a specific server if a session cookie is created.

The proxy fails over to another server if a connection or request times out.

The proxy distributes requests to cluster members based on their CPU usage.

The proxy dynamically learns the latest locations of cluster members.

The proxy always uses SSL, regardless of the client’s protocol.

The proxy replicates session data to its backup proxy.

Define the name in the library’s manifest file

Configure the element in web.xml

Run weblogic.Deployer with the –name option

Set a computed name based on the deployment source file

Set the element in application.xml

Ignore Heuristics

Pinned to Thread

One Phase Commit

Logging Last Resource

Test Connections on Reserve

Create one cluster.

Install Oracle HTTP Server.

Create one Coherence server.

Create four managed servers.

Assign three servers to a cluster.

Specify a proxy port for the administration server.

Dynamic clusters are only supported for the multitier architecture

Remote EJB access is blocked

Each cluster can be scaled independently

Future web clusters can share the same EJB tier

All servers can be managed (started/stopped) together

Use the startNodeManager.sh script

Use the administration console. Select the machine and then click the Start button.

Have Node Manager start at system boot as a daemon

Use the Oracle Process Manager and Notification Server (OPMN) to start Node Manager as a system process

Set the appropriate environment variables. Then run the Java virtual machine with the class nodemanager.RunTime, passing the class the proper parameters.

Database persistence

File persistence

In-memory replication

Whole-server migration

Nothing, Node Manager runs and behaves the same on both WLS versions

Node Manager runs in “per machine” mode and nothing is needed to keep the same behavior.

Node Manager runs in “per domain” mode and requires manual steps to return to “per machine” mode, used in WLS 10.3.6.

Node Manager mode of operating and behavior can be selected in Reconfiguration Wizard.

a name

an ID

the status of “marked for rollback”

a status

The Oracle Notification Service is used to notify the data source of changes to RAC nodes.

The reaction is quick, because in using FCF all network timeouts are set very low.

FCF is faster because it polls and tests connection, freeing the data source from these tasks.

FCF requires the use and configuration of a database server in the GridLink data source.

You can use any Oracle Thin database driver with a GridLink data source.

Create a new deployment plan.

Create a new machine.

Create a new server.

Add a server to the cluster.

Add a server to the machine.

Add the cluster to the machine.

The server’s name is OracleDS1.

The server’s machine name is host01.

The transaction ID is 001129.

The JDBC subsystem generated the message.

The user’s identity is managed1.

The severity level of the message is Critical.

Under the managed server's Services configuration select “JDBC” as the type for the transaction log store.

Under the managed server's Services configuration, select “Disable the Default Store”.

Create a non-XA data source in the domain for the database transaction log.

Create an XA data source in the domain for the database transaction log.

web1 is available but has never been accessed

server1 is in standby mode

server1 is not running

web1 is in the process of being deployed to server1

If you stop Node Manager, the managed servers it started will also stop.

You may kill the Node Manager process by using operating system commands.

Use the stopNodeManager.sh script so Node Manager stops gracefully.

Using the administration console, select the appropriate machine and click Stop.

The administration server goes into ADMIN mode if it can no longer communicate with Node Manager.

The managed servers that Node Manager started go into ADMIN mode if they can no longer communicate with Node Manager.

Click the server ‘s Debug > Heap tab.

Click the server’s Debug > Health tab.

Click the server’s Monitoring > Health tab.

Click the server’s Monitoring > Threads tab.

Click the server ‘s Monitoring > Performance tab.

You must also set the domain attribute “CLASSPATH Discovery Enabled.”

Each machine that hosts WebLogic Servers has its own domain directories. The script must be modified there as well.

Only the first server to receive the new configuration from the administration server gets the updated CLASSPATH

The CLASSPATH is not for application code. It is for interval WebLogic Server code. So, only applications deployed to the administrative server can access code through the CLASSPATH

Statement Cache Type

Pool Reserve Mode

Test Table Name

Test Connection Mode

Test Connections on Reserve

Include the JAR file as an optional package

Deploy the JAR file as an EJB

Deploy the JAR file as a shared library

Place the JAR file in the lib folder of the domain

Deploy the JAR file to the administration server. All managed servers have access to their admin server

Add the JAR file to the CLASSPATH of the domain servers by editing the domain’s seyDomainEnv.sh script

Deploy the JAR file as another web application

Timeout Seconds

Abandon Timeout Seconds

Before Completion Iteration Limit

Checkpoint Interval Seconds

Unregister Resource Grace Period

weblogic-application.xml

session.xml

web.xml

config.xml

weblogic.xml

Data sources are targeted to a domain.

Data sources are bound in the JNDI tree of a server.

Data sources are based on the JMS specification.

A data source contains a connection pool.

A domain requires at least one data source.