VMware Workspace ONE: Skills for UEM [V22.x] — Lesson 3: Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery

Learning Objectives

• Translate a realistic infrastructure or application requirement into an executable approach for Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery.
• Use application rollout test and assignment evidence to verify configuration, connectivity, security, and expected behavior.
• Explain how to recover safely when an application update reaching test devices and production devices at the same time occurs.

Detailed Topics

• Application catalog
• Public and internal apps
• Assignment groups
• Deployment modes
• App configuration
• Managed access
• Updates
• Licensing
• And content delivery
• Decision ownership, prerequisites, and acceptance evidence for Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery, narrating each decision and showing how it contributes to a Workspace ONE UEM service that enrolls diverse endpoints, applies compliant profiles and applications, protects corporate data, and provides supportable device operations. The demonstration records application rollout test and assignment evidence so learners can compare design intent with observable behavior.

Hands-On Exercise

Configure and test Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery with representative infrastructure or application data. Use “an application update reaching test devices and production devices at the same time” as the troubleshooting challenge, compare hypotheses, retest the affected path, and complete application rollout test and assignment evidence 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 Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how application rollout test and assignment evidence should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid changing multiple settings at once while troubleshooting Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery. Preserve the failing example, review application rollout test and assignment evidence, and verify whether “an application update reaching test devices and production devices at the same time” is the root cause. After remediation, confirm downstream effects and add a monitoring action.

Validation Checklist

• The scope of Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery is clear, including what is deliberately excluded from the test.
• Evidence in application rollout test and assignment evidence 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 Application catalog, public and internal apps, assignment groups, deployment modes, app configuration, managed access, updates, licensing, and content delivery, explain the decisions made, and defend the result with application rollout test and assignment evidence.