This four-week HPE0-G05 study plan is designed to help you build a complete, structured, and practical understanding of HPE Morpheus Enterprise Software. The plan is organized around the official exam’s five core knowledge areas and follows a progressive path from foundational concepts to full end-to-end application deployment. Each week focuses on a specific group of skills, while each day provides clear learning goals, detailed tasks, and focused study cycles based on the Pomodoro method and the forgetting curve. By following this plan, you will develop both conceptual mastery and practical reasoning abilities necessary for confidently passing the HPE0-G05 exam.

Week 1 — Mastering Morpheus Automation Core

Cypher, Archives, Tasks, Workflows, Script Templates, File Templates

Weekly Goal

By the end of Week 1, you should be able to clearly explain and practically work with:

• What Cypher is and how to store & retrieve secrets

• How Archives store reusable files

• How Tasks are constructed and executed

• How Workflows orchestrate Tasks across tiers

• How Script Templates and File Templates are used in provisioning

• How automation components interact during provisioning

This week builds the foundation for all other topics.

Daily Method

Each day:

• 5 Pomodoros (25 min each + breaks)

• Follow the built-in review cycle (Ebbinghaus curve):

  • Review today’s notes right after learning (10 min)

  • Review again on the next day (15 min)

Day 1 — Understanding Morpheus Automation Architecture

Daily Goal

Gain a complete conceptual map of automation components and how they interact during provisioning.

Content to Study

• Core Morpheus objects: Cloud, Group, Instance, App, Tenant

• Automation pipeline:

  • Inputs → Variables → Tasks → Workflows → Templates

• Workflow stages:

  • Pre-provision → Provision → Post-provision

• Where automation executes:

  • Morpheus agent, guest OS, remote scripts, local execution

Tasks

Task 1 (Pomodoro 1): Automation Map

• Draw a full automation flow:

  • User request → Inputs → Pre-provisioning variables
    → Tasks → Workflow → Script/File Templates → Provisioned instance

• Annotate which components act before, during, after provisioning.

Task 2 (Pomodoro 2): Concept Deep Dive
Write explanations (in your own words) for:

• Task vs Workflow

• Inline script vs Template script

• Pre-provisioning stage vs Post-provision

Task 3 (Pomodoro 3): Component Identification Exercise
From your existing notes, classify every automation component into:

• Execution

• Orchestration

• Configuration

• Secret storage

• File storage

Task 4 (Pomodoro 4): Scenario Thinking
Create 3 realistic scenarios:

• Deploying a web server

• Deploying a 3-tier app

• Adding monitoring during provisioning

Identify:

• Which Tasks needed

• Which Workflows needed

• Which Templates needed

Task 5 (Pomodoro 5): Mini-Quiz (self-made)
Write 10 quiz questions to test yourself.

Day 2 — Cypher (Secure Secrets Storage)

Daily Goal

Understand Cypher completely: structure, storage, RBAC, usage in automation.

Content to Study

• Cypher purpose: store passwords, tokens, API keys

• Cypher path structure

• RBAC interaction

• Cypher interpolation syntax ${cypher:/path/key}

• Good practices for secure automation

Tasks

Task 1: Cypher Structure Mastery (Pomodoro 1)
Design a realistic Cypher tree including:

• app credentials

• DB credentials

• ssh keys

• cloud access secrets

Example path patterns:

secret/app/frontend/apiKey
secret/db/prod/password
secret/cloud/aws/apiKey
secret/ssh/automationKey

Write why each path belongs where it is.

Task 2: Access Control Exercise (Pomodoro 2)
For each Cypher secret, define:

• which roles can read it

• which roles cannot

• how tenant separation affects access

Task 3: Script Usage (Pomodoro 3)
Create 5 examples of Cypher usage:

• in Bash scripts

• in PowerShell

• in File Templates

• in HTTP Tasks

• in Blueprint variables

Task 4: Security Best Practices (Pomodoro 4)
Write a “Cypher security checklist” including:

• rotation schedule

• masking strategy

• RBAC enforcement

• audit approach

Task 5: Realistic Scenario (Pomodoro 5)
Design a scenario:
“Deploying an app with DB credentials stored in Cypher”
Write step-by-step how secrets flow through the system.

Day 3 — Archives (Reusable Artifact Storage)

Daily Goal

Understand how Morpheus Archives act as file repositories for scripts, configs, app content.

Content to Study

• Archive purpose

• How files are referenced in Tasks

• File versioning strategies

• How Archives support automation consistency

Tasks

Task 1: Build an Archive Hierarchy (Pomodoro 1)
Design an archive folder structure:

configs/
  nginx/
    nginx.conf
  app/
    app.yml
scripts/
  init/
    install.sh
packages/
  webapp/
    v1.0/
    v1.1/

Task 2: Integration Practice (Pomodoro 2)
Write 4 examples of how an Archive file is used in:

• Script Task

• File Template

• Workflow

• Blueprint deployment

Task 3: Versioning Strategy (Pomodoro 3)
Create a versioning guideline:

• When to version

• How to prevent breaking existing deployments

• Branch-like organization

Task 4: Failure Handling (Pomodoro 4)
Describe what happens if:

• archive file missing

• wrong version used

• permission insufficient

Task 5: Real Use Case (Pomodoro 5)
Document a scenario:
“Using Archive-based nginx.conf to configure web server through a Workflow.”

Day 4–5 — Tasks (Automation Execution Units)

Two-Day Goal

Completely understand Task types and be able to design Tasks for real deployment needs.

Content to Study

• Script Tasks

• HTTP Tasks

• Ansible Tasks

• Local execution vs remote execution

• Error handling & exit codes

• Passing Inputs / Variables / Cypher into Tasks

Tasks

Day 4

Task 1: Compare Task Types (Pomodoro 1)
Write a comparison table with columns:

• What it does

• When to use

• Pros

• Cons

• Real example

Task 2: Create 3 Script Tasks (Pomodoro 2)

• Install Nginx

• Download file from Archive

• Configure system settings

Include:

• script content

• variables used

• expected outputs

Task 3: HTTP Task Practice (Pomodoro 3)
Write an HTTP Task to:

• POST data to an ITSM system

• GET data from a CMDB

Include headers & JSON example.

Task 4: Targeting Logic (Pomodoro 4)
Explain when Tasks run:

• on instance

• on container

• on Morpheus worker

• on remote host

Task 5: Error Strategy (Pomodoro 5)
Create rules:

• when Task failure should stop workflow

• when errors can be safely ignored

Day 5

Task 1: Task + Template Integration (Pomodoro 1)
Write a Task that uses a Script Template.

Task 2: Task Input Mapping (Pomodoro 2)
Design Tasks that use:

• ${input.env}

• ${input.region}

• ${cypher:/secret/db/password}

Explain the flow.

Task 3: Debug Strategy (Pomodoro 3)
Write procedures for debugging failed tasks.

Task 4: Task Library Creation (Pomodoro 4)
Create a list of “common enterprise tasks”:

• install package

• join domain

• register to CMDB

• deploy config file

Task 5: Deep Scenario Design (Pomodoro 5)
Create a Task sequence for deploying a 2-tier app.

Day 6 — Workflows (Task Orchestration)

Daily Goal

Understand how Tasks are chained together and how sequencing works.

Content to Study

• Workflow types

• Pre/Post provision

• Workflow → Tier → Instance mapping

• Error handling

• Parameter passing across Tasks

Tasks

Task 1: Build a Workflow Diagram (Pomodoro 1)
Draw a workflow with:

• 5 tasks

• dependencies

• targets

• pre/post phases

Task 2: Write Real Workflow (Pomodoro 2)
A workflow for:

• Validate Inputs

• Configure OS

• Deploy app code

• Register monitoring

Task 3: Passing Variables (Pomodoro 3)
Show how one Task passes values to the next.

Task 4: Failure Simulation (Pomodoro 4)
Document behavior if Task #3 fails:

• stop workflow?

• continue?

Task 5: Tier Workflow Study (Pomodoro 5)
Explain how different tiers use different workflows in a multi-tier blueprint.

Day 7 — Script Templates & File Templates

Daily Goal

Understand how templates standardize configuration & scripting.

Content to Study

• Script Template structure

• File Template variable interpolation

• Application configuration deployment

• Template + Workflow combined usage

Tasks

Task 1: Create 3 Script Templates (Pomodoro 1)

• init.sh

• deploy_app.sh

• restart_service.sh

Task 2: File Template Creation (Pomodoro 2)
Create a full config file with variables:

app:
  env: ${input.env}
  version: ${input.version}
database:
  host: ${db.host}
  pass: ${cypher:/secret/db/password}

Task 3: Template Rendering Flow (Pomodoro 3)
Explain:
Input → variable → File Template → rendered file → instance

Task 4: Template Versioning (Pomodoro 4)
Define how to avoid breaking older deployments.

Task 5: End-to-End Example (Pomodoro 5)
Show how a File Template is:

• stored

• rendered

• deployed

• applied

Week 2 — Mastering Variables and Identity

Focus areas:

1. Variable Contexts

2. Morpheus Variables Overview

3. Pre-provisioning Variables

4. Authentication

5. RBAC and Multi-tenancy

6. Morpheus CLI

7. Morpheus API (Headers, Body, Response Codes)

Weekly objective:
By the end of Week 2, you should be able to:

• Explain all variable types and scopes in Morpheus

• Understand variable precedence, inheritance, and runtime evaluation

• Design naming conventions and provisioning rules completely driven by variables

• Authenticate using token-based authentication in CLI and API

• Send real-world API requests with correct headers and JSON body

• Interpret 2xx, 4xx, 5xx error codes in Morpheus responses

Daily method:
Each day:

• 5 Pomodoros (25 minutes each + breaks)

• 10-minute review immediately after learning

• 15-minute spaced review the next day

Day 8 — Variable Contexts (Foundational Understanding)

Daily goal:
Understand what variable contexts are, how scoping works, and how variables flow through the system.

Content to study:

• Definition of variable context

• Global, Tenant, Group, Cloud, App, Blueprint, Instance, Workflow contexts

• How contexts affect visibility and precedence

• Importance of scoping in multi-tenant systems

Tasks:

Pomodoro 1: Document All Context Layers
Write a detailed explanation of each context layer, including:

• What defines the context

• What types of variables appear in each

• How an object inherits variables from its parent layer

Pomodoro 2: Context Comparison Chart
Create a comparison table with columns:
context name, example variables, use cases, precedence level, example scenario.

Pomodoro 3: Overlapping Variables Exercise
Write three scenarios where the same variable name exists at different levels.
Describe which value wins and why.

Pomodoro 4: Context Mapping to Real Deployment
Design a sample application and map where each variable would come from:

• cloud

• group

• instance

• workflow

• user input

• pre-provision formulas

Pomodoro 5: Self-evaluation Questions
Write 10 comprehension questions about variable contexts and answer them.

Day 9 — Variables Overview (Built-in, Custom, Secret, Tags)

Daily goal:
Master all variable types, how they interact, and where they are consumed.

Content to study:

• Built-in system variables (instance.id, instance.name, cloud.name, etc.)

• Custom variables from Inputs

• Secrets via Cypher

• Metadata variables (tags/labels)

• Interpolation syntax patterns in Scripts, Templates, Workflows

Tasks:

Pomodoro 1: List All System Variables
Write a list of at least 20 built-in variables, including:

• instance.*

• app.*

• cloud.*

• tenant.*
  Describe how each one may be used in a script.

Pomodoro 2: Custom Variables from Inputs
Create 5 Input definitions and map them to variables:
environment, region, appCode, vmSize, version.

Pomodoro 3: Secret Variable Usage
Write 5 examples of Cypher interpolation in different environments:
Script Template, bash script, PowerShell script, File Template, HTTP Task.

Pomodoro 4: Metadata and Tags
Design a tagging scheme for an enterprise deployment and list how variables expose tag values.

Pomodoro 5: Variable Validation
Create rules for validating variables before provisioning begins.

Day 10 — Pre-provisioning Variables

Daily goal:
Understand how variables become finalized before provisioning and how they influence critical decisions.

Content to study:

• The pre-provision stage

• Inputs → pre-provision variables

• Request scripts

• Option list selections

• Cloud/Group defaults and policy overrides

• Naming conventions based on pre-provision data

Tasks:

Pomodoro 1: Pre-provision Variable Flow
Write a step-by-step flow from user Inputs to final pre-provision variables.

Pomodoro 2: Naming Convention Design
Design three naming conventions:

• instance hostname

• app name

• volume naming
  Use pre-provision variables to compute them.

Pomodoro 3: Decision Logic Examples
Write three examples where pre-provision variables determine:

• plan

• region

• OS image

• subnet
  Provide conditional examples.

Pomodoro 4: Request Script Interaction
Describe how Request Scripts modify pre-provision variables and give two examples.

Pomodoro 5: Pre-provision Validation Rules
Define validation rules that must run before provisioning.

Day 11 — Authentication, RBAC, Multi-tenancy (Part 1)

Daily goal:
Understand authentication mechanisms and the identity model inside Morpheus.

Content to study:

• Local user authentication

• LDAP / AD authentication

• SAML and SSO concepts

• User → Role → Permission model

• Tenant isolation and resource boundaries

Tasks:

Pomodoro 1: Authentication Method Comparison
Write a table comparing local auth, LDAP, SAML based on:
configuration, strengths, weaknesses, use cases.

Pomodoro 2: Role and Permission Mapping
Define three roles:

• Developer

• Administrator

• Auditor
  Write what each role can and cannot do.

Pomodoro 3: Tenant Isolation Models
Explain how tenants isolate:

• users

• clouds

• blueprints

• instances

• Cypher secrets

Pomodoro 4: Real-world Scenario
Design a scenario:
A service provider hosts three customers.
Document how RBAC and tenancy prevent cross-access.

Pomodoro 5: Authentication Troubleshooting
List common problems:

• expired token

• wrong tenant

• missing role
  and give solutions.

Day 12 — Authentication, RBAC, Multi-tenancy (Part 2)

Daily goal:
Apply identity and access control knowledge to real automation scenarios.

Content to study:

• Relationships between users, tenants, roles

• Cypher access control

• Workflow permissions

• Instance management permissions

• Cloud management permissions

Tasks:

Pomodoro 1: Permission Impact Analysis
Analyze how a missing permission affects:

• running workflows

• accessing clouds

• using Cypher

• viewing instances

Pomodoro 2: Build Access Profiles
Define two tenant configurations:
internal IT tenant and external customer tenant.
List differences in:

• cloud access

• workflow access

• template access

• Cypher access

Pomodoro 3: Minimal Privilege Automation
Design a limited-permission automation service account.
Specify exactly what roles it requires.

Pomodoro 4: Multi-tenant Conflict Scenarios
Write three conflict cases:

• user sees "403 Forbidden"

• user cannot access workflow

• user cannot view instance
  Explain resolution.

Pomodoro 5: Identity Review
Summarize RBAC behavior in your own words.

Day 13 — Morpheus CLI

Daily goal:
Use the CLI for authentication, listing, creating, and managing automation components.

Content to study:

• CLI login

• Profiles

• Token storage

• Commands for managing instances, tasks, workflows, templates

Tasks:

Pomodoro 1: CLI Installation and Configuration
Document full setup steps and how to configure the appliance URL.

Pomodoro 2: Authentication Exercise
Perform login using:

• username/password

• token
  Write what files are created by the CLI.

Pomodoro 3: CLI Commands Library
List 20 important commands for:

• instances

• tasks

• workflows

• templates

• clouds

• groups

Pomodoro 4: Scripted CLI Usage
Write a shell script that uses CLI to:

• create instance

• run workflow

• retrieve instance status

Pomodoro 5: CLI Troubleshooting Table
Document issues like:

• invalid token

• profile mismatch

• SSL errors
  and solutions.

Day 14 — Morpheus API (Headers, Body, Responses)

Daily goal:
Understand how to interact with the API and interpret responses.

Content to study:

• Structure of REST API

• Authorization header (Bearer token)

• Content-Type and Accept headers

• POST vs GET vs PUT vs DELETE

• Pagination

• Error codes and meanings

Tasks:

Pomodoro 1: API Request Anatomy
Write the complete structure of an API request including:
URL, headers, body, method, expected response.

Pomodoro 2: Build Two Real API Requests
Construct example JSON bodies for:

• creating an instance

• creating a workflow

Pomodoro 3: Response Code Interpretation
Create a table explaining:
200, 201, 204, 400, 401, 403, 404, 500, 503
and what each means in Morpheus.

Pomodoro 4: Error Analysis
Write three example failures (401, 403, 404).
Explain the root cause and how to fix each.

Pomodoro 5: Pagination Practice
Write examples of requesting a paginated list of instances using:
max, offset, sort, filters.

Week 3 — Mastering Dynamic Forms and Data Interaction

Focus areas:

1. Option Lists

2. Inputs

3. Request Scripts

4. Translation Scripts

Weekly objective:
By the end of Week 3, you will be able to:

• Build static and dynamic Option Lists

• Build Inputs that accept user selections and generate variables

• Use Request Scripts to validate, enrich, or transform user requests

• Use Translation Scripts to normalize external API responses

• Understand how dynamic forms and scripts drive pre-provisioning variables

• Integrate forms with blueprints and automations

Daily method:
Each day:

• 5 Pomodoros (25 minutes each, with breaks)

• 10-minute review immediately after learning

• 15-minute spaced review on the next day

Day 15 — Option Lists (Static)

Daily goal:
Understand static Option Lists, their structure, and their usage in Inputs.

Content to study:

• What Option Lists are

• JSON structure: name/value pairs

• Static lists vs dynamic lists

• When static lists are appropriate

• How Option Lists feed Inputs

Tasks:

Pomodoro 1: Static Option List Definition
Create 5 static Option Lists for common enterprise fields:
environment, region, vmSize, osType, complianceLevel.

Pomodoro 2: JSON Structure Practice
Write JSON definitions for at least 3 Option Lists, ensuring the proper name/value structure.

Pomodoro 3: Input Integration
Attach your static Option Lists to Inputs and document how variables appear (${input.env}, ${input.region}, etc.).

Pomodoro 4: Validation Logic
Define when static lists must be used instead of dynamic lists (for governance and standardization).

Pomodoro 5: Real Scenario
Design a scenario in which static Option Lists enforce standardization across multiple teams.

Day 16 — Option Lists (Dynamic Script-backed)

Daily goal:
Learn how to build dynamic Option Lists that are generated by scripts.

Content to study:

• Script-backed Option Lists

• Required output format

• How Morpheus executes scripts

• Runtime context of lists

• Use cases for dynamic option generation

Tasks:

Pomodoro 1: Script-backed Option List Examples
Write 2 script examples (bash or python) that output a valid Option List JSON structure.

Pomodoro 2: Parameterized Logic
Create a dynamic Option List that adjusts choices based on another Input (e.g., region drives VM size list).

Pomodoro 3: Error Handling
Explain how Morpheus behaves when a dynamic list fails and how to mitigate issues.

Pomodoro 4: Performance Considerations
Document how often lists execute and how to avoid performance bottlenecks.

Pomodoro 5: Real Integration Scenario
Write one scenario where a dynamic list pulls data from:

• CMDB

• monitoring system

• environment configuration service

Day 17 — Option Lists (API-backed)

Daily goal:
Understand how to build Option Lists backed by external APIs.

Content to study:

• Remote Option Lists

• Calling REST APIs to populate lists

• Authentication with external systems

• Handling response errors

• Standardizing API responses for Morpheus

Tasks:

Pomodoro 1: Create an API-backed Option List
Design a list that gets application versions from an external endpoint.

Pomodoro 2: Response Mapping
Take an example external API response and reformat it into Option List JSON.

Pomodoro 3: Error Simulation
Simulate failures such as 401 or 404 responses and document expected behavior and fallback strategies.

Pomodoro 4: Authentication Methods
Describe how external API authentication works (token, basic auth, no auth).

Pomodoro 5: End-to-End Example
Document a complete flow:
User Input → Option List API call → returned choices → user selection becomes ${input.version}.

Day 18 — Inputs (Form Field Design)

Daily goal:
Understand how Inputs allow users to define variables used during automation.

Content to study:

• Field types (text, number, select, multi-select, password, checkbox)

• Field dependencies (conditional visibility)

• Default values

• Required vs optional

• How Inputs become variables

Tasks:

Pomodoro 1: Form Field Library
Create at least 10 Inputs commonly used in enterprise deployments:
env, region, owner, costCenter, osType, version, role, priority, instanceCount, backupPolicy.

Pomodoro 2: Conditional Logic
Define 3 Inputs whose visibility depends on other Inputs (e.g., show DB size only when tier=database).

Pomodoro 3: Variable Mapping Exercise
Show how each Input becomes a variable and where the variable is referenced:
script, workflow, template, API request.

Pomodoro 4: Governance Use Cases
Document how Inputs enforce compliance, such as requiring costCenter for all new VMs.

Pomodoro 5: Error Prevention
List cases of Input misconfiguration and how to avoid them.

Day 19 — Request Scripts

Daily goal:
Understand how Request Scripts run before provisioning to validate or modify request data.

Content to study:

• Purpose of Request Scripts

• Pre-provisioning influence

• Interaction with Inputs

• API calls inside scripts

• Error handling strategies

Tasks:

Pomodoro 1: Create Request Script Examples
Write 3 Request Scripts:
validate costCenter, validate projectID, validate allowed regions.

Pomodoro 2: External System Integration
Document how a Request Script queries a CMDB to enrich provisioning data.

Pomodoro 3: Dynamic Default Assignment
Write logic that sets default vmSize based on Input env.

Pomodoro 4: Pre-provision Failure Handling
Write scenarios where a Request Script intentionally stops provisioning with a message.

Pomodoro 5: Full Request Phase Flow
Write a flow diagram:
User Inputs → Request Script → Variables → Provisioning Stage.

Day 20 — Translation Scripts

Daily goal:
Understand how Translation Scripts reshape or normalize data before Morpheus consumes it.

Content to study:

• What Translation Scripts are

• When they are used (catalog integration, external option lists)

• Difference from Request Scripts

• Input/Output requirements

Tasks:

Pomodoro 1: Build a Translation Script
Create a script that converts an external system’s JSON format to Morpheus Option List format.

Pomodoro 2: Normalization Logic
Take inconsistent external assets and normalize them into consistent name/value pairs.

Pomodoro 3: Use Case Mapping
Write three real-world scenarios requiring Translation Scripts:
external CMDB, service catalog integration, dynamic API normalization.

Pomodoro 4: Failure Simulation
Describe what happens if a Translation Script produces invalid JSON.

Pomodoro 5: Integration Flow
Map how Translation Scripts integrate with Option Lists and Request Scripts.

Day 21 — Integration Review and Practice Scenarios

Daily goal:
Combine everything learned into end-to-end dynamic form design.

Content to study:

• Option Lists (static, dynamic, API-backed)

• Inputs

• Request Scripts

• Translation Scripts

• Pre-provisioning variables

Tasks:

Pomodoro 1: Design Full Dynamic Request Form
Create a full Input set with option lists for:
environment, appVersion, region, vmSize, dbSize, osFamily.

Pomodoro 2: Create Dependencies
Add conditional visibility logic.

Pomodoro 3: Add Request Script Logic
Validate the request and enrich fields.

Pomodoro 4: Add Translation Script
Normalize external version data into a usable Option List.

Pomodoro 5: Build an End-to-End Provisioning Document
Write a full flow describing dynamic request → validated → enriched → provisioned.

Week 4 — Mastering Multi-tier Blueprints and Application Deployments

(Knowledge Point #5)

Focus areas:

1. Multi-tier application blueprints

2. Tier design, dependencies, orchestration

3. Workflow integration inside blueprints

4. Application deployments

5. Day-2 operations

6. Full end-to-end system automation

Weekly objective:
By the end of Week 4, you should be able to:

• Explain clearly what multi-tier blueprints are and how Morpheus structures them

• Design an application blueprint with multiple tiers and dependencies

• Attach workflows and templates to individual tiers

• Understand the full deployment pipeline from request → provision → configure → post-provision

• Understand Day-2 operations (scaling, reconfiguring, lifecycle actions)

• Build a complete application deployment plan integrating everything learned in Weeks 1–3

Daily method:
Each day:

• 5 Pomodoros (25 minutes each + breaks)

• 10-minute same-day review

• 15-minute spaced review on the following day

Day 22 — Introduction to Multi-tier Blueprints

Daily goal:
Understand the role of multi-tier blueprints and what problems they solve.

Content to study:

• What a tier is

• How tiers form a complete application

• Tier examples: web, application, database, cache, message bus

• How Morpheus expresses multi-tier design

• Relationship between tiers, instances, workflows, variables

Tasks:

Pomodoro 1: Blueprint Structure Overview
Write an in-depth description of every component of a multi-tier blueprint:
tiers, networks, workflows, templates, variables, dependencies.

Pomodoro 2: Tier Analysis
Select a typical 3-tier enterprise application and describe:
web tier responsibilities, app tier responsibilities, DB tier responsibilities.

Pomodoro 3: Dependency Logic
Explain why DB must deploy before app, and app before web.
Write a short dependency map.

Pomodoro 4: Blueprint Concept Mapping
Map how Inputs, Option Lists, Request Scripts, and Variables feed into a multi-tier blueprint.

Pomodoro 5: Comparison Exercise
Compare a simple single-instance blueprint with a multi-tier blueprint and list advantages.

Day 23 — Tier Design (Instances, Plans, Images, Networks)

Daily goal:
Understand how tier configuration defines provisioning behavior.

Content to study:

• How plans, sizing, images, and networks are defined per tier

• How workflows attach to tiers

• How tier-level variables override or inherit values

• How multiple instances of the same tier scale

Tasks:

Pomodoro 1: Per-tier Configuration Mapping
Write a detailed breakdown of settings for a tier:
plan, image, networks, security groups, volumes.

Pomodoro 2: Workflow Attachment
Document how workflows attach to a specific tier and run in the correct sequence.

Pomodoro 3: Variable Overriding Exercise
Show examples of how tier variables override app variables.

Pomodoro 4: Scaling Logic
Describe how Morpheus handles:
multiple web nodes, clustered app tiers, multi-node DB clusters.

Pomodoro 5: Tier Role Summary
Write a complete description of:
what makes a tier different from an instance,
and what multi-tier orchestration adds.

Day 24 — Workflow Integration in Blueprints

Daily goal:
Understand how Workflows operate inside blueprints and across tiers.

Content to study:

• Tier workflows

• App-level workflows

• Pre-provision and post-provision integration

• Cross-tier orchestration patterns

Tasks:

Pomodoro 1: Multi-tier Workflow Flowchart
Draw a flowchart showing workflow execution across tiers.

Pomodoro 2: Tier-specific Workflow Example
Develop a workflow for each tier (web/app/db) and list the difference.

Pomodoro 3: Global Workflow Example
Create an app-level workflow for CMDB registration or environment tagging.

Pomodoro 4: Cross-tier Event Handling
Explain how one tier’s workflow completion signals the next tier to begin provisioning.

Pomodoro 5: Workflow Collision Prevention
Document how to avoid:
race conditions, conflicting configurations, misordered steps.

Day 25 — Application Deployment Flow (Request to Post-Provision)

Daily goal:
Master the entire deployment lifecycle.

Content to study:

• Request phase

• Pre-provisioning variable calculation

• Provisioning across tiers

• Post-provision workflows

• Configuration file deployment

• Integration with monitoring, backup, CMDB

Tasks:

Pomodoro 1: Deployment Pipeline Deep Dive
Write the complete sequence from user request to final deployment.

Pomodoro 2: Pre-provisioning Analysis
List every variable needed before the first VM is created and where each originates.

Pomodoro 3: Tier Provisioning Flow
Describe how Morpheus:
creates DB → configures DB → creates App → configures App → creates Web → configures Web.

Pomodoro 4: Post-Provision Action Mapping
Document examples:
register monitoring, register backup policy, apply tags.

Pomodoro 5: Deployment Issues and Solutions
Write 5 example issues and how to solve them:
incorrect sequencing, missing variables, failed tasks, network misconfiguration.

Day 26 — Day-2 Operations

Daily goal:
Understand operational lifecycle functions after deployment.

Content to study:

• Scaling operations

• Reconfiguring instances

• Running operational workflows

• Backup, restore, snapshots

• Expiration and lease policies

• Governance policies

Tasks:

Pomodoro 1: Scaling Logic
Explain how horizontal scaling of a tier works and how state is handled.

Pomodoro 2: Reconfiguration Paths
Document how to update config files or restart services in a running app.

Pomodoro 3: Operational Workflows
Design three day-2 workflows:
restart service, apply new version, rotate credentials.

Pomodoro 4: Governance
Explain how expiration and lease rules work for apps.

Pomodoro 5: Policy Impact
Document how cost, quota, and compliance policies affect application operation.

Day 27 — Full Multi-tier Blueprint Design

Daily goal:
Create a complete 3-tier application blueprint using everything learned in Weeks 1–3.

Content to study:

• Tier modeling

• Workflows

• Variables

• Templates

• Dependencies

• Option lists and Inputs

• Request scripts

• Pre-provisioning logic

• Multi-tier orchestration

Tasks:

Pomodoro 1: Design Inputs and Option Lists
Define Inputs for region, env, version, instanceCount, dbSize.

Pomodoro 2: Build Tier Definitions
Define web tier, app tier, DB tier, including:
plan, image, networks, workflows.

Pomodoro 3: Add Automation Logic
Add all necessary tasks, workflows, templates to each tier.

Pomodoro 4: Create Dependencies
Define deployment order and dependency reasons.

Pomodoro 5: Create a Document
Write a formal blueprint specification with sections:
tiers, workflows, variables, templates, dependencies, lifecycle behavior.

Day 28 — End-to-End Practice + Full Knowledge Review

Daily goal:
Integrate all previous concepts into a realistic end-to-end scenario.

Content to study:

• Everything learned in Weeks 1–3

• Practical integrations

• Exam-style reasoning

Tasks:

Pomodoro 1: End-to-End Deployment Exercise
Write a complete step-through scenario from request → dynamic form → provisioning → workloads configured → app online.

Pomodoro 2: Troubleshooting Collection
List the top 20 issues and how you would troubleshoot them.

Pomodoro 3: Exam Knowledge Map
Create a structured map of all knowledge points with relationships.

Pomodoro 4: Self-Review and Mini Quiz
Write 15 exam-style conceptual questions and answer them.

Pomodoro 5: Final Adjustments
Identify weak areas and define which topics need extra review during your final 2–3 days before the exam.

---