Which of the following statements are true for built-in roles in the WebLogic Server Administration console? Choose two.

Carlos M.Jun 23, 2026

B and E are your two correct picks. The Monitor role is read-only but excludes encrypted attributes, and the Admin role has full configuration rights across the entire server, which is exactly what makes it the top-level role.

Ola B.Jun 10, 2026

Good practice question, and the trap here catches a lot of people because the role names sound intuitive but the actual permissions are not what you would guess. Monitor sounds passive, and it is, but the key detail is that it still exposes most of the server config to view, just not the encrypted attributes, which is exactly what option B says. Admin being able to modify the entire server configuration, option E, is the other lock-in because Admin in WebLogic is genuinely unrestricted on the config side. The tricky distractors are A and D. Operators can start and stop the server but they are not the ones deploying apps, that belongs to the Deployer role, and the "only Admin can start/stop" claim in D is just flat wrong since Operators handle that. If you have access to a VirtualBox or even Oracle's free developer VM, spin up a WebLogic domain and log into the admin console with a user assigned the Operator role, then try to hit the deployment screens and see what happens. What I am curious about is whether you have a clear mental model of where the Deployer role fits in relation to Operator, because that distinction shows up in more than one question on this exam.

Fatima Z.Jun 12, 2026

Nailed it with B and E, and here is the sticky image that will make it click forever: picture the WebLogic role ladder as M-O-D-A, Monitor, Operator, Deployer, Admin, where each rung adds one more superpower and the Admin at the top holds the whole wardrobe. The Monitor is basically a window-shopper, read-only access to config but the encrypted fields are behind a locked glass case she can see but not touch, which is exactly what B says. Admin owns the whole store, every shelf, every setting, full modification rights, so E is solid. The tricky trap here is D, because Operators can also start, stop, and resume servers, so Admin is not the only one with that key, and A fails because it is the Deployer role, not Operator, that handles application deployment. Remember M-O-D-A and you will never mix up who can do what on exam day.

Luis F.Jun 2, 2026

B and E are definitely the right picks here. The Monitor role is read-only but it does hide encrypted attributes, and the Admin role is the top-level role that gives full config access across the entire domain, not just parts of it.

Nina C.Jun 5, 2026

Okay so I got tripped up on A at first because I kept thinking Operator sounded like it should cover deployments, but that is actually the Deployer role that handles deployments, not Operator. Operator can start, stop, and resume servers, which also makes D wrong because Operator shares those duties with Admin, not just Admin alone. B holds up because Monitor is strictly read-only and Oracle specifically carves out encrypted data from what Monitor users can see, which makes sense from a security standpoint. And E is straightforward once you clear away the noise, Admin is the top-tier role and can touch the full server configuration, so B and E are the two that check out.