Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft MB-820 Exam - Topic 6 Question 14 Discussion

Posted by Madelyn on Jun 20, 2024 at 09:52 AM

You are developing an app.

You plan to publish the app to Microsoft AppSource.

You need to assign an object range for the app.

Which object range should you use?

Suggested Answer: A

Using InherentPermissions in an event subscriber with the specified syntax could potentially resolve the permission issues related to MyTable, provided that the permissions specified (in this case, 'R' for Read) align with the minimum necessary for the users to perform their tasks. This approach allows the app to grant permissions dynamically based on the context of the event subscriber, which in this case is involved with inserting data into MyTable. By granting Read permission at the event level, it ensures that users have the necessary permissions to interact with MyTable in the context of the operations facilitated by the event subscriber, without needing to alter existing permission sets or grant broader permissions than necessary. This solution adheres to the principle of least privilege by ensuring that permissions are granted only within the narrow scope needed for specific operations, thereby potentially resolving the reported user issues in a secure and controlled manner.


Get Premium MB-820 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
33 comments · newest first
RU
Ruthann 10 months ago
Why are there so many ranges? This is confusing!
RA
Rasheeda 11 months ago
B could work too, but A is definitely safer.
DE
Desire 11 months ago
Wait, can we really use 7000000 to 74999999? That sounds off.
TI
Timmy 11 months ago
Totally agree, A seems to fit the criteria best!
CL
Clare 11 months ago
I think option A is the right choice for custom objects.
MA
Major 12 months ago
I feel like the standard range of 1 to 49999 is too limiting for a published app. I think we need to go higher.
MI
Michal 12 months ago
I'm a bit confused about the specific country range option. Does that really apply here, or is it more for localization?
GR
Gracia 12 months ago
I remember practicing a similar question, and I think the broader range of 50000 to 99999 might be correct for custom objects.
VI
Vince 1 year ago
I think the object range for custom apps should be between 50000 and 59999, but I'm not entirely sure if that's the only option.
GL
Glenn 1 year ago
I'm leaning towards A - a custom object within 50000 to 59999. That seems like a safe bet, but I'll review the instructions carefully to confirm.
DI
Dierdre 1 year ago
Option D sounds interesting - an object range requested from Microsoft. I wonder if that's the recommended approach, or if there's a more standard range I should use.
TH
Thad 1 year ago
Hmm, I'm a bit unsure about this one. I'll need to double-check the guidelines for publishing to AppSource to make sure I select the right object range.
KA
Kathrine 1 year ago
I think the answer is B - a custom object within the range 50000 to 99999. That seems like the most appropriate range for an app published to Microsoft AppSource.
RA
Ramonita 1 year ago
The question mentions publishing to AppSource, so I'm thinking B is the way to go. A custom range from 50000 to 99999 seems like the best fit.
AR
Art 1 year ago
Hmm, I'm a little unsure about the differences between Vlocity Guided Selling and the regular Vlocity Cart. I'll need to review my notes to make sure I don't miss anything important.
NO
Noble 1 year ago
Hmm, this is a tricky one. I need to think carefully about which of these options would not be a countermeasure for protecting cloud operations.
KE
Kenny 1 year ago
Okay, let me see here. I don't think restarting the web app is required, and the Snapshot Debugger seems unrelated. I'm going to go with option B - it makes sense that Smart Detection needs some time to learn the app's normal behavior.
ME
Meghan 1 year ago
I'm gonna go with option F: Just make my own object range and pretend it's approved. What could go wrong?
NO
Nobuko 1 year ago
E is the obvious choice. Why pay Microsoft when you can just use the free standard range? Gotta save those pennies!
EV
Eva 1 year ago
Option B looks good to me. The wider range of 50000 to 99999 gives me more flexibility in my app design.
CH
Chery 1 year ago
↳ replying to Eva
I would go with option E for a more standard approach.
KR
Kristian 1 year ago
↳ replying to Eva
I think option A might be better for my specific needs.
JO
Joseph 1 year ago
↳ replying to Eva
I agree, option B does provide more flexibility in app design.
BE
Beth 1 year ago
I'm leaning towards option C. Dividing the range by countries makes sense to me for a global app deployment.
HY
Hyman 1 year ago
↳ replying to Beth
Using specific country ranges can definitely help with organization and scalability.
ES
Essie 1 year ago
↳ replying to Beth
I agree, dividing by countries can help with global deployment.
NE
Nelida 1 year ago
↳ replying to Beth
I think option C is a good choice. It allows for specific country ranges.
MA
Marylyn 1 year ago
I think option D is the way to go. Getting the object range directly from Microsoft is the safest bet to ensure compatibility with AppSource.
AD
Adria 1 year ago
↳ replying to Marylyn
Using an object range requested from Microsoft is a smart move for compatibility.
KI
Kirby 1 year ago
↳ replying to Marylyn
I agree, option D seems like the most reliable choice for the object range.
AM
Amina 2 years ago
I agree with Pearly, we should go with option B for future expansion potential.
PE
Pearly 2 years ago
I disagree, I believe option B, custom object within the range 50000 to 99999, would be better for scalability.
ED
Edwin 2 years ago
I think we should use option A, custom object within the range 50000 to 59999.
0/2000 characters

Save Cancel