LPIC-1 Linux Installation and Package Management Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Step 1: Set environment variables (http_proxy, https_proxy, no_proxy) in /etc/environment or user shell config. Step 2: Source the config file (e.g., source ~/.bashrc) or log out/in. Step 3: Configure application-specific proxy settings (e.g., apt.conf, /etc/wgetrc). Step 4: Test connectivity using curl or wget.

  Why this is correct

  This order ensures environment variables are set system-wide or per-user first, then applied by sourcing, then application-specific settings override or complement, and finally testing confirms functionality.

• ✗

  Step 1: Configure application-specific proxy settings (e.g., apt.conf). Step 2: Set environment variables in /etc/environment. Step 3: Source the config file. Step 4: Test connectivity.

  Why it's wrong here

  This order is incorrect because environment variables are typically read before application configs; setting them after application configs may result in applications not using the proxy if they rely on env vars. Also, sourcing should occur after setting env vars, not before configuring apps.

• ✗

  Step 1: Set environment variables in a terminal session (export http_proxy=...). Step 2: Configure application-specific settings. Step 3: Test connectivity. Step 4: Do not make settings persistent by saving to config files.

  Why it's wrong here

  This order is incorrect because the environment variables are not persistent; they only apply to the current shell session. After logging out, settings are lost, and the system will not use the proxy for future sessions.

• ✗

  Step 1: Set environment variables in /etc/environment. Step 2: Test connectivity without sourcing or logging out. Step 3: Configure application-specific settings. Step 4: Reboot the system.

  Why it's wrong here

  This order is incorrect because environment variables set in /etc/environment are not immediately applied without logging out or sourcing. Testing before the variables are active will fail. Rebooting is unnecessary; a simple source or new login is sufficient.

Go deeper

Related to this question