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 AZ-120 Exam - Topic 13 Question 82 Discussion

Posted by Lindsey on Dec 27, 2023 at 08:41 AM

You have an SAP workload on an Azure virtual machine.

You have a built-in role-based access control (RBAC) role definition in the JSON format.

You plan to change the built-in role definition to a custom role definition.

Which property value in the built-in role definition must you change?

Suggested Answer: C

Get Premium AZ-120 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
38 comments · newest first
MO
Moon 11 months ago
I thought roleHoae was the one to change? That's new to me!
DE
Dean 11 months ago
Nope, it's definitely assignableScopes.
RO
Rosann 12 months ago
Wait, are you sure it's not actions?
AL
Alex 12 months ago
I agree, assignableScopes is the key here!
LI
Lizette 1 year ago
You definitely need to change the assignableScopes.
AL
Alex 1 year ago
If I remember correctly, the notActions property is usually for restrictions, so it might not be the one we need to change.
ER
Erin 1 year ago
I’m a bit confused about the roleHoae property; I don’t recall seeing that in our materials.
GW
Gwenn 1 year ago
I remember practicing a similar question where we had to modify role definitions, and I think actions might be important too.
AM
Ammie 1 year ago
I think we need to change the assignableScopes property to create a custom role, but I'm not entirely sure.
LO
Louis 1 year ago
I'm confident the answer is "assignableScopes". The question states we're converting a built-in role to a custom role, so we'll need to update that property to define the new scope for the custom role.
SI
Sina 1 year ago
Hmm, I'm a bit unsure about this one. Is it the "actions" property we need to change, or the "assignableScopes"? I'll have to review the RBAC documentation again to be sure.
KI
Kirk 1 year ago
This seems straightforward. I think the property value we need to change is the "assignableScopes" since we're converting a built-in role to a custom role.
AR
Art 1 year ago
Okay, let me think this through. If we're changing a built-in role to a custom role, then we'll need to modify the "assignableScopes" property. That makes the most sense to me.
JU
Justine 1 year ago
Okay, I've got this. The key is understanding that the federal government can have its own unique accounting requirements, which may or may not align with standard GAAP. I'll weigh the options and select the most appropriate answer.
MA
Margurite 1 year ago
I'm feeling confident about this one. I'll make sure to set up the suggester properly and use the appropriate analyzer settings for the product name fields.
SC
Scarlet 1 year ago
Hmm, this looks tricky. I'll need to carefully review the OCAPI documentation to understand the proper request format.
NI
Nikita 1 year ago
This is tricky, I'm not totally sure about the differences between the technical, business, and operational environments. I'll have to think it through carefully.
JU
Justine 1 year ago
Ah, the age-old question: 'Which property do you change to create a custom role?' It's like asking 'Which button do you press to turn on the computer?' Gotta love these certification exams!
HU
Hui 1 year ago
Wait, hold up. Isn't the answer supposed to be C? I mean, 'roleHoae' sounds like the most important thing to modify, right? *chuckles*
LA
Lavera 1 year ago
I'm going to go with A. The 'assignableScopes' is where you define which resources the role can be assigned to, so that's the key property to change.
MO
Mollie 1 year ago
↳ replying to Lavera
Great, let's update the 'assignableScopes' in the role definition.
LA
Latricia 1 year ago
↳ replying to Lavera
I agree, changing 'assignableScopes' will define the resources for the role.
ON
Oneida 1 year ago
↳ replying to Lavera
Yes, 'assignableScopes' determines where the role can be assigned.
RE
Refugia 1 year ago
↳ replying to Lavera
I think you're right. 'assignableScopes' is the property to change.
MA
Malcom 1 year ago
I'm pretty sure it's B. The 'notActions' property is what you'd need to modify to create a custom role from a built-in one.
IV
Ivette 1 year ago
↳ replying to Malcom
C) roleHoae
RA
Ramonita 1 year ago
↳ replying to Malcom
B) notActions
KA
Kasandra 1 year ago
↳ replying to Malcom
A) assignableScopes
AM
Amie 2 years ago
Hmm, I think the answer is D. The 'actions' property is the one that defines the permissions in the role definition. Changing that would be the way to create a custom role.
GA
Gaynell 1 year ago
↳ replying to Amie
That makes sense. So, the correct answer is D - actions.
ER
Ernest 1 year ago
↳ replying to Amie
Yes, you are correct. Changing the 'actions' property is necessary to create a custom role.
CL
Clorinda 1 year ago
↳ replying to Amie
I think the answer is D. The 'actions' property is the one that defines the permissions in the role definition.
KA
Kate 2 years ago
I'm not sure, but I think actions might also need to be changed for a custom role definition.
GE
Germaine 2 years ago
I agree with Alethea, assignableScopes should be changed to create a custom role definition.
AL
Alethea 2 years ago
I think the property value that must be changed is assignableScopes.
AL
Alayna 2 years ago
I'm not sure, but I think we should also consider changing the actions property value.
AH
Ahmed 2 years ago
I agree with Geoffrey, assignableScopes is the property value that needs to be changed.
GE
Geoffrey 2 years ago
I think we need to change the assignableScopes property value.
0/2000 characters

Save Cancel