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.

A WebLogic domain can be composed of a number of WebLogic instances, and

several of these servers may be grouped into clusters. For instance, you could set up a

cluster of WebLogic servers, all of which host your web application and related

resources. This cluster of servers could be fronted by a load balancer that distributes

requests evenly across all the members of the cluster. The load balancer could itself be

another WebLogic instance. All server instances must belong to the same WebLogic

domain. Thus, a WebLogic cluster is a group of servers working together with services,

such as clustered JNDI, to provide support for failover and load balancing. A domain

may in turn have a number of WebLogic instances, several groups of which can be

placed into different clusters.

D: You were able to log in to the web application that is deployed through WebLogic.

In WebLogic Server, Authentication providers are used to prove the identity of users or system processes.

This implies that your account exists in an authentication provider.

E: Extra security is needed to use the publish link. This could be explained by a security policy attached the publish Link URL.