|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/salesforce-mulesoft-platform-architect-i-exam-questions/
课程评论:没有评论
课程名称:Salesforce MuleSoft 平台架构师 I 考试问题 课程概述: Salesforce 认证的 MuleSoft 平台架构师 I 证书旨在帮助有经验的专业人士定义和管理组织的 Anypoint 平台战略。持有该认证的人员能够监督从单个集成解决方案发展出强大的应用程序网络,利用 API 引导的连接性贯穿整个组织。课程旨在帮助参与者深入了解如何在特定的组织环境中优化和配置 Anypoint 平台的部署,并具备与业务、基础设施、信息安全等团队协作的能力。 目标受众: 本课程的目标受众为拥有 Salesforce 认证的 MuleSoft 平台架构师的候选人,他们应具备以下知识和经验: - 优化和配置 Anypoint 平台的部署。 - 指定 Anypoint 平台与组织内其他工具和应用的集成方式。 - 定义 Anypoint 平台的使用及维持平台可持续性所需的组织和流程变更。 候选人可能的典型工作角色包括企业架构师和解决方案架构师。 考试概述: Salesforce 认证的 MuleSoft 平台架构师 I 考试包含 60 道多选题和最多 5 道非评分题,考试时间为 120 分钟,及格分数为 70%。考试注册费用为 400 美元,重考费用为 200 美元。考试过程中不允许参考任何物理或在线材料。 考试大纲: 考试内容包括以下几个方面: 1. 应用网络基础:理解 API 引导连接的技术和 web API 的角色。 2. 组织和平台基础:建立支持 Anypoint 平台的能力中心,识别关键绩效指标。 3. 设计和共享 API:识别 API 的依赖关系和创建可重用 API 相关资产。 4. 使用系统、进程和体验层设计 API:识别适合实施业务过程的 API。 5. 管理 Anypoint 平台上的 web API:选择合适的 API 策略以支持特定的非功能需求。 6. 架构和部署 API 实现:使用自动发现连接 web API 实现与 API 实例。 7. 部署到 CloudHub:描述 CloudHub 共享工作云的可靠性和性能特征。 8. 达成 API 质量目标:设计恢复策略以帮助 web API 客户端抵御失败。 9. 监控和分析应用程序网络:识别生成监控和警报数据的组件。 本课程为希望深入理解 Anypoint 平台并追求 Salesforce 认证的 MuleSoft 平台架构师提供了系统性的培训和复习材料。
About the Salesforce Certified MuleSoft Platform Architect I CredentialThe Salesforce Certified MuleSoft Platform Architect I credential is intended for professionals who have experience in defining and managing an organization's Anypoint Platform strategy.Holders of the Salesforce Certified MuleSoft Platform Architect I credential can oversee the development of a robust application network from individual integration solutions, utilizing application programming interface (API)-led connectivity throughout an organization with the Anypoint Platform.Audience Description: Salesforce Certified MuleSoft Platform Architect ICandidates for the Salesforce Certified MuleSoft Platform Architect I possess the knowledge, abilities, and experience to:Optimize and configure the Anypoint Platform deployment within the specific organizational environment, collaborating with business, infrastructure, InfoSec, and other teams.Specify how the Anypoint Platform integrates with other tools and applications within the organization.Define the use of the Anypoint Platform and the related organizational and process changes necessary to maintain the platform's sustainability.Offer guidance and lead the development of standards, reusable assets, and automation needed for scaling and adopting multiple lines of business (LoB).Typical job roles for candidates may include:Enterprise ArchitectsSolution ArchitectsThese roles generally involve experience with common integration methodologies (such as SOA) and integration technologies/platforms, along with foundational knowledge and experience with the components of the Anypoint Platform.About the ExamBelow are details about the Salesforce Certified MuleSoft Platform Architect I Exam:Content: 60 multiple-choice questions and up to five non-scored questionsTime Allotted: 120 minutes (includes time for non-scored questions)Passing Score: 70%Registration Fee: US$400, plus applicable taxes as required by local lawRetake Fee: $200, plus applicable taxes as required by local lawReferences: No physical or online materials may be referenced during the exam.Prerequisite: NoneExam OutlineThe Salesforce Certified MuleSoft Platform Architect I Exam measures a candidate's knowledge and skills related to the following objectives. Candidates should have experience in defining and being responsible for an organization's Anypoint Platform strategy. Candidates should also have the knowledge and skills to direct the emergence of an effective application network from individual integration solutions, following application programming interface (API)-led connectivity across an organization using Anypoint Platform.Explaining application network basics: 7%Identify and differentiate between technologies typically used to implement API-led connectivity.Describe the role and characteristics of web APIs.Correctly assign APIs to tiers according to ownership, functional focus, and rate of change.Describe the capabilities and high-level components of Anypoint Platform.Establishing organizational and platform foundations: 10%Advise on establishing a Center for Enablement (C4E) and identify key performance indicators (KPIs) to measure its success.Describe the high-level structure and benefits of MuleSoft Catalyst.Choose between options for hosting and managing Anypoint Platform control and runtime planes.Compare and contrast Identity Management and Client Management options on Anypoint Platform.Identify data residency of different kinds of data (payload, metrics, and others).Designing and sharing APIs: 10%Identify dependencies between an API, its API specification, its implementation, and its clients.Describe the creation and publication of reusable API-related assets using API specifications and Anypoint Platform components.Identify changes to an API that would require or not require changing the major/minor/patch component of its semantic version.Given a specific power relationship between two Bounded Contexts, choose the most appropriate strategy for mapping between the API data models of these Bounded Contexts.Identify idempotent HTTP methods and HTTP-native support for optimistic concurrency.Designing APIs using System, Process, and Experience Layers: 12%Identify appropriate APIs to implement a business process and assign them to layers of API-led connectivity.Assign APIs to layers according to ownership, functional focus, and rate of change.Recommend the most appropriate approach relating the API data model of System APIs to that of their backend system based on specific requirements and organizational characteristics.Recommend the use of an Enterprise Data Model or Bounded Context Data Models based on a set of APIs and specific preferences and organizational characteristics.Select DataGraph only for suitable roles in an application network, according to its high-level features.Governing web APIs on Anypoint Platform: 17%Make appropriate use of API instances and environments in API Manager, taking into account the nature of the API and the underlying data and system.Select appropriate API policies and other components of the API to support specific non-functional requirements (NFRs).Identify any change(s) required to an API specification to reflect the application of an API policy with specific characteristics.Select an approach to API policy enforcement based on specific preferences and constraints, including, but not limited to, API proxies/API gateways and Anypoint Service Mesh.Secure web APIs using API policies appropriately chosen for the API's tier (System, Process, Experience).Describe in what circumstances and how to pass client ID and secret to a web API.Explain how to request access to an API version for an API client, and how that access is approved and revoked.Select appropriate API policies to enforce non-functional security constraints on web API invocations.Explain the relationships of Anypoint Platform, external Identity Providers (IdPs), AP Business Groups, and API clients in the context of OAuth 2.0.Identify scenarios needing custom API policies.Architecting and deploying API implementations: 11%Explain how to use auto-discovery to link a web API implementation to an API instance managed with API Manager.Identify requirements that call for the use of an Anypoint Virtual Private Cloud (VPC).Compare and contrast options for hosting and managing Anypoint Platform runtime planes.Compare unit and integration tests and specify where MUnit is best employed.Explain options for automated building, testing, and deployment of API implementations and related artifacts in a DevOps setting.Deploying API implementations to CloudHub: 11%Describe the scenarios for which Object Store (OS) should be used with CloudHub.Select CloudHub worker sizes and configuration as appropriate.Given an app deployed to the CloudHub shared worker cloud in one or more regions, describe and predict its reliability and performance characteristics.Identify the defining differences between the CloudHub Shared and Dedicated Load Balancers.Compare and contrast the options for CloudHub networking in the presence of customer-owned Amazon VPCs and on-premises data centers.Identify and avoid single points of failure in CloudHub deployments of API implementations.Meeting API quality goals: 10%Design, describe, and differentiate between scenarios that use an OS or caching.Select resilience strategies that help web API clients guard against failures when invoking APIs.Describe when horizontal scaling of an API implementation is or is not likely to benefit response time and throughput as seen by API clients.Monitoring and analyzing application networks: 12%Identify the components of Anypoint Platform that generate data for monitoring and alerting.Describe the metrics collected by Anypoint Platform for API invocations.Specify alerts to define for key metrics of API invocations for all layers of API-led connectivity.Specify alerts to define for Mule applications.