VMware Cloud Foundation: Automate and Operate [V9.0] — Lesson 2: Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions

Learning Objectives

• Assess dependencies, controls, resilience, and the intended service outcome for Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions.
• Demonstrate the workflow and leave reproducible evidence in catalog deployment trace and policy decision record.
• Recommend a preventive improvement after resolving a template deploying successfully but selecting a noncompliant network profile.

Detailed Topics

• Templates
• Images
• Flavors
• Networks
• Storage profiles
• Catalog content
• Deployments
• Policies
• Approvals
• Leases
• And day-two actions
• Decision ownership, prerequisites, and acceptance evidence for Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

Using realistic infrastructure, identities, and workloads, the instructor demonstrates Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions. Checkpoints are captured in catalog deployment trace and policy decision record, with discussion of alternatives, side effects, and acceptance conditions.

Hands-On Exercise

Build or execute Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions for a defined scenario. Introduce the condition “a template deploying successfully but selecting a noncompliant network profile,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in catalog deployment trace and policy decision record.

1. Map the current workflow and mark where the expected result can first be observed.
2. Run the scenario while preserving timestamps, object identifiers, and relevant output.
3. Apply a reversible correction only after evidence supports the cause.
4. Retest the original case plus an unaffected case and update the handover record.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how catalog deployment trace and policy decision record should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid changing multiple settings at once while troubleshooting Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions. Preserve the failing example, review catalog deployment trace and policy decision record, and verify whether “a template deploying successfully but selecting a noncompliant network profile” is the root cause. After remediation, confirm downstream effects and add a monitoring action.

Validation Checklist

• The requirement for Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions is linked to an owner and observable acceptance condition.
• Catalog deployment trace and policy decision record contains enough detail for another practitioner to repeat the check.
• Normal operation, one boundary condition, and the identified failure path have been tested.
• Access, security, downstream impact, rollback, monitoring, and support ownership are recorded.

Lesson Outcome

Learners can apply Templates, images, flavors, networks, storage profiles, catalog content, deployments, policies, approvals, leases, and day-two actions, explain the decisions made, and defend the result with catalog deployment trace and policy decision record.