Explanation:
Box 1: synchronous
A synchronous pattern is a blocking request and response pattern, where the caller is blocked until the callee has finished running and gives a response.
Box 2: Asynchronous
An asynchronous pattern is a non-blocking pattern, where the caller submits the request and then continues without waiting for a response.
Box 3: synchronous
Box 4: Asynchronous
A typical Batch job.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/integration-overview

Topic 2, World Wide Importers
Current environment
Requirements
Customers may place orders by email, phone, or by using the company's website. The company authorizes and processes credit card transactions by using a web-based application. Customer, inventory, supplier, and other master and transactional data is stored in a legacy database.
The company collects feedback from customers by phone or a form on the company's website and maintains the data in a Microsoft Excel workbook.
Wide World Importers runs on-premises applications to manage payroll and workers compensation. The company has a set of Microsoft Power Bl dashboards that present data from a reporting database.
The company creates a Lifecycle Services (LCS) implementation project and completes Dynamics 365 Finance onboarding.
The company maintains production, quality assurance (QA). development, user acceptance testing (UAT), and build environments.
General
* You must configure a cloud-based Dynamics 365 Finance development environment and enable code extensions that support updates.
* You must configure version control and a Build environment.
* You must migrate all legacy data to the new system.
* You must implement best practices for X++ coding, the data model, caching, and security.
* All new code must be unit tested in a development environment and then validated by the QA team before code is added to source control.
Business processes
* You must configure vendor trade agreements.
* Products must be shipped directly from suppliers to customers depending on customer location to save indirect costs.
* You must collect customer feedback on products shipped directly from vendors.
* You must deploy code to a UAT environment for testing before deploying code to production.
* You must validate all entries for the purchase order creation form.
* You must develop a web portal that allows customers to browse products, place orders, and check order status. Product data for the web portal must be integrated as periodic batches.
Business systems
* You must install and configure a third-party solution for credit card processing within Dynamics 365 Finance. The third-party company will provide a deployable package.
* The workers compensation application must be able to call an API to update worker compensation details in Dynamics 365 Finance.
* You must develop a process to import payroll journals into the system.
* You must configure the warehouse mobile device portal for warehouse operations.
* You must install a third-party solution to support web portal integration. The solution is supplied as a source code model file.
You must develop a new solution to maintain a Vendor exclusion list for each customer and item combination. The solution must meet the following requirements:
* Isolate all new vendor exclusion codes as a new assembly by creating a table named Vend Exclusions.
* Create an index for the table named Primaryldx that uses the following fields: CustAccount, Itemld, VendAccount.
* Ensure that users can open the Vendor Exclusion list report from the customer master form. The list must display the customer account Item ID, and Vendor account fields.
* Implement the Excel integration for the Vendor Exclusion List form.
* Provide functionality to periodically export the Vendor exclusion list to prepare reports by using standard reporting capabilities of Dynamics 365 Unified Operations.
* Develop necessary security permissions to view and maintain the new Vendor exclusion list functionality and reporting. Users with maintain rights will be able create, update, and delete the exclusion list. Permissions must be assigned to security roles to match company security model.
* Maintain referential integrity with other tables.
* Users must be presented with a warning message before a direct delivery purchase order is created for a vendor in exclusion list.
* Sales managers must be alerted when a new exclusion record is added to the system.
Security
* You must implement the record level audit feature to identify the users who created the record.
* Grant specific users rights to maintain the vendor exclusion list by using Excel.
* You must implement validation to check whether a proposed direct delivery purchase order vendor is on the exclusion list for the customer and product combination.
Issues
User1 is not able to access many features in the system. You must provide User1 administrator rights.
A sales manager suspects a data-related issue in the vendor exclusion list. User1 must identify the user who created the referenced exclusion records.
Developed joins the company and does not have access to a development environment or source control.
User2 reports performance issues when they generate direct delivery purchase orders after current updates are applied.
User2 reports that they cannot access new functionality and reports.

Explanation
Explanation:
One use of the SysObsoleteAttribute class is to notify the compiler that the compile should fail if a particular method is called in the source code. The compiler rejects the compile, and displays the specific message that is stored in this use of the attribute.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-ref/xpp-attribute-classes

Optimistic Concurrency only locks records from the time when the actual update is performed.
Following are the advantages of using OCC:
Records remain available for other processes to update if they have been selected from the database but haven't yet been updated.
Records are locked for a shorter length of time.
Fewer resources are used to hold the locks during the update process.
Incorrect Answers:
A: Pessimistic Concurrency Control locks records as soon as they are fetched from the database for an update.
E: One record can be selected for update by two different processes at the same time when using OCC.
Reference:
https://docs.microsoft.com/en-us/dynamicsax-2012/developer/optimistic-concurrency-control