1. Home
  2. Salesforce
  3. Plat-Arch-202 Exam Syllabus

Salesforce Plat-Arch-202 Exam Syllabus

Start Free Plat-Arch-202 Exam Practice After Reviewing the Topics

Before starting your Plat-Arch-202 exam preparation, it is recommended to review the complete Salesforce Certified Platform Development Lifecycle and Deployment Architect exam syllabus and carefully go through the exam objectives listed below. Once you understand the exam structure and objectives, you should practice using our free Plat-Arch-202 questions. We also provide premium Plat-Arch-202 practice test, fully updated according to the latest exam objectives, to help you accurately assess your preparedness for the actual exam.

Vendor
Plat-Arch-202
Exam Code
118
Total Questions
8
Total Exam Domains

START FREE Plat-Arch-202 EXAM PRACTICE

NO SIGNUP REQUIRED  •  100% FREE TO START

Plat-Arch-202 EXAM QUESTIONS

Salesforce Plat-Arch-202 Exam Objectives

Section 1: Application Lifecycle Management
Weight:
8%
  • Given the project risk and customer requirements, explain how to assess the benefits and risks of the different development methodologies and recommend the appropriate governance strategies based on the customer maturity.
Section 2: Planning
Weight:
13%
  • Given a complex customer scenario, assess ALM maturity and identify the people, technology, and processes required.
  • Understand customer environment risks and articulate appropriate mitigation strategies.
  • Given a customer scenario, analyze and recommend the appropriate governance framework.
  • Given a customer scenario involving a new Salesforce release (Summer, Winter, Spring), recommend the appropriate strategy to mitigate risks.
Section 3: System Design
Weight:
15%
  • Explain the advantages of using agile tools to support an agile development process.
  • Given a customer landscape and their requirements, evaluate business, technical, and architectural considerations which support the defined org strategy.
  • Given a customer scenario, define an environment (sandbox) strategy that utilizes the correct sandbox types (for example, multiple project streams, training requirements, staging, production, and hotfixes).
  • Given a scenario, compare, contrast and recommend the components and tools of a successful deployment strategy.
Section 4: Building
Weight:
14%
  • Given a customer scenario, explain how source control branching/versioning/merging can be used and recommend appropriate strategies.
  • Describe the appropriate approaches to building test data strategy and unit test to ensure successful code (positive, negative, permission-based, large data volume).
  • Given a customer scenario, describe the appropriate development model (org-based vs package-based) and development environment (scratch org vs sandboxes).
  • Describe the methods to ensure the delivery of quality code, such as coding standards, pull requests, code review and static code analysis.
Section 5: Deploying
Weight:
14%
  • Given a scenario, describe the capabilities, limitations and considerations when using the Metadata and Tooling APIs for deployment.
  • Given a scenario, describe approaches to handle pre and post deployment steps, including items not supported via the APIs.
  • Given a scenario, describe and recommend an approach to manage and deploy technical reference data - configuration stored as object data.
Section 6: Testing
Weight:
13%
  • Given a customer scenario, describe and recommend an appropriate testing methodology. 
  • Given a customer testing strategy, describe the appropriate test execution methodology and coverage requirements.
  • Given a customer scenario, describe and recommend a unified test data strategy that utilizes representative data in a secure manner throughout the development lifecycle.
Section 7: Releasing
Weight:
13%
  • Given a scenario, analyze and explain the use cases and considerations when using managed and unmanaged as well as unlocked packages.
  • Apply map sandbox strategy to a specific Release Plan, taking into consideration multiple project streams, training requirements, staging and hotfixes.
  • Given a customer scenario, describe and recommend an appropriate release management strategy.
Section 8: Operating
Weight:
10%
  • Given a detailed customer environment scenario including a specific request, explain the implications for incorporating the request directly in a production environment.
  • Given a customer scenario where changes are made directly in production, explain the implications on the development lifecycle and steps to integrate changes into application lifecycle management.
  • Given a multi-org customer scenario, compare and contrast approaches for managing common release artifacts.
Info