Try and practice the latest Oracle : 1z1-134 real questions & answers

Your organization is using a Multi data source (MDS) on WebLogic Server to support applications connecting to an Oracle RAC database. You have been tasked with configuring a new callback handler for the MDS.
Which two statements are true concerning related MDS options and behavior? (Choose two.)

• A. Callback handlers are called for both failover and failback decisions.
• B. If the Failover Callback Handler attribute is set on the MDS, the Test Frequency attribute is no longer used.
• C. Callback handlers are optional when using the Failover MDS Algorithm.
• D. You can register only one callback handler for each WebLogic server.

You have a versioned application deployed in your production environment. You have been asked to troubleshoot why the most recent production redeployment appeared to allow the older version to retire too quickly.
In this case, the application had active RMI clients, but their subsequent calls were directed to the newer version immediately rather than waiting for the expected five minutes defined by the retirement timeout argument. The script command was:
java
weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
-password Welcome1 -redeploy -name myDeployment
-source /myDeployments/myApplication/appX
-retiretimeout 300
You expected the older version to remain active (when there are active RMI clients) for five minutes after executing the production redeployment.
Which modification should have been made to this command to ensure the older version remains active?
(Choose the best answer.)

• A. java
  weblogic.Deployer -adminurl http://localhost:7001 -user weblogic-password Welcome1 -redeploy
  -name myDeployment-source /myDeployments/myApplication/appX-retiretimeout 300 -remote
• B. java
  weblogic.Deployer -adminurl http://localhost:7001 -user weblogic-password Welcome1 -redeploy
  -name myDeployment-source /myDeployments/myApplication/appX-retiretimeout 300 -keepsessions
• C. java
  weblogic.Deployer -adminurl http://localhost:7001 -user weblogic-password Welcome1 -redeploy
  -name myDeployment-source /myDeployments/myApplication/appX-retiretimeout 300
  -rmigraceperiod 300
• D. java
  weblogic.Deployer -adminurl http://localhost:7001 -user weblogic-password Welcome1 -redeploy
  -name myDeployment-source /myDeployments/myApplication/appX-retiretimeout 300 -timeout 300

Examine the domain diagram:

You are asked to write a WLST script that will print the current available heap size for server04.
Assuming:
* all servers are running
* you have just started an offline, interactive WLST session
* a domain-scoped node manager is running on each machine, listening o port :5556
* the username/password "weblogic/Welcome1" maps to a valid domain administrator and Node Manager client Which two code options will accomplish this task? (Choose two.)

• A. connect('weblogic','Welcome1','host00.acme.com:7001')serverRuntime()x = getMBean('/JVMRuntime/server04')print x.getHeapFreeCurrent()
• B. connect('weblogic','Welcome1','host02.acme.com:7201')serverRuntime()x = getMBean('/JVMRuntime/server04')print x.getHeapFreeCurrent()
• C. connect('weblogic','Welcome1','host00.acme.com:7001')domainRuntime()x = getMBean('/ServerRuntimes/server04/JVMRuntime/server04')print x.getHeapFreeCurrent()
• D. nmConnect('weblogic','Welcome1','host02.acme.com:5556')serverRuntimes()x=getMBean('/server04/JV x.getHeapFreeCurrent()
• E. nmConnect('weblogic','Welcome1','host00.acme.com:5556')domainRuntime()x=getMBean('/ServerRun x.getHeapFreeCurrent()

You are asked to create a WLST script to make live updates to a domain that has its administration server running. You want your script to mimic the actions of a WebLogic administrator by using the administration console and clicking the "Lock and Edit" button.
What commands would accomplish this?

• A. edit() followed by startEdit()
• B. lockDomain() followed by editDomain()
• C. domainConfig() followed by cd('Edit')
• D. lockDomain() followed by edit()
• E. clearPending() followed by lockDomain()
• F. getLock(0) followed by edit()

For some reason, servers in your domain are failing. The host machines are pingable and the WebLogic JVM processes are running but the getState() method on the ServerRuntimeMBean reports FAILED.
In the future, when this happens, you want these failed servers to be shut down and then restarted automatically without human intervention. At the same time, you want to constrain how much time will be spent restarting those servers and how many restart attempts will be made.
Pick the two options that would help with this situation. (Choose two.)

• A. Make sure all managed servers are members of a cluster with ReplicationGroupsEnabled set to true.
• B. For each server (or cluster), set RestartInterval to an appropriate positive integer.
• C. When starting Node Manager, use the WLST nmStart command and pass in a WLST properties object with RestartMax set to an appropriate positive integer.
• D. Start the servers by executing the restartManagedWebLogic.sh script in the domain's /bin directory.