D.

wls:install, wls:create-domain, wls:start-server, wls:wlst, wls:appc:

wls-maven-plugin—Delivered in WebLogic Server 12c, provides enhanced
functionality to install, start and stop servers, create domains, execute WLST
scripts, and compile and deploy applications.
Reference: Developing Applications for Oracle WebLogic Server, Using the WebLogic
Development Maven Plug-In

D.

installing WebLogic binaries on a remote machine using Node Manager

http://docs.oracle.com/middleware/1212/wls/WLSTG/domains.htm

D.

SUFFICIENT

Note:
* When you configure multiple Authentication providers, use the JAAS Control Flag for
each provider to control how the Authentication providers are used in the login sequence.
You can choose the following the JAAS Control Flag settings, among others
REQUIRED—The Authentication provider is always called, and the user must
always pass its authentication test. Regardless of whether authentication
succeeds or fails, authentication still continues down the list of providers.
SUFFICIENT—The user is not required to pass the authentication test of the
Authentication provider. If authentication succeeds, no subsequent Authentication
providers are executed. If authentication fails, authentication continues down the
list of providers.
OPTIONAL—The user is allowed to pass or fail the authentication test of this
Authentication provider. However, if all Authentication providers configured in a
security realm have the JAAS Control Flag set to OPTIONAL, the user must pass
the authentication test of one of the configured providers.
* Example:
Setting the Order of Providers
Re-order the OAM Identity Asserter, OID Authenticator, and Default Authenticator by
ensuring that the control flag for each authenticator is set as follows:
OAMAuthenticator (REQUIRED)
OracleInternetDirectoryAuthenticator (SUFFICIENT)
DefaultAuthenticator (SUFFICIENT)
Reference: Oracle Fusion Middleware Security Guide

A.

Search information in logs across multiple domains

A.

GET

B.

PUT

D.

DELETE

E.

POST

The following principles encourage RESTful applications to be simple,
lightweight, and fast:
Resource identification through URI
* Uniform interface: Resources are manipulated using a fixed set of four create, read,
update, delete operations: PUT, GET, POST, and DELETE. PUT creates a new resource,
which can be then deleted by using DELETE. GET retrieves the current state of a resource
in some representation. POST transfers a new state onto a resource. See Responding to
HTTP Methods and Requests for more information.
* Self-descriptive messages
* Stateful interactions through hyperlinks
Reference: The Java EE 6 Tutorial, What Are RESTful Web Services?

B.

Keep environmental data in Deployment Plan XML files. It allows you to change
parameters in the deployment descriptor without opening the archive file.

WebLogic Server uses the standard J2EE web.xml deployment descriptor for
defining a Web Application. Some applications also require the WebLogic-specific
deployment descriptor, weblogic.xml. You use these deployment descriptors to define
components and operating parameters for a Web Application. Deployment descriptors are
standard text files, formatted using XML notation. You package them in the Web
Application.
Reference: Overview of Web Application Deployment Descriptors

B.

enabling Logging Last Resource

http://my-java-planet.blogspot.com/2014/04/which-weblogic-optimizationallows-
one.html

A.

Per Machine

A Node Manager process is not associated with a specific WebLogic domain
but with a
machine. You can use the same Node Manager process to control server instances in
any WebLogic Server domain, as long as the server instances reside on the same
machine as the Node Manager process. Node Manager must run on each computer
that hosts WebLogic Server instances—whether Administration Server or Managed
Server—that you want to control with Node Manager.
Reference: Overview of WebLogic Server Domains