An administrator needs to set NGINX worker processes to run with the user ID 1001 and group ID 1002. The administrator writes 'user 1001 1002;' in the main context. After reloading, the administrator checks the processes and sees they are running as 'appuser:appgroup'. What does this indicate?

The numeric IDs were ignored, and NGINX used the default user.

NGINX resolved the numeric IDs to the corresponding user and group names.

The 'user' directive only accepts names, not numeric IDs.

The group ID was ignored because only the user ID is supported.

An NGINX administrator needs to configure worker processes to run with the 'appuser' user and the 'webgroup' group. The administrator writes the following directive in the main context of nginx.conf: 'user appuser webgroup;'. After reloading NGINX, the administrator verifies that worker processes are running as 'appuser' but the group is still the default group of 'appuser', not 'webgroup'. What is the most likely cause?

The group name must be specified as a numeric GID, not a name.

The 'webgroup' group does not exist on the system, so NGINX falls back to the user's primary group.

The 'user' directive syntax requires a colon between the user and group names.

The 'user' directive must be placed in the events block to affect worker processes.

An administrator is configuring NGINX on a system where the 'appuser' user exists but has a primary group of 'users'. The administrator wants worker processes to run as 'appuser' with the group 'webgroup'. The administrator adds 'user appuser webgroup;' to the main context. After starting NGINX, the administrator checks the processes and sees they are running as 'appuser:webgroup'. What can be concluded about the configuration?

The 'user' directive only sets the user, and the group is inherited from the user's primary group.

The 'user' directive correctly set both the user and group for worker processes.

The 'webgroup' group must be the primary group of 'appuser' for the directive to work.

The 'webgroup' group was ignored because 'appuser' is not a member of it.

F5Certified Administrator NGINX

Domain 3Objective 1

Identify User Context (i.e. Using the Configuration File) F5N1 Practice Questions (Page 1)

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

17questions here

4free pages

4concepts

Questions 1–5

1application · medium
An administrator needs to set NGINX worker processes to run with the user ID 1001 and group ID 1002. The administrator writes 'user 1001 1002;' in the main context. After reloading, the administrator checks the processes and sees they are running as 'appuser:appgroup'. What does this indicate?
Select an answer first
2application · medium
An NGINX administrator needs to configure worker processes to run with the 'appuser' user and the 'webgroup' group. The administrator writes the following directive in the main context of nginx.conf: 'user appuser webgroup;'. After reloading NGINX, the administrator verifies that worker processes are running as 'appuser' but the group is still the default group of 'appuser', not 'webgroup'. What is the most likely cause?
Select an answer first
3foundation · easy
An administrator needs to verify which OS user account NGINX worker processes will run as. Which configuration file directive should they look for?
Select an answer first
4application · easy
An NGINX server is configured with 'user appuser;' in the main context. The administrator wants to verify that the configuration is valid before reloading. Which command should the administrator run to test the configuration and confirm the user directive is syntactically correct?
Select an answer first
5expert · medium
An administrator is configuring NGINX on a system where the 'appuser' user exists but has a primary group of 'users'. The administrator wants worker processes to run as 'appuser' with the group 'webgroup'. The administrator adds 'user appuser webgroup;' to the main context. After starting NGINX, the administrator checks the processes and sees they are running as 'appuser:webgroup'. What can be concluded about the configuration?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5N1

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. “F5N1” is a trademark of its owner, used for identification only.

Identify User Context (i.e. Using the Configuration File) F5N1 Practice Questions (Page 1)

Questions 1–5

An administrator needs to set NGINX worker processes to run with the user ID 1001 and group ID 1002. The administrator writes 'user 1001 1002;' in the main context. After reloading, the administrator checks the processes and sees they are running as 'appuser:appgroup'. What does this indicate?

An administrator needs to verify which OS user account NGINX worker processes will run as. Which configuration file directive should they look for?

An NGINX server is configured with 'user appuser;' in the main context. The administrator wants to verify that the configuration is valid before reloading. Which command should the administrator run to test the configuration and confirm the user directive is syntactically correct?

Keep studying — Demonstrate how to manage user permissions