CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. MB-820

Free MB-820 Exam Braindumps (page: 5)

Page 5 of 15
PDF with 56 Questions

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.

  1. Each customer has their own Business Central Server.
  2. The application and the business data are stored in the same database.
  3. Multiple customers share a single Business Central Server.
  4. The application and business data are stored in separate databases.
  5. Multiple customers share multiple Business Central Server instances.

Answer(s): B,D

Explanation:

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.



DRAG DROP (Drag and Drop is not supported)
A company plans to deploy Business Central.
The company has the following deployment requirements:
- Use the company hardware architecture to run the deployment.
- Use sandbox environments to develop extensions.
- Allow tenants to connect to Shopify with the standard connector.
- Use Microsoft Power Automate to create a workflow that calls a business event. You need to identify the deployment type for each requirement.
Which deployment types should you use? To answer, move the appropriate deployment types to the correct requirements. You may use each deployment type once, more than once, or not at all.

  1. See Explanation section for answer.

Answer(s): A

Explanation:

Use the company hardware architecture to run the deployment: On-premises Use sandbox environments to develop extensions: Online Allow tenants to connect to Shopify with the standard connector: Online Use Microsoft Power Automate to create a workflow that calls a business event: Online

When deploying Microsoft Dynamics 365 Business Central, there are two main deployment types to consider: On-premises and Online.
On-premises Deployment:
The requirement to use the company's hardware architecture implies a need for an on-premises deployment. This is because on-premises deployment allows for the application to be installed and run directly from the company's in-house servers and computing infrastructure, giving full control over the environment and data.

Online Deployment:
The use of sandbox environments for developing extensions is a feature provided in the online version of Business Central. Sandbox environments are a part of the service offered in the cloud- based version, which allows developers to test and develop without affecting the live environment. Connection to Shopify with the standard connector implies an online deployment. The standard connector is typically a cloud-based service that allows Business Central to connect with other cloud platforms like Shopify, which is more seamlessly integrated with the online version. Lastly, the use of Microsoft Power Automate to create a workflow that calls a business event suggests an online deployment. Power Automate is a cloud-based service designed to create automated workflows between applications and services - which aligns with the services provided by the online version of Business Central.
Therefore, each requirement aligns with the deployment types as indicated above.



DRAG DROP (Drag and Drop is not supported)
A company is examining Connect apps and Add-on apps for use with Business Central. You need to describe the development language requirements for Connect apps and Add-on apps. How should you describe the app language requirements? To answer, move the appropriate app types to the correct descriptions. You may use each app type once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Developed by using any coding language: Connect app
Developed by using AL language in Visual Studio Code: Add-on app

In Microsoft Dynamics 365 Business Central, there are distinct types of applications that can be developed: Connect apps and Add-on apps. Each has its own development language requirements:
Connect apps:
Connect apps are designed to connect Business Central with external services or applications. They are often developed using a variety of programming languages, not limited to the AL language, and can be hosted outside of the Business Central environment. Therefore, when a description states that the app is developed using any coding language, it generally refers to a Connect app. This type of app integrates with Business Central through APIs and web services.
Add-on apps:
Add-on apps are built to extend the functionality of Business Central within the application itself. These are developed using the AL language, which is the programming language for Business Central, and they are created and managed within the Visual Studio Code environment with the AL Language extension. An Add-on app is typically a Business Central extension that is directly installed into the Business Central environment.

The language and environment used for developing these apps are key differentiators between Connect apps and Add-on apps.



DRAG DROP (Drag and Drop is not supported)
A company is implementing Business Central.
In the per-tenant extension, TableA Header and TableA Line are document tables, and TableB Header and TableB Line are document history tables.
The company requires that the resulting dataset of query objects contain the following records:
- All records from TableA Header even if no matching record value exists in the linked TableA Line
- Records from TableB Header where a match is found in the linked TableB Line field

You need to configure the linked data item to generate the required dataset.
Which SqlJoinType should you use? To answer, move the appropriate SqUoinTypes to the correct dataset requirements. You may use each SqlJoinType once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Include all records from TableA Header even if no matching record value exists in the linked TableA Line: LeftOuterJoin
Include only matched records from TableB Header: InnerJoin

In SQL and similarly in Business Central when defining table relationships in query objects, the type of join determines how records from one table are combined with records from another table. Here's what each join type means in the context of the company's requirements:
LeftOuterJoin:
A LeftOuterJoin includes all records from the 'left' table (TableA Header) and the matched records from the 'right' table (TableA Line). If there is no match, the result is NULL on the side of the 'right' table. This is why it fits the requirement to include all records from TableA Header even if there is no matching record in TableA Line.
InnerJoin:
An InnerJoin includes records when there is at least one match in both tables. So, it will only include records from TableB Header where a corresponding match is found in TableB Line. If there is no match, the records from TableB Header will not appear in the result set. This aligns with the requirement to include only matched records from TableB Header. By using these join types, the company can ensure that their dataset includes the appropriate records from the document tables and document history tables according to their specified requirements.



Page 5 of 15



Post your Comments and Discuss Microsoft MB-820 exam with other Community members:

TwZ commented on June 18, 2024
Question 25: correct answer: Permissions = tabledata "Boxes" = rm; https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-permissions-property
PORTUGAL
upvote

lporro commented on June 05, 2024
Question 10: if you look there it says 90 days https://learn.microsoft.com/en-us/training/modules/easy-application-upgrade/consider-update-lifecycle
Anonymous
upvote