WGU E027 | TASK 2 INFRASTRUCTURE IMPLEMENTATION REPORT
IMPLEMENTATION REPORT
Azure IaaS Web Server Deployment and
Verification
NovaMart Retail Group | Ubuntu, Nginx, TLS, iperf3, and Azure Monitor
Submission Information Details
Course WGU E027 - Virtualization and Infrastructure as a Service
Assessment Task 2 - Infrastructure Implementation Report
Student Name [Your Name]
Student ID [Your Student ID]
Deployment date [Date and time, including time zone]
Azure subscription/lab [WGU lab subscription or approved alternative]
Academic evidence requirement: This report contains screenshot placeholders, exact capture instructions, and
example narrative. Replace every placeholder with screenshots from your own authorized deployment. Do not
submit sample, borrowed, generated, or altered evidence. Redact subscription IDs, public IP addresses if
required, email addresses, and other sensitive identifiers without obscuring the configuration being assessed.
Page 1
, WGU E027 | TASK 2 INFRASTRUCTURE IMPLEMENTATION REPORT
Implementation Overview
This report documents the deployment of a secured Ubuntu Server web host in Microsoft Azure for NovaMart Retail
Group. The implementation translates the Task 1 architecture into a small, verifiable IaaS proof of concept. The build
uses one resource group, one virtual network, a dedicated web subnet, one subnet-level network security group, one
Ubuntu Server 24.04 LTS virtual machine, Nginx, a locally generated self-signed TLS certificate, iperf3, and Azure
Monitor platform metrics.
The proof of concept is intentionally sized for a short-lived academic lab. It demonstrates provisioning, network
segmentation, VM configuration, package management, secure administration, HTTPS binding, diagnostic testing, and
cloud monitoring. It does not claim production readiness: the self-signed certificate is not publicly trusted, the web tier
is a single VM, and public SSH is retained only if the lab requires it. A production system would use a trusted certificate,
multiple instances, private administration, application-aware monitoring, backup, and stricter change governance.
Component Selected configuration Reason
Region [Use the region allowed by the lab; example: East Keep all resources together and select a
US] permitted region with quota.
Resource group rg-e027-novamart-lab Creates a clean lifecycle and deletion
boundary.
VNet / subnet vnet-e027 10.27.0.0/16; snet-web 10.27.1.0/24 Provides nonoverlapping private addressing
and a distinct web security boundary.
NSG nsg-e027-web Allows only required inbound ports; source-
restrict SSH.
VM vm-e027-web01; Standard B1s; Ubuntu Server Low-cost lab size and a current LTS Linux
24.04 LTS image.
Web/TLS Nginx + self-signed RSA-2048/SHA-256 certificate Demonstrates service installation and HTTPS
binding.
Diagnostics iperf3 loopback plus Azure Monitor CPU/network Produces guest-level and platform-level
charts verification.
Before deployment: Open the current Task 2 rubric in the WGU portal and confirm the required platform,
evidence format, screenshot count, and whether external Azure subscriptions are accepted. The rubric and lab
instructions control if they differ from this report.
Evidence Capture Standard
Capture the Azure breadcrumb, resource name, and the relevant configuration in the same image whenever
possible.
For terminal evidence, include the prompt, command, complete result, and a harmless identity command such
as hostname. Never display a private SSH key or password.
Keep screenshots legible at normal document zoom. Crop irrelevant browser chrome, but do not crop away the
evidence needed to identify the resource or command.
Add a numbered caption under each image and explain what the result proves. A screenshot without
interpretation is weaker evidence.
Use consistent names throughout. If your actual Azure names differ from this model, replace the names in both
prose and captions before submission.
Page 2
IMPLEMENTATION REPORT
Azure IaaS Web Server Deployment and
Verification
NovaMart Retail Group | Ubuntu, Nginx, TLS, iperf3, and Azure Monitor
Submission Information Details
Course WGU E027 - Virtualization and Infrastructure as a Service
Assessment Task 2 - Infrastructure Implementation Report
Student Name [Your Name]
Student ID [Your Student ID]
Deployment date [Date and time, including time zone]
Azure subscription/lab [WGU lab subscription or approved alternative]
Academic evidence requirement: This report contains screenshot placeholders, exact capture instructions, and
example narrative. Replace every placeholder with screenshots from your own authorized deployment. Do not
submit sample, borrowed, generated, or altered evidence. Redact subscription IDs, public IP addresses if
required, email addresses, and other sensitive identifiers without obscuring the configuration being assessed.
Page 1
, WGU E027 | TASK 2 INFRASTRUCTURE IMPLEMENTATION REPORT
Implementation Overview
This report documents the deployment of a secured Ubuntu Server web host in Microsoft Azure for NovaMart Retail
Group. The implementation translates the Task 1 architecture into a small, verifiable IaaS proof of concept. The build
uses one resource group, one virtual network, a dedicated web subnet, one subnet-level network security group, one
Ubuntu Server 24.04 LTS virtual machine, Nginx, a locally generated self-signed TLS certificate, iperf3, and Azure
Monitor platform metrics.
The proof of concept is intentionally sized for a short-lived academic lab. It demonstrates provisioning, network
segmentation, VM configuration, package management, secure administration, HTTPS binding, diagnostic testing, and
cloud monitoring. It does not claim production readiness: the self-signed certificate is not publicly trusted, the web tier
is a single VM, and public SSH is retained only if the lab requires it. A production system would use a trusted certificate,
multiple instances, private administration, application-aware monitoring, backup, and stricter change governance.
Component Selected configuration Reason
Region [Use the region allowed by the lab; example: East Keep all resources together and select a
US] permitted region with quota.
Resource group rg-e027-novamart-lab Creates a clean lifecycle and deletion
boundary.
VNet / subnet vnet-e027 10.27.0.0/16; snet-web 10.27.1.0/24 Provides nonoverlapping private addressing
and a distinct web security boundary.
NSG nsg-e027-web Allows only required inbound ports; source-
restrict SSH.
VM vm-e027-web01; Standard B1s; Ubuntu Server Low-cost lab size and a current LTS Linux
24.04 LTS image.
Web/TLS Nginx + self-signed RSA-2048/SHA-256 certificate Demonstrates service installation and HTTPS
binding.
Diagnostics iperf3 loopback plus Azure Monitor CPU/network Produces guest-level and platform-level
charts verification.
Before deployment: Open the current Task 2 rubric in the WGU portal and confirm the required platform,
evidence format, screenshot count, and whether external Azure subscriptions are accepted. The rubric and lab
instructions control if they differ from this report.
Evidence Capture Standard
Capture the Azure breadcrumb, resource name, and the relevant configuration in the same image whenever
possible.
For terminal evidence, include the prompt, command, complete result, and a harmless identity command such
as hostname. Never display a private SSH key or password.
Keep screenshots legible at normal document zoom. Crop irrelevant browser chrome, but do not crop away the
evidence needed to identify the resource or command.
Add a numbered caption under each image and explain what the result proves. A screenshot without
interpretation is weaker evidence.
Use consistent names throughout. If your actual Azure names differ from this model, replace the names in both
prose and captions before submission.
Page 2
