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.
A company is deploying Business Central on-premises.
The company plans to use a single-tenant deployment architecture.
You need to describe how the data is stored and how the Business Central Server is configured.
In which two ways should you describe the single-tenant architecture? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Answer : A, B
In a single-tenant deployment architecture of Business Central on-premises, the following characteristics describe how the data is stored and how the Business Central Server is configured:
The application and the business data are stored in the same database (B): In a single-tenant architecture, each tenant (which typically corresponds to a single customer) has its own dedicated database. This database contains both the application objects (such as pages, reports, codeunits, etc.) and the business data (such as customer, vendor, and transaction records). This setup ensures that each tenant's data is isolated and can be managed independently.
The application and business data are stored in separate databases (D): While (B) is a characteristic of a single-tenant deployment, it's important to clarify that in some configurations, the application objects can be stored in a separate database from the business data. This approach can be used for easier maintenance and upgrades of the application code without affecting the business data. However, each tenant still has its own set of databases, maintaining the single-tenancy model.
The other options provided do not accurately describe a single-tenant architecture:
Each customer has their own Business Central Server (A): This statement might be misleading. In a single-tenant deployment, while each customer has their own database, they do not necessarily have their own Business Central Server instance. Multiple databases (tenants) can be hosted on a single server instance, although they are not shared across customers.
Multiple customers share a single Business Central Server (C) and Multiple customers share multiple Business Central Server instances (E): These options describe a multi-tenant architecture rather than a single-tenant one. In a multi-tenant setup, multiple customers (tenants) can share the same server instance and even the same application database, with data isolation ensured at the application level.
You need to determine If you have unwanted incoming web service calls in your tenant during the last seven days.
Which two KQL queries should you use? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
A.
B.
C.
D.
E.
Answer : A, C
The task is to identify unwanted incoming web service calls during the last seven days. To do this, we need to look at KQL (Kusto Query Language) queries that would filter out web service calls based on the timestamp (to ensure the calls are within the last seven days) and by certain characteristics that would indicate they are unwanted, such as the wrong type of protocol (SOAP in this case, as Contoso Ltd. plans to dismiss using it).
Looking at the options:
Option A: This query selects all traces where the timestamp is within the last 7 days and where the custom dimension has a value of 'RT0008', and where the category is either 'ODataV4', 'ODataV3', or 'Api'. This query would show all API calls except SOAP, so it does not directly answer the question about unwanted calls.
Option B: This query filters for traces with a timestamp within the last 7 days, where 'RT0008' is present, and specifically looks for the category 'SOAP'. This query is correct because it directly targets SOAP calls, which are the unwanted calls according to Contoso Ltd.'s plans.
Option C: Similar to option B, this query filters for traces within the last 7 days and looks for 'RT0008' but uses the equality operator for the category 'SOAP'. This would also correctly return the unwanted SOAP calls.
Option D: This query also filters for traces within the last 7 days, but it excludes the 'ODataV4' category, which doesn't necessarily target the unwanted SOAP calls.
Option E: This query selects traces where the timestamp is within the last 7 days and the custom dimension has 'RT0008'. However, it filters out categories 'ODataV4' and 'Api', which does not directly help in identifying the unwanted SOAP calls.
Therefore, the queries that should be used to determine if there are unwanted incoming web service calls (SOAP calls) in the tenant during the last seven days are Options B and C. These queries are specific to identifying SOAP protocol usage, which is what Contoso Ltd. considers unwanted.
You need to evaluate the version values of the Quality Control extension to decide how the quality department must update it.
Which two values can you obtain in the evaluation? Each correct answer presents part of the solution. Choose two.
NOTE: Each correct selection is worth one point.
Answer : A, C
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 B and the ExcludedPermissionSets property to Permission Set A.
Does the solution meet the goal?
Answer : B
You need to improve performance when ticketAPI is used to analyze the POS data. What should you do?
Answer : C
Read Scale-Out:
Read scale-out is a feature in Business Central that allows you to improve performance by distributing read-only queries (such as the ones from the ticketAPI) across multiple read replicas in the cloud database. This reduces the load on the primary database and helps improve the response time for read-intensive operations, like analyzing POS data through the ticketAPI.
Data Access Intent - ReadOnly:
When enabling read scale-out, you can configure the DataAccessIntent property of APIs to be ReadOnly. This directs the system to use read replicas to handle read-only queries, which enhances performance by offloading such queries from the primary database.
Why Not Other Options?
Option A (ODataReadonlyGetEnabled): This parameter is unrelated to read scale-out and primarily affects OData services behavior, not API performance tuning.
Option B (AccessByPermission): Setting the permission to Read does not directly affect the performance. It only controls access based on user permissions.
Option D (DataAccessIntent ReadOnly): While setting this property to ReadOnly helps in read-only operations, enabling read scale-out (option C) ensures the underlying infrastructure is optimized to handle such read operations, which is the fundamental action required.
Reference Documentation:
Read Scale-Out in Business Central
A company has a test application.
A user observes the following error messages when running the test:
* "Unhandled Ul: Message'
* "Unhandled Ul: Confirm"
You need to resolve the errors. Which action should you take?
Answer : B
A user observes error messages such as:
'Unhandled UI: Message'
'Unhandled UI: Confirm'
These messages indicate that the test code is not handling system prompts like Message and Confirm dialogs, which can appear during test execution.
Options
Message Handler and Confirm Handler methods are used to intercept and handle these UI prompts during automated testing.
These methods should be added to the test runner codeunit, which is responsible for running the tests and handling these system-level interactions.