A company plans to optimize its permission sets.
The company has the following permission sets:

You need to provide the following implementation for a third permission set:
* Create a new Permission Set C that is a composite of Permission Set A and Permission Set B.
* Assign Permission Set C to a user.
You need to ensure that the user has only read access to the Job table.
Solution: Set the IncludedPermissionSets property to Permission Set A.
Does the solution meet the goal?
Answer : B
You create a Business Central report.
You need to insert values on the Request page to be saved for the next time the report is run.
What should you do?
Answer : D
You develop an extension for the newest release of Business Central online.
You have a customer who has an earlier on-premises release of Business Central. The extension must be deployed to the customer's environment.
You need to deploy the extension to the older Business Central version,
What should you do?
Answer : C
You need to determine why the debugger does not start correctly.
What is the cause of the problem?
Answer : A
In Microsoft Dynamics 365 Business Central, when configuring snapshot debugging, it is crucial that the parameters in the configuration file are correctly set. From the options provided, the issue with the debugger not starting correctly is most likely due to an incorrect 'userId' parameter.
Option A is the cause of the problem. The 'userId' parameter must be the GUID of the user, not the username. The snapshot debugger needs the exact GUID to attach to the right session for debugging.
Option B is incorrect because 'breakOnNext' set to 'WebClient' is a valid setting. This tells the debugger to break on the next client action in the web client, which is a typical scenario.
Option C is not the cause of the problem. The 'userId' parameter is meant to specify which user session to debug, and this works in conjunction with the 'breakOnNext' parameter.
Option D is incorrect as the 'executionContext' parameter does not need to be set to 'Debug' for snapshot debugging to work. 'DebugAndProfile' is a valid value for the 'executionContext' parameter, as it allows for debugging and collecting performance information.
Therefore, the reason why the debugger does not start correctly is due to Option A: The 'userId' parameter must have the GUID of the user specified, not the username.
You need to create the access modifier for IssueTotal.
Which variable declaration should you use?
Answer : B
In Business Central development using AL (the language for Business Central extensions), the use of access modifiers defines how variables and procedures are accessed within and outside of an object or codeunit.
Access Modifiers in AL:
Public: A public variable can be accessed from any object or codeunit within the same module or extension.
Protected: This restricts access to the current object and objects that inherit from the current object. However, in AL (at least in versions used for Business Central), the Protected access modifier is used with methods but not variables.
Internal: This modifier restricts the visibility to the current extension. This means that variables or methods declared as internal can only be accessed from within the same extension. This is appropriate when you want to provide functionality that is shared within the extension but not exposed externally.
Local: This restricts the variable or method to the current object or method where it is declared. It cannot be accessed from anywhere else, even within the same extension.
Scenario Justification:
In the scenario for Contoso, Ltd., IssueTotal is a global variable in the ISSUE BASE extension, and the ISSUE EXT extension needs to access it. Therefore, the variable cannot be declared as Local, because this would restrict access to just the current object (or method).
Using Public would expose the variable outside of the extension, which is unnecessary because you only want other parts of the extension (specifically the ISSUE EXT extension) to have access.
The best choice in this case is Internal because it restricts access to the variable to within the same extension, which includes the base extension and any dependent extensions like ISSUE EXT. It strikes the right balance between visibility and encapsulation.
Microsoft Dynamics 365 Business Central Developer Reference:
Access Modifiers in AL: Microsoft's documentation on AL provides the details on access modifiers, where it is specified that internal variables can be accessed within the extension, and the public variable is accessible across all extensionssource: Microsoft Learn on AL Programming.
Best Practices for AL Development: Business Central development best practices suggest keeping variables internal unless they need to be accessed outside of the current extensionsource: Microsoft Learn on AL development guidelines.
You have a query object named Items Query. You write code using an Items Query query variable. You need to export the Items Query query data to a file. Which SaveAs function should you use?
Answer : D
SaveAsCsv is the correct function to export the query data to a CSV (Comma-Separated Values) file, which is a commonly used text format for data exports.
SaveAsExcel would export to an Excel file, SaveAsWord to a Word document, and SaveAsHtml to an HTML file, but since the requirement is to export to a file and the question doesn't specify any particular file format other than what fits standard data exports, CSV is the most fitting and efficient format for this scenario.
For more information, see the Query Object Functions in Business Central.
You need to call the Issue API action from the mobile application.
Which action should you use?
Answer : A