1Z0-1072-20 · Question #236
Which two parameters are required in a back end set's HTTP health check? (Choose two.)
The correct answer is B. URL path D. port. https://docs.cloud.oracle.com/iaas/Content/GSG/Tasks/loadbalancing.htm#Create Enter the Health Check details. Load Balancing automatically checks the health of the instances for your load balancer. If it detects an unhealthy instance, it stops sending traffic to the instance…
Question
Which two parameters are required in a back end set's HTTP health check? (Choose two.)
Options
- Aresponse body
- BURL path
- Ctimeout
- Dport
- Estatus code
How the community answered
(34 responses)- A6% (2)
- B82% (28)
- C9% (3)
- E3% (1)
Explanation
https://docs.cloud.oracle.com/iaas/Content/GSG/Tasks/loadbalancing.htm#Create Enter the Health Check details. Load Balancing automatically checks the health of the instances for your load balancer. If it detects an unhealthy instance, it stops sending traffic to the instance and reroutes traffic to healthy instances. In this step, you provide the information required to check the health of servers in the backend set and ensure that they can receive data traffic. Protocol: Select HTTP. URL Path (URI): Enter / The rest of the fields are optional and can be left blank for this tutorial.
Topics
Community Discussion
6
Nina C.Dec 21, 2025The correct answers are B, URL path, and D, port. When OCI's load balancer runs an HTTP health check, it has to actually send an HTTP request to each backend server, and to do that it needs two things it cannot guess or default in a meaningful way, which is exactly where to send the request and on which port to knock. The URL path tells the health checker which endpoint to hit, like /health or just /, and the port tells it which TCP port on the backend to connect to, since your backend might not be listening on the standard port 80. The other options like response body, timeout, and status code either have built-in defaults (timeout defaults to 3000ms, status code defaults to 200) or are optional pattern-matching features, so the system can function without you explicitly setting them, but it literally cannot form a valid HTTP request without a path and a port.
Samuel O.Jan 2, 2026URL path and port are the two required fields, everything else defaults.
Lena V.Jan 4, 2026Port defaults too depending on the scheme, so the exam will nail you if you mark it required when HTTP assumes 80 and HTTPS assumes 443 without you specifying anything.
Lena V.Jan 11, 2026Saw this exact scenario on my exam last spring and almost second-guessed myself into picking timeout, but the OCI docs I drilled the night before made it stick that the health checker needs the URL path to know where to send the probe and the port to know where to reach the backend. Lock in B and D, move on.
Orla P.Jan 4, 2026Honestly my first instinct was C and D because timeout feels like something you'd have to explicitly declare or the check would just hang forever, but the console and the API docs both show that timeout carries a default value, so it is optional, not required. URL path and port are the two you cannot skip because the service needs to know exactly where on the backend server to send the HTTP request, and without a port it cannot even open the connection to begin checking. If you are doing this in Terraform or through the API you will see those two fields flagged in the schema as required while everything else, including status code range and response body match, falls under optional configuration you layer on top. Go back and read the health check section in the OCI Load Balancing documentation one more time before test day and it will click.
Nina C.Jan 6, 2026Good point on timeout having a default, and I would just add that URL path is only required when the protocol is HTTP or HTTPS, not for TCP health checks, which caught me off guard the first time I read through that section.