When configuring OCI Stack Monitoring to discover and monitor an Oracle WebLogic Server environment, which THREE prerequisites or configuration steps are required?
Stack Monitoring discovers WebLogic Server resources through the Management Agent, which must be installed on the WebLogic host to collect metrics and topology data. Without this agent, no discovery or monitoring of the WebLogic domain is possible, making it a mandatory prerequisite.
Why this answer
Option B is correct because Stack Monitoring relies on the OCI Management Agent installed on the WebLogic host to collect metrics and communicate with the OCI Monitoring service. Option D is correct because discovery requires valid WebLogic administrator credentials plus JMX connection details (host, port, protocol) so the agent can query the WebLogic MBeans. Option E is correct because the Stack Monitoring discovery wizard, run from the OCI Console or CLI, is the mechanism that creates the WebLogic resource and associates it with the agent.
Option A is not required, as the administration console does not need a public IP and exposing it would be a security risk. Option C is not required, since BGP peering is a networking concept unrelated to WebLogic discovery and monitoring.
Exam trap
The trap is assuming network-level prerequisites like BGP peering or public IP exposure are needed for Stack Monitoring, when in fact discovery relies entirely on the outbound Management Agent plus JMX credentials.