|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/exam-pl-600-microsoft-power-platform-solution-architect-r/
课程评论:没有评论
**课程名称:** Exam PL-600: Microsoft Power Platform 解决方案构架师 **课程概述:** 本课程旨在帮助学员成为 Microsoft Certified: Power Platform 解决方案构架师专家。课程内容涵盖了 Power Platform 解决方案构架师所需的各项关键技能,包括但不限于: * **执行解决方案的构想和需求分析 (35-40%)** * **启动解决方案规划:** 评估业务需求,识别 Power Platform 解决方案组件及其他相关组件(如现有应用、AppSource 应用、第三方组件、ISV 组件),并预估迁移工作量。 * **识别组织信息和指标:** 了解组织的高层业务流程,识别业务流程自动化机会,评估风险因素,并明确关键成功标准。 * **识别现有解决方案和系统:** 评估组织的企业架构,识别解决方案所需的数据源,定义数据用例和质量标准,并识别和记录组织业务流程。 * **捕获需求:** 提炼高层需求,识别功能性与非功能性需求,并确保需求符合组织目标。 * **执行适配/差距分析 (Fit/Gap Analyses):** 评估满足特定需求的可行性,考察 Dynamics 365 应用和 AppSource 选项,通过替代方案解决功能差距,并确定解决方案范围。 * **构架解决方案 (40-45%)** * **领导设计过程:** 设计解决方案拓扑,定制现有应用,设计并验证用户体验原型,识别组件重用机会,可视化沟通系统设计,设计应用生命周期管理 (ALM) 流程,设计数据迁移策略,按角色或任务组织功能设计应用,设计数据可视化策略,以及设计使用 Power Automate 的自动化策略。 * **设计数据模型:** 设计表和列,设计参考和配置数据,设计关系和关系行为,确定连接外部数据还是导入数据,并设计数据模型以满足复杂的需求。 * **设计集成:** 设计协作集成,设计 Microsoft Power Platform 解决方案与 Dynamics 365 应用之间的集成,设计与组织现有系统的集成,设计第三方集成,设计身份验证策略,设计业务连续性策略,并识别集成和扩展 Power Platform 解决方案的机会(利用 Microsoft Azure)。 * **设计安全模型:** 设计业务部门和团队结构,设计安全角色,设计列安全,设计满足复杂需求的安全模型,确定安全模型管理策略和流程,识别支持解决方案所需的 Azure Active Directory 组和应用程序注册,识别解决方案的数据丢失防护 (DLP) 策略,并确定外部用户如何访问解决方案。 * **实施解决方案 (15-20%)** * **验证解决方案设计:** 评估详细设计和实施,验证安全性,确保解决方案符合 API 限制,解决自动化冲突,以及解决集成冲突。 * **支持上线 (Go-live):** 识别和解决潜在和实际的性能问题,进行数据迁移故障排除,解决部署计划中发现的任何问题,并识别影响上线就绪性的因素并进行补救。 **课程大纲:** 无
Microsoft Certified: Power Platform Solution Architect Expert - Skills MeasuredNOTE: The bullets that appear below each of the skills measured are intended to illustrate how we are assessing that skill. This list is NOT definitive or exhaustive.NOTE: Most questions cover features that are General Availability (GA). The exam may contain questions on Preview features if those features are commonly used.Exam PL-600: Microsoft Power Platform Solution ArchitectPerform solution envisioning and requirement analyses (35-40%)Initiate solution planning evaluate business requirements identify Microsoft Power Platform solution components identify other components including existing apps, AppSource apps, third-party components, and components from independent software vendors (ISV) identify and estimate migration effortIdentify organization information and metrics identify desired high-level organizational business processes identify business process automation opportunities assess an organization's risk factors review key success criteriaIdentify existing solutions and systems evaluate an organization's enterprise architecture identify data sources needed for a solution define use cases and quality standards for existing data identify and document an organization's business processesCapture requirements refine high-level requirements identify functional requirements identify non-functional requirements confirm that requirements meet an organization's goalsPerform fit/gap analyses determine the feasibility of meeting specific requirements evaluate Dynamics 365 apps and AppSource options to solve requirements address functional gaps through alternate solutions determine the scope for a solution Architect a solution (40-45%)Lead the design process design the solution topology design customizations for existing apps design and validate user experience prototypes identify opportunities for component reuse communicate system design visually design application lifecycle management (ALM) processes design a data migration strategy design apps by grouping required features based on role or task design a data visualization strategy design an automation strategy that uses Power AutomateDesign the data model design tables and columns design reference and configuration data design relationships and relationship behaviors determine when to connect to external data versus import data design data models to address complex sets of requirementsDesign integrations design collaboration integrations design integrations between Microsoft Power Platform solutions and Dynamics 365 apps design integrations with an organization's existing systems design third-party integrations design an authentication strategy design a business continuity strategy identify opportunities to integrate and extend Microsoft Power Platform solutions by using Microsoft AzureDesign the security model design the business unit and team structure design security roles design column security design security models to address complex sets of requirements determine security model management policies and processes identify Azure Active Directory groups and app registrations required to support a solution identify data loss prevention (DLP) policies for a solution determine how external users will access a solutionImplement the solution (15-20%)Validate the solution design evaluate detail designs and implementation validate security ensure that the solution conforms to API limits resolve automation conflicts resolve integration conflictsSupport go-live identify and resolve potential and actual performance issues troubleshoot data migration resolve any identified issues with deployment plans identify factors that impact go-live readiness and remediate issues