01. One application on a shared Managed Server occasionally consumes so many request threads that other applications on the same server are starved.
Which is the most appropriate practice to contain it?
a) Give the application a minimum-threads constraint so that it is guaranteed a reserved set of threads and never has to yield any of them back to other work.
b) Move the application onto its own dedicated Managed Server so that the default Work Manager on the shared server never has to arbitrate between competing applications.
c) Increase the size of the shared self-tuning thread pool globally so that every deployed application always has additional spare threads available to it.
d) Assign the application a Work Manager with an appropriate maximum-threads or capacity constraint, so that one workload cannot exhaust the shared thread resource.
02. During a design review, one engineer argues that because Managed Servers keep running while the Administration Server is down, it is safe to route some user traffic through the Admin Server for extra capacity.
Which statement best captures why keeping the Administration Server separate and off the request path is still the recommended practice?
a) Because Managed Servers keep serving and even failing over while the Admin Server is unavailable, isolating it from application load means a restart or failure of the Admin Server never disturbs user traffic.
b) Because application deployments can only ever be started from a Managed Server during the periods when the Administration Server happens to be offline for maintenance.
c) Because Managed Servers cannot accept any client requests at all unless the Administration Server is currently running and reachable, so the Admin Server must be kept lightly loaded in order to stay responsive to every member.
d) Because the Administration Server itself actively load-balances the cluster and distributes incoming requests, and so it must never be slowed down by competing application threads.
03. Two WebLogic-hosted SOAP web services must exchange messages with a guarantee that each request is delivered exactly once and in order, even if the network drops connections, and this must not be coded into the application logic.
Which WebLogic web services capability addresses this?
a) JAX-RS resource methods annotated for idempotency so repeated REST calls have the same effect.
b) Store-and-Forward agents attached to each web service endpoint to buffer and retry the SOAP calls.
c) Active GridLink runtime load balancing distributing the SOAP requests between the two services.
d) Web Services Reliable Messaging (WS-ReliableMessaging), applied declaratively via policy on the service.
04. In a WebLogic-managed Coherence deployment, Coherence cache servers run as managed Coherence server instances that belong to the WebLogic domain.
Which component starts and stops these Coherence server instances as part of normal domain lifecycle operations?
a) A standalone Coherence cache-server shell script independent of the domain
b) Node Manager
c) The proxy web server fronting the cluster
d) The domain's embedded LDAP server
05. A bank has three monitoring goals for its WebLogic platform: (1) alert when real customers see slow responses or errors, (2) enforce and localize per-transaction service-level targets across tiers, and (3) pinpoint a JVM-internal bottleneck such as a lock or slow SQL when a server degrades.
Which three feature-to-goal pairings are correct?
(Choose three.)
a) Use JVMD to pinpoint a JVM-internal bottleneck such as a lock or slow SQL
b) Use SmartUpdate to monitor real end-user experience
c) Use RUEI to measure and alert on real end-user response times and errors
d) Use Node Manager to trace business transactions across services
e) Use the free Administration Console to automatically compare configuration drift across all domains
f) Use BTM to track per-transaction service-level targets and identify the failing tier
06. Messages representing operations on a single customer order must be consumed in the exact sequence they were produced, even though the queue is a distributed destination spread across several cluster members.
Which WebLogic JMS feature enforces this per-order processing sequence?
a) Unit-of-Work (UOW)
b) Unit-of-Order (UOO)
c) A durable subscription
d) Message load balancing
07. You are designing JMS for a cluster so that message load spreads across members and a member failure does not strand its messages.
Which destination design is the most appropriate practice?
a) Host every distributed-destination member on the Administration Server itself, so that all message storage and all persistent stores are concentrated together in one central place.
b) Give every member a JMS server that all point at one shared file store on a single local disk, so that every member ends up reading and writing exactly the same messages.
c) Place a single physical destination on one Managed Server and point every other member's producers and consumers at that one central destination, on the assumption that global message ordering is then trivially preserved across every member of the whole cluster.
d) Configure a uniform distributed destination with a member on each clustered server, each backed by its own JMS server and persistent store, so producers and consumers spread out and a failed member's messages can be migrated.
08. After a WAN failover, operators find that a few order messages forwarded by Store-and-Forward were processed twice at the central site. The SAF configuration uses the default at-least-once quality of service.
Which two design responses correctly address this behavior?
(Choose two.)
a) Make the central-site consumers idempotent so that reprocessing a duplicated message has no additional effect.
b) Configure Unit-of-Order on the queue, which removes duplicates as a side effect of ordering.
c) Treat the duplicates as data corruption and disable SAF persistence to stop them.
d) Switch SAF to an exactly-once quality of service, which WebLogic guarantees end to end across sites.
e) Have the consumer track already-processed message identifiers and discard a message whose identifier was seen before.
f) Replace SAF with a synchronous remote send so the producer blocks until the central site confirms.
09. To maximize uptime for a stateful web application, an architect proposes placing all of the cluster's managed servers on one large, powerful machine, arguing that this avoids the overhead of replicating sessions across machines.
How should you evaluate this proposal?
a) It functions but is not recommended: the one machine becomes a single point of failure, so servers should be spread across machines even at some replication cost
b) It is beneficial because consolidating all the servers onto one host eliminates the need for a load balancer in front of the cluster
c) It is required because a WebLogic cluster can only ever contain managed servers that reside together on one and the same physical machine
d) It is the recommended approach because keeping in-memory session replication within a single machine is the fastest option and avoids all cross-machine network overhead
10. Under peak load, an application intermittently fails with pool errors indicating that no connections are currently available, even though the database itself is healthy and responsive. Threads wait and then time out while trying to reserve a connection.
Which change to the JDBC data source most directly addresses this symptom?
a) Configure a test table so that Test Connections on Reserve validates each connection before it is handed out
b) Shorten the shrink frequency so idle connections are released sooner
c) Increase the pool's maximum capacity toward the concurrent demand the database can support
d) Raise only the initial capacity while leaving maximum capacity unchanged