VMware Cloud Foundation: Automate and Operate [V9.0] – FT — Lesson 3: Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback

Learning Objectives

• Translate a realistic infrastructure or application requirement into an executable approach for Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback.
• Use extensibility workflow test and rollback proof to verify configuration, connectivity, security, and expected behavior.
• Explain how to recover safely when a workflow retry creating duplicate external resources occurs.

Detailed Topics

• Event broker
• Subscriptions
• Workflows
• Custom actions
• APIs
• Source control
• Secrets
• Error handling
• Version promotion
• And rollback
• Decision ownership, prerequisites, and acceptance evidence for Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback, narrating each decision and showing how it contributes to a focused VCF automation capability that delivers policy-controlled catalog services, repeatable deployment workflows, extensible day-two operations, and operational accountability. The demonstration records extensibility workflow test and rollback proof so learners can compare design intent with observable behavior.

Hands-On Exercise

Configure and test Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback with representative infrastructure or application data. Use “a workflow retry creating duplicate external resources” as the troubleshooting challenge, compare hypotheses, retest the affected path, and complete extensibility workflow test and rollback proof for review.

1. Define the requirement and identify dependencies before changing the environment.
2. Create a baseline result that can be compared with later changes.
3. Reproduce the exception and test one hypothesis at a time.
4. Complete the evidence record and obtain peer or instructor review.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how extensibility workflow test and rollback proof should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid changing multiple settings at once while troubleshooting Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback. Preserve the failing example, review extensibility workflow test and rollback proof, and verify whether “a workflow retry creating duplicate external resources” is the root cause. After remediation, confirm downstream effects and add a monitoring action.

Validation Checklist

• The scope of Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback is clear, including what is deliberately excluded from the test.
• Evidence in extensibility workflow test and rollback proof supports each material decision and outcome.
• A negative test demonstrates that controls reject or expose an invalid condition.
• Open risks, owners, due actions, and production safeguards are documented.

Lesson Outcome

Learners can apply Event broker, subscriptions, workflows, custom actions, APIs, source control, secrets, error handling, version promotion, and rollback, explain the decisions made, and defend the result with extensibility workflow test and rollback proof.