diff --git a/assignment-2/dev0.png b/assignment-2/dev0.png
new file mode 100644
index 00000000..857be7b5
Binary files /dev/null and b/assignment-2/dev0.png differ
diff --git a/assignment-2/dev2.png b/assignment-2/dev2.png
new file mode 100644
index 00000000..446c9156
Binary files /dev/null and b/assignment-2/dev2.png differ
diff --git a/assignment-2/dev3.png b/assignment-2/dev3.png
new file mode 100644
index 00000000..7258e8e1
Binary files /dev/null and b/assignment-2/dev3.png differ
diff --git a/assignment-2/i192009_m_rizwan.md b/assignment-2/i192009_m_rizwan.md
new file mode 100644
index 00000000..a7b009ec
--- /dev/null
+++ b/assignment-2/i192009_m_rizwan.md
@@ -0,0 +1,24 @@
+# Q1.
+
+1. Containers typically have faster startup times compared to Virtual Machines (VMs), which can take longer to initialize.
+2. VMs tend to consume a significant amount of system memory, whereas containers are more efficient in their memory usage.
+3. VMs are considered more secure because they don't share underlying hardware resources, while containers, by design, share some resources and are therefore considered less secure in certain scenarios.
+4. VMs are a preferable choice when you need to utilize the entirety of an operating system's resources, while containers excel at maximizing application density on minimal server resources.
+5. VMs generally have larger disk space requirements compared to containers.
+
+# Q2.
+
+
+docker network create assignment-2
+
+![Alt text](dev0.png)
+![Alt text](dev2.png)
+
+docker run -d --name assignment-2-I192009 -p 9090:80 --network assignment-2 nginx:1.24.0
+
+![Alt text](dev3.png)
+
+# Q3.
+
+I have run the above command and added screenshots above.
+