New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe AD0-E704 Exam - Topic 13 Question 60 Discussion

Actual exam question for Adobe's AD0-E704 exam
Question #: 60
Topic #: 13
[All AD0-E704 Questions]

Suppose in the product rest API in Magento, you added a new attribute. But this attribute can be accessed by API consumers only when they have access permission. How do you create the attributes following the above condition:

Show Suggested Answer Hide Answer
Suggested Answer: B

by Stephen at Apr 09, 2025, 08:54 AM

Limited Time Offer

25%

Off

Get Premium AD0-E704 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Myrtie
2 months ago
C is misleading, we can set permissions for REST API attributes.
upvoted 0 times
...
Arletta
2 months ago
I disagree, B seems more appropriate for extension attributes.
upvoted 0 times
...
Carin
3 months ago
D is the best choice here, extending the API interface makes sense.
upvoted 0 times
...
Rodrigo
3 months ago
Wait, can we really restrict access like that? Sounds tricky!
upvoted 0 times
...
Davida
3 months ago
I think option A is correct. Custom attributes are the way to go.
upvoted 0 times
...
Cyril
3 months ago
Extending the product API interface sounds familiar, but I can't remember if that's the only way to manage access permissions.
upvoted 0 times
...
Vincent
4 months ago
I feel like we discussed that access permissions can be tricky with REST APIs, but I can't recall if they apply to attributes specifically.
upvoted 0 times
...
Kiley
4 months ago
I think extension attributes might be the way to go here, but I need to double-check how they interact with ACL permissions.
upvoted 0 times
...
Craig
4 months ago
I remember something about custom attributes and ACL, but I'm not sure if that's the right way to restrict access.
upvoted 0 times
...
Sonia
4 months ago
Okay, I've got a plan. I'll create the new attribute as an extension_attribute and then set up the appropriate ACL permissions to control access. Feeling confident about this one.
upvoted 0 times
...
Micaela
4 months ago
I think the key here is understanding how to use ACL to restrict access to the new attribute. Option B seems like the right approach, but I'll double-check the details.
upvoted 0 times
...
Daniela
5 months ago
Hmm, I'm a bit confused about the difference between custom_attribute and extension_attribute. I'll need to review that before deciding.
upvoted 0 times
...
Werner
5 months ago
This looks like a tricky one. I'll need to think through the different options carefully.
upvoted 0 times
...
Delmy
10 months ago
Option E: Just use a completely undocumented, secret attribute that only the dev team knows about. That'll show those pesky API consumers!
upvoted 0 times
Lina
8 months ago
D) New attributes must be created by extending the product API interface, to restrict access using ACL.
upvoted 0 times
...
Karon
8 months ago
B) New attribute must be created as extension_attribute to restrict the access using ACL
upvoted 0 times
...
Rosalyn
9 months ago
A) New attributes must be created as custom_attribute to restrict the access using ACL
upvoted 0 times
...
...
Lourdes
10 months ago
B is the way to go, gotta keep those prying API consumers out of my precious custom attributes!
upvoted 0 times
Carman
9 months ago
User 3: Agreed, we need to make sure only those with access permission can retrieve the new attribute data.
upvoted 0 times
...
Una
9 months ago
User 2: Yeah, that sounds like the best way to protect our custom attributes from unauthorized API consumers.
upvoted 0 times
...
Nelida
10 months ago
User 1: I think we should go with option B) New attribute must be created as extension_attribute to restrict the access using ACL.
upvoted 0 times
...
...
Geoffrey
10 months ago
C is just wrong, you can definitely set up access permissions for the REST API. This is basic Magento stuff.
upvoted 0 times
...
Louvenia
10 months ago
I'd go with option D. Extending the API interface is the way to go if you want to control access permissions.
upvoted 0 times
Eric
10 months ago
User2: I agree, extending the API interface seems like the right way to control access.
upvoted 0 times
...
Yuki
10 months ago
User1: I think option D is the best choice.
upvoted 0 times
...
...
Tambra
11 months ago
Option B makes the most sense to me. Extension attributes are designed for this exact use case of restricting access.
upvoted 0 times
Viki
9 months ago
Extending the product API interface is another valid approach for restricting access.
upvoted 0 times
...
Tracey
9 months ago
D) New attributes must be created by extending the product API interface, to restrict access using ACL.
upvoted 0 times
...
Launa
9 months ago
That's correct. Extension attributes are the way to go for restricting access.
upvoted 0 times
...
Nickolas
9 months ago
B) New attribute must be created as extension_attribute to restrict the access using ACL
upvoted 0 times
...
Johnetta
9 months ago
Extending the product API interface is also a valid option for restricting access.
upvoted 0 times
...
Vicente
9 months ago
D) New attributes must be created by extending the product API interface, to restrict access using ACL.
upvoted 0 times
...
Destiny
10 months ago
That's correct. Extension attributes are the way to go for restricting access.
upvoted 0 times
...
Daniel
10 months ago
B) New attribute must be created as extension_attribute to restrict the access using ACL
upvoted 0 times
...
...
Oliva
11 months ago
I'm not sure, but I think C) We can't create access permission for REST API, it's only applicable for entity and repository.
upvoted 0 times
...
Donte
11 months ago
I disagree, I believe the correct answer is D) New attributes must be created by extending the product API interface, to restrict access using ACL.
upvoted 0 times
...
Alyce
11 months ago
I think the answer is A) New attributes must be created as custom_attribute to restrict the access using ACL.
upvoted 0 times
...

Save Cancel