What happens if you omit the format parameter in the access_log directive?

Logging is disabled for that context

An error is generated and NGINX fails to start

The last defined log_format is used automatically

The default 'combined' format is used

An administrator needs to record the client's IP address, the requested URI, and the HTTP status code for each request. What is the primary reason to customize the NGINX log format instead of using the default combined format?

To reduce the size of log files by omitting the timestamp

To enable encryption of log data at rest

To change the destination file where logs are written

To capture only the specific data fields required by the organization's logging policy

A platform team is troubleshooting slow API responses. They need to determine whether the delay occurs in NGINX itself or in the upstream application server. Which set of variables in a custom log format would provide the most direct evidence for this diagnosis?

$request_time and $upstream_response_time

$remote_addr and $http_user_agent

After configuring a custom log format, an administrator runs `nginx -t` and receives a warning about an unknown variable. The configuration still loads. What is the most likely reason for this warning?

The variable is deprecated and will be removed in a future version.

The log_format directive is placed in the wrong context.

The variable name is misspelled or does not exist in the current NGINX version.

The access_log directive references a format that is not defined.

F5 Certified Administrator NGINX - Configuration:Demonstrate

Domain 3Objective 1

Demonstrate How to Customize the Format of Log Files F5N3 Practice Questions (Page 1)

Part of the Demonstrate how to configure logging domain, which makes up ~18% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~2–4 in this domain), expect 1–1 from this objective — we provide 18 practice questions to prepare you well beyond it. (estimate)

18questions here

4free pages

6concepts

Questions 1–5

1foundation · easy
Which directive is used to define a custom log format in NGINX?
Select an answer first
2foundation · easy
What happens if you omit the format parameter in the access_log directive?
Select an answer first
3foundation · easy
An administrator needs to record the client's IP address, the requested URI, and the HTTP status code for each request. What is the primary reason to customize the NGINX log format instead of using the default combined format?
Select an answer first
4application · medium
A platform team is troubleshooting slow API responses. They need to determine whether the delay occurs in NGINX itself or in the upstream application server. Which set of variables in a custom log format would provide the most direct evidence for this diagnosis?
Select an answer first
5application · medium
After configuring a custom log format, an administrator runs `nginx -t` and receives a warning about an unknown variable. The configuration still loads. What is the most likely reason for this warning?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5N3

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by F5. “F5N3” is a trademark of its owner, used for identification only.