Environment management with conda and pip in MLOps - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Conda environment creation output

What is the output when you run the following command in a terminal?

conda create -n myenv python=3.9

MLOps

conda create -n myenv python=3.9

A Usage: conda create [OPTIONS]\nTry 'conda create --help' for more information.

B Error: unknown command 'create-env'\nTry 'conda --help' for more information.

C CommandNotFoundError: No command 'conda create' found.

D Collecting package metadata (current_repodata.json): done\nSolving environment: done\n\n## Package Plan ##\n\n environment location: /home/user/miniconda3/envs/myenv\n\n added / updated specs:\n - python=3.9\n\nThe following packages will be downloaded:\n ...\nProceed ([y]/n)?

💡 Hint

Think about what conda normally outputs when creating an environment.

The 'conda create' command outputs metadata collection, environment solving, and package plan details before asking for confirmation.

🧠 Conceptual

intermediate

Difference between pip and conda for package installation

Which statement correctly describes a key difference between pip and conda when managing Python packages?

A conda installs packages only from PyPI, while pip can install from any URL or local file.

B pip manages virtual environments, but conda does not support environment management.

C pip installs packages only from the Python Package Index (PyPI), while conda can install packages from multiple sources including non-Python libraries.

D conda installs packages only for Python 2, while pip supports Python 3.

💡 Hint

Think about the scope of packages each tool can handle.

Conda can install packages beyond Python libraries, including system-level dependencies, while pip focuses on Python packages from PyPI.

❓ Troubleshoot

advanced

Resolving package conflicts in conda environment

You run conda install numpy=1.18 pandas=1.3 in an existing environment and get a conflict error. What is the best next step to resolve this?

A Run <code>conda update --all</code> to update all packages and resolve conflicts automatically.

B Delete the environment and create a new one with the desired packages from scratch.

C Use <code>pip install numpy==1.18 pandas==1.3</code> inside the conda environment to bypass conda conflicts.

D Ignore the error and force install with <code>conda install --force numpy=1.18 pandas=1.3</code>.

💡 Hint

Think about how conda manages package versions and dependencies.

Updating all packages helps conda find compatible versions and resolve conflicts safely.

🔀 Workflow

advanced

Best practice for sharing environment setup

You want to share your conda environment setup with a teammate so they can recreate it exactly. Which command should you run to export the environment configuration?

A conda list --export > packages.txt

B conda env export --no-builds > environment.yml

C pip freeze > requirements.txt

D pip list --format=freeze > environment.yml

💡 Hint

Consider which command exports a full environment including dependencies and versions.

The 'conda env export' command creates a YAML file with all packages and versions, ideal for sharing environments.

✅ Best Practice

expert

Combining pip and conda in environment management

You have a conda environment but need to install a package only available via pip. What is the recommended best practice to avoid dependency issues?

A First install all conda packages, then install pip packages inside the activated conda environment using pip.

B Install pip packages first, then create the conda environment with conda packages.

C Use pip outside the conda environment to install packages globally, then activate conda environment.

D Mix pip and conda installs randomly without activating the environment.

💡 Hint

Think about environment isolation and dependency management order.

Installing conda packages first ensures dependency resolution; pip installs afterward add packages not available in conda.