Microsoft MB-500 Exam - Topic 7 Question 98 Discussion

Actual exam question for Microsoft's MB-500 exam

Question #: 98
Topic #: 7

A company requires a Power Apps app that will enable users to view and create new leads in Dynamics 365 from the app. The data is in a custom entity named LeadsTable, which is not accessible outside Dynamics 365. You need to make the data available outside Dynamics 365. What should you do?

AEnable IsPublic for the data entity linked to the LeadsTable.

BAssign the create, read, update, and delete operations for the LeadsTable to the sales associate role.

CCreate an aggregate data entity for the LeadsTable.

DEnable data management capabilities on the data entity.

Show Suggested Answer

Suggested Answer: A

by Janine at Jan 09, 2025, 10:13 AM

Limited Time Offer

25%

Off

Get Premium MB-500 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Yan

5 months ago

Creating an aggregate entity sounds like a solid option too.

upvoted 0 times

...

Gwenn

5 months ago

Wait, can you really just make it public like that?

upvoted 0 times

...

Cassi

5 months ago

Not sure about that, isn't there more to it?

upvoted 0 times

...

Lon

5 months ago

I agree, that's the way to go!

upvoted 0 times

...

Raelene

6 months ago

You need to enable IsPublic for external access.

upvoted 0 times

...

Elza

6 months ago

Enabling data management capabilities in option D seems like it could help, but I can't remember if that's the best approach for this scenario.

upvoted 0 times

...

Rene

6 months ago

I'm a bit confused about the aggregate data entity in option C. I don't recall if that actually makes the data accessible outside Dynamics 365.

upvoted 0 times

...

Julian

6 months ago

I think I practiced a question similar to this where we had to manage permissions. Option B sounds familiar, but I feel like it might not be enough on its own.

upvoted 0 times

...

Lauran

6 months ago

I remember something about making entities public, so maybe option A is the right choice? But I'm not entirely sure how that works with custom entities.

upvoted 0 times

...

Cheryll

6 months ago

This seems like a good opportunity to demonstrate my understanding of Dynamics 365 data management. I think creating an aggregate data entity is the most appropriate solution, as it will allow the Power Apps app to access the data without exposing the underlying table.

upvoted 0 times

...

Billy

6 months ago

I'm not sure about the "IsPublic" option. Does that mean the data will be publicly accessible, or just accessible to the app? I'll need to research that a bit more before deciding.

upvoted 0 times

...

Casandra

6 months ago

Okay, I've got this. The question is asking us to make the LeadsTable data available outside of Dynamics 365, so I think creating an aggregate data entity is the way to go. That should do the trick.

upvoted 0 times

...

Marge

6 months ago

Hmm, I'm a bit confused about the difference between a data entity and an aggregate data entity. I'll need to review the options carefully to understand which one is the best approach here.

upvoted 0 times

...

Katie

7 months ago

This seems like a straightforward question about making data accessible outside of Dynamics 365. I think the key is to create a data entity that can be used by the Power Apps app.

upvoted 0 times

...

Annmarie

1 year ago

D sounds like the safest option. Enabling data management capabilities should give us the access we need without too much risk.

upvoted 0 times

Mari

1 year ago

Let's go with option D then. It seems like the most reliable choice for our needs.

upvoted 0 times

...

Kanisha

1 year ago

Enabling data management capabilities sounds like a good solution to me as well.

upvoted 0 times

...

Nilsa

1 year ago

Yeah, I agree. It's important to ensure that we have the necessary access without compromising security.

upvoted 0 times

...

Renea

1 year ago

I think D is the best option too. It seems like the most secure way to make the data accessible.

upvoted 0 times

...

Anabel

1 year ago

This question is making my head spin. I wish I could just ask Clippy for the answer.

upvoted 0 times

Genevieve

1 year ago

I think option A sounds like the right choice.

upvoted 0 times

...

Haley

1 year ago

C) Create an aggregate data entity for the LeadsTable.

upvoted 0 times

...

Nieves

1 year ago

B) Assign the create, read, update, and delete operations for the LeadsTable to the sales associate role.

upvoted 0 times

...

Mitsue

1 year ago

A) Enable IsPublic for the data entity linked to the LeadsTable.

upvoted 0 times

...

Gerri

1 year ago

B is the way to go! Assign the necessary permissions to the sales associate role, and they'll be able to access the data as needed.

upvoted 0 times

...

Carma

1 year ago

Hmm, I'm not sure about this one. Enabling IsPublic for the data entity seems like a risky move, but I could be wrong.

upvoted 0 times

Nenita

1 year ago

B) Assign the create, read, update, and delete operations for the LeadsTable to the sales associate role.

upvoted 0 times

...

Annamae

1 year ago

B) Assign the create, read, update, and delete operations for the LeadsTable to the sales associate role.

upvoted 0 times

...

Anthony

1 year ago

A) Enable IsPublic for the data entity linked to the LeadsTable.

upvoted 0 times

...

Audry

1 year ago

A) Enable IsPublic for the data entity linked to the LeadsTable.

upvoted 0 times

...

Kandis

1 year ago

Hmm, that makes sense too. Let's see what others think before we make our final choice.

upvoted 0 times

...

Laurel

1 year ago

I disagree, I believe the correct answer is D) Enable data management capabilities on the data entity.

upvoted 0 times

...

Kandis

1 year ago

I think the answer is A) Enable IsPublic for the data entity linked to the LeadsTable.

upvoted 0 times

...

Martha

1 year ago

I think C is the correct answer. Creating an aggregate data entity will make the data available outside Dynamics 365 without exposing the underlying table.

upvoted 0 times