{"id":19270,"date":"2026-09-22T12:34:10","date_gmt":"2026-09-22T12:34:10","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=19270"},"modified":"2026-09-22T12:34:10","modified_gmt":"2026-09-22T12:34:10","slug":"microsoft-mb-820-practice-test-questions-and-exam-dumps-part5-q81-100","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-mb-820-practice-test-questions-and-exam-dumps-part5-q81-100\/","title":{"rendered":"Microsoft MB-820 Practice Test Questions and Exam Dumps Part5 Q81-100"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/mb-820-exam-dumps\"><b>Microsoft MB-820 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 81<\/b><\/h3>\n<p><b>Which AL data type is most appropriate for storing a collection of values that can be accessed by an integer index?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Array<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Record<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enum<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An Array in AL is designed to store multiple values of the same data type and access them using an index. Arrays are useful when the number of elements is known or can be represented by defined dimensions. For example, an array can store several Text values, Decimal values, or other supported data types. A Dictionary instead stores values using keys, while a Record represents data from a table. An Enum represents a predefined set of named values. Choosing the correct collection type helps make AL code clearer and more efficient for the specific data-handling requirement.<\/span><\/p>\n<h3><b>Question 82<\/b><\/h3>\n<p><b>Which AL collection type stores values using unique keys for retrieving the associated values?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Array<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">List<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Record<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Dictionary in AL stores data as key-value pairs. Each key identifies an associated value, making it useful when code needs to retrieve information based on a unique identifier rather than a numeric position. For example, a Dictionary could associate a customer identifier with a calculated value. Unlike an Array, which uses indexes, a Dictionary uses keys to access values. This makes it especially useful for lookup scenarios. Developers should select a Dictionary when the relationship between a key and its corresponding value is more important than sequential positioning of elements.<\/span><\/p>\n<h3><b>Question 83<\/b><\/h3>\n<p><b>Which AL object is designed to import or export structured data using formats such as XML?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Report<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">XMLport<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Page<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An XMLport is an AL object designed specifically for importing and exporting structured data. It can define how records and fields are represented when data is transferred between Business Central and external systems or files. XMLports can work with XML and other supported formats depending on their configuration. A Query is primarily used to retrieve data, while a Report focuses on presenting or processing information. A Page provides a user interface for viewing or editing records. XMLports are therefore appropriate when the requirement involves structured data exchange rather than interactive user access.<\/span><\/p>\n<h3><b>Question 84<\/b><\/h3>\n<p><b>Which property of a codeunit allows the same instance of the codeunit to be reused within a session?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Subtype<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SingleInstance<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Access<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scope<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The SingleInstance property on a codeunit determines whether one instance of that codeunit is maintained for the lifetime of a session. When a codeunit is marked as SingleInstance, its global variables and state can remain available between calls within the same session. This can be useful for maintaining session-level state or caching information when appropriate. However, developers should use SingleInstance carefully because persistent state can make code more difficult to understand and test. Normal codeunits are instantiated as needed, so their state is not maintained in the same way across separate calls.<\/span><\/p>\n<h3><b>Question 85<\/b><\/h3>\n<p><b>What is the primary purpose of an interface in AL?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create a database table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define a contract that implementations must provide<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create a page layout<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define a report dataset<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An interface in AL defines a contract containing methods that implementing objects must provide. It allows code to depend on an abstraction instead of being tightly coupled to one specific implementation. This design can improve flexibility, maintainability, and testability. Different codeunits can implement the same interface while providing different behavior. The calling code can work with the interface without needing to know the implementation details. Interfaces are particularly useful when applications need interchangeable business logic, integration components, or test implementations that can be substituted without changing the consuming code.<\/span><\/p>\n<h3><b>Question 86<\/b><\/h3>\n<p><b>Which AL event mechanism is used when one object needs to react to an event published by another object without modifying the publisher?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Event subscriber<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table relation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Field group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Permission set<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An event subscriber allows AL code to respond to an event published by another object. This provides a loosely coupled extension mechanism because the subscriber can add or modify behavior without changing the original publisher&#8217;s source code. For example, an extension can subscribe to a table event and execute additional validation or processing when that event occurs. This pattern is central to extensibility in Business Central. The publisher defines when an event occurs, while subscribers contain the additional logic that should execute in response to that event.<\/span><\/p>\n<h3><b>Question 87<\/b><\/h3>\n<p><b>Which event type is commonly intended to allow extensions to add custom business logic at defined points in application processing?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database trigger<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Integration event<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Business event<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Page field<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Integration events are commonly used to expose extensibility points where other AL code can subscribe and add custom behavior. They are generally designed for communication between application components and extensions without requiring direct modification of the publishing code. A publisher raises the event at an appropriate point, and one or more subscribers can react to it. This supports loose coupling and makes applications easier to extend. Business events can also communicate business occurrences, but integration events are commonly used as technical extensibility points within application logic.<\/span><\/p>\n<h3><b>Question 88<\/b><\/h3>\n<p><b>Which AL feature is useful for scheduling recurring background processing in Business Central?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Job Queue<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FactBox<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Field Group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role Center<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Job Queue provides a mechanism for scheduling code to run automatically in the background. Developers can create codeunits that perform specific processing and configure job queue entries to execute them according to a schedule. This is useful for recurring tasks such as data synchronization, calculations, notifications, or integration processing. Because the processing occurs in the background, users do not need to manually start every operation. Proper error handling and monitoring are important when designing job queue processes so that failures can be identified and recurring operations do not silently stop.<\/span><\/p>\n<h3><b>Question 89<\/b><\/h3>\n<p><b>Which AL data type is commonly used when code must work with a value whose exact type is determined at runtime?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Boolean<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Variant<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Integer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Date<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Variant data type can hold values of different data types and is useful when code must handle information whose exact type may vary at runtime. It can be particularly helpful in generic processing scenarios where the same procedure needs to work with different kinds of AL values. However, Variant should be used carefully because it reduces compile-time type specificity and can make code harder to understand. Strongly typed variables are generally preferable when the required data type is known. Variant is most useful when flexibility is genuinely required by the design.<\/span><\/p>\n<h3><b>Question 90<\/b><\/h3>\n<p><b>Which AL type is used to represent a JSON object containing property names and their associated values?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JsonArray<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JsonToken<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JsonObject<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JsonValue<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">JsonObject represents a JSON object in AL and contains named properties with associated JSON values. It is commonly used when Business Central communicates with external systems through JSON-based APIs or web services. Developers can add properties, retrieve values, and manipulate JSON structures through the appropriate methods. JsonArray is used for ordered collections of JSON elements, while JsonToken is a general representation of a JSON element. JsonValue represents an individual JSON value. Selecting the correct JSON type is important when constructing, reading, or processing data exchanged with external applications.<\/span><\/p>\n<h3><b>Question 91<\/b><\/h3>\n<p><b>Which AL object is most appropriate for defining a reusable data retrieval structure that can combine fields from multiple related tables?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Page<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Codeunit<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enum<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Query object is designed to retrieve structured data from one or more tables. It can define data items, columns, filters, and relationships between related tables. Queries are useful when applications need efficient data retrieval without creating a complete user interface. They can also support scenarios involving APIs, reporting, and integration. A Page focuses on user interaction, while a Codeunit contains executable business logic. An Enum defines a fixed set of named values. Using a Query for data retrieval helps separate data-access requirements from user-interface and business-processing responsibilities.<\/span><\/p>\n<h3><b>Question 92<\/b><\/h3>\n<p><b>Which AL method can be used to obtain a field reference from a RecordRef?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Get<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Field<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Find<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Validate<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Field method of RecordRef can be used to obtain a FieldRef representing a particular field. RecordRef and FieldRef are useful when developing generic logic that must work with records or fields without knowing their exact table structure at compile time. After obtaining a FieldRef, code can inspect or manipulate information about the corresponding field according to the supported operations. This is especially useful for generic frameworks, metadata-driven processing, and reusable routines. Developers should still use strongly typed records when the table structure is known because they generally provide clearer and safer code.<\/span><\/p>\n<h3><b>Question 93<\/b><\/h3>\n<p><b>What is the main purpose of a FieldRef in AL?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To represent a dynamic reference to a table field<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create a new page<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To schedule a task<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define an interface<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">FieldRef provides a dynamic reference to a field and is commonly used together with RecordRef. It allows AL code to work with fields dynamically when the exact table or field may not be known at compile time. This is useful for generic routines that inspect metadata or process different tables using a common mechanism. FieldRef can expose information about a field and support certain operations on it. Although powerful, dynamic references can make code less explicit than strongly typed field access, so they should be used when generic behavior is actually required.<\/span><\/p>\n<h3><b>Question 94<\/b><\/h3>\n<p><b>Which method is used to assign a value to a record field while also executing the field&#8217;s validation logic?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Modify<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Assign<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Validate<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SetRange<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Validate method assigns a value to a field while invoking the field&#8217;s validation trigger. This is important when the table field contains business rules that must execute whenever the value changes. Direct assignment may not provide the same validation behavior. Using Validate helps ensure that related calculations, checks, and business rules are applied consistently. For example, when changing a customer-related field, validation may update dependent information or enforce business requirements. Developers should understand when validation is required rather than relying only on direct assignment when working with business-critical fields.<\/span><\/p>\n<h3><b>Question 95<\/b><\/h3>\n<p><b>Which AL object can be used to define additional fields or functionality for an existing table without modifying the base table object?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TableExtension<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">XmlPort<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Codeunit<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A TableExtension allows an extension to add fields, keys, triggers, and other supported functionality to an existing table. This is one of the fundamental extensibility mechanisms in Business Central because developers can customize application data structures without directly changing the original Microsoft object. Table extensions help preserve upgradeability and reduce conflicts with the base application. When designing an extension, developers should carefully consider field names, relationships, keys, and dependencies. A TableExtension is therefore preferred when the requirement involves extending an existing table rather than creating a completely independent table.<\/span><\/p>\n<h3><b>Question 96<\/b><\/h3>\n<p><b>Which property controls whether an AL field or object is available to external applications through supported service exposure scenarios?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Caption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Editable<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Access<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ObsoleteState<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Access property controls the accessibility level of certain AL objects and members. It is used to determine whether functionality is available within an application or can be accessed from outside the defining scope, depending on the object and member involved. Proper access control helps developers maintain encapsulation and avoid exposing implementation details unnecessarily. Properties such as Caption affect display text, Editable controls whether users can modify certain UI elements, and ObsoleteState manages the lifecycle of deprecated elements. Access should therefore be considered when designing reusable and secure extension architecture.<\/span><\/p>\n<h3><b>Question 97<\/b><\/h3>\n<p><b>Which AL feature is specifically intended to provide information about an error and allow more structured error handling?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ErrorInfo<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Label<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enum<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FieldGroup<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">ErrorInfo provides a structured way to represent error information in AL. It can contain details that help the application present more meaningful error messages and support richer error-handling scenarios. Structured error information is useful when applications need to distinguish between different failure conditions or provide users with actionable information. Traditional ERROR handling remains important, but ErrorInfo allows developers to communicate error context in a more organized manner. Good error handling should identify meaningful causes, avoid exposing sensitive technical information, and provide enough context for users or support teams to understand what went wrong.<\/span><\/p>\n<h3><b>Question 98<\/b><\/h3>\n<p><b>Which AL mechanism is intended to allow code to attempt an operation and handle an error without immediately terminating the surrounding process?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TryFunction<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FlowField<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FieldGroup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TableRelation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A TryFunction is used for scenarios where AL code needs to attempt an operation that may fail and then handle the failure through controlled logic. Instead of allowing an error to immediately terminate the normal execution path, the try mechanism allows the caller to determine whether the operation succeeded. This can be useful for validation, optional processing, and integrations where failure needs to be handled gracefully. Developers must understand the transaction and database implications of TryFunctions and should not use them simply to hide errors. Meaningful failures should still be handled and communicated appropriately.<\/span><\/p>\n<h3><b>Question 99<\/b><\/h3>\n<p><b>Which feature is used to display additional contextual information alongside a Business Central page?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role Center<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FactBox<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">XMLport<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A FactBox displays additional contextual information alongside the main content of a Business Central page. It can provide related details without requiring the user to leave the current page. For example, a card page may display related statistics, contacts, or other information in a FactBox area. This improves usability by keeping relevant information accessible while the user works with the primary record. Role Centers provide broader navigation and activity-focused experiences, while XMLports and Queries serve data-processing and retrieval purposes rather than providing contextual page information.<\/span><\/p>\n<h3><b>Question 100<\/b><\/h3>\n<p><b>Which AL technique is most appropriate for storing sensitive credentials used by an extension to communicate with an external service?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hard-code the credentials in a codeunit<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Store credentials in a public table field<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use a secure credential or secret-management mechanism<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Put the credentials directly in a page caption<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Sensitive credentials should be handled through secure credential or secret-management mechanisms rather than being hard-coded or exposed through application data or user-interface objects. Storing secrets directly in source code creates security risks because source code may be accessible to developers, repositories, or deployment systems. Public table fields and page captions are also inappropriate for confidential information. A secure design separates secrets from application logic and limits access to authorized processes. Developers should also consider environment-specific configuration, access permissions, and secure rotation of credentials when implementing integrations with external services.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft MB-820 Exam Dumps and Practice Test Dumps. &nbsp; Question 81 Which AL data type is most appropriate for storing a collection of values that can be accessed by an integer index? Dictionary Array Record Enum Correct Answer: 2 Explanation An Array in AL is designed to store multiple values of the same [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/19270"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=19270"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/19270\/revisions"}],"predecessor-version":[{"id":19271,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/19270\/revisions\/19271"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=19270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=19270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=19270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}