E028 is a four-unit course in WGU's Bachelor of Science, Cloud and Network Engineering and its AWS version. It sits late in the program and builds towards the capstone.
The guidebook says it covers the design, implementation and management of hybrid cloud environments, including the integration of on-premises infrastructure, private cloud, public cloud and edge computing into a single hybrid ecosystem.
The challenge is holding many moving parts in mind at once: network design, security, integration and automation. Students who draw the whole picture before configuring any part tend to find the course far easier.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University (WGU) |
| Course | E028, Hybrid Cloud Infrastructure and Orchestration |
| Competency units | 4 |
| Level | Undergraduate |
| Programs | BS Cloud and Network Engineering and its AWS version |
| Prerequisites | None stated in the course description |
What E028 Covers
| Competency (WGU wording, summarized) | What it asks of you |
|---|---|
| Configure networks and security measures for a hybrid cloud environment | Connect and protect on-premises and cloud networks |
| Describe considerations for implementing a hybrid cloud environment | Explain integration of on-premises, private, public and edge components |
| Manage workflows of a hybrid cloud environment using orchestration tools | Automate and coordinate tasks across environments |
Key Concepts Explained
Connecting Environments
Hybrid networks link a local network to a cloud network, commonly through encrypted tunnels or dedicated connections. Careful address planning matters: the ranges at each end must not overlap, or traffic cannot be routed correctly.
Illustration: An office uses 10.0.0.0/16 and plans a cloud network of 10.0.0.0/16 as well. Traffic to 10.0.1.5 could belong to either side, so routing fails. Changing the cloud range to 10.1.0.0/16 solves it, and the plan records the change.
Identity and Security Across Boundaries
Users should have consistent identities and permissions in both worlds. Security measures such as encryption in transit, firewall rules and logging need to be designed for the whole environment, not each side alone.
Orchestration
Orchestration tools coordinate tasks across systems, for example creating resources, configuring them and updating them in order. The benefits are consistency, speed and a record of what was done.
Typical Assignments and How to Approach Them
| Task element | What it tests | How to approach it |
|---|---|---|
| Network and security configuration | Practical skill | Document addressing, routes, rules and tests |
| Hybrid considerations | Design reasoning | Discuss integration, latency, data location and cost |
| Orchestration workflow | Automation thinking | Describe the steps, order and checks in each workflow |
Design Considerations Table
The second competency asks for considerations, which are easiest to present in a table. Fill one row per component type in your scenario.
| Component | Consideration | Question to answer |
|---|---|---|
| On-premises | Existing hardware and links | What stays local and why? |
| Private cloud | Control and compliance | Which data needs it? |
| Public cloud | Scale and cost | Which workloads benefit? |
| Edge | Latency | What must be processed near users? |
A Study Approach for Each Competency
For the configuration competency, begin with a topology diagram showing both networks, the link between them and the security measures at each point. Build the connection first, test basic reachability, then add security rules and test again. Small steps make faults easy to locate.
For the considerations competency, think about what moves and what stays. Some workloads need to remain local for latency or compliance, others gain from cloud scale, and edge locations handle work close to users.
For the orchestration competency, write each workflow as an ordered list of steps with the check that follows each one. Then show how the tool repeats the workflow reliably, which is the main reason to orchestrate at all.
Weak and Strong Workflow Descriptions
When describing orchestration, specifics matter. Compare the two descriptions below.
| Weak | Stronger |
|---|---|
| The tool automates the setup. | The workflow creates the network, then the servers, then applies security rules, then runs a connectivity test. If the test fails, it stops and reports which step failed. |
| Security is handled in the cloud. | Traffic between sites is encrypted, only two ports are open between tiers, and logs from both environments go to one place for review. |
Final Review Before You Submit
Before submitting, read your documentation as someone who has never seen the environment. Can they redraw the topology from your description, and can they tell why each security measure is there? Missing reasons are the most common gap.
- Address ranges are listed and do not overlap.
- Each connection and security rule has a stated purpose.
- Every orchestration workflow is described step by step with its checks.
- Test results are recorded, including at least one failure and its fix.
Where Students Get Stuck
- Overlapping addresses. Plan ranges before building anything.
- Security on one side only. Check rules and logging at both ends and on the link.
- Manual work called orchestration. Show workflows that are repeatable and ordered.
- No testing evidence. Record how you confirmed connectivity and policy.
Study Tips for E028
- Draw the full topology first and label every address range.
- Run a simple connectivity test after each change.
- Keep orchestration scripts or definitions short and commented.
- Match rubric lines to headings.
How We Help with E028
Send the task, your notes and the rubric. A writer can explain the design, prepare a model write-up, or review your documentation. This is study support only: we do not access lab environments, and you complete your own work under WGU's academic integrity policy.
GradeEssays is independent of Western Governors University. Orders are written from scratch, include free revisions within the scope of your original request, and are refunded in full if late.
Get Your Hybrid Design Explained
Share the task, your draft and feedback. We help you describe integration choices and workflow logic.
Start My E028 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
The guidebook lists 4.
An environment integrating on-premises infrastructure, private cloud, public cloud and edge computing.
None is stated in the course description.
It involves tools that automate workflows; check your task for the tools and scripting expected.
It sits late in the program, shortly before the capstone courses.
Yes. We check clarity, completeness and rubric match, and explain what to improve.