Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E704 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

Contribute your Thoughts:

Delmy
1 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
Rosalyn
16 days ago
A) New attributes must be created as custom_attribute to restrict the access using ACL
upvoted 0 times
...
...
Lourdes
2 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 days ago
User 3: Agreed, we need to make sure only those with access permission can retrieve the new attribute data.
upvoted 0 times
...
Una
23 days ago
User 2: Yeah, that sounds like the best way to protect our custom attributes from unauthorized API consumers.
upvoted 0 times
...
Nelida
1 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
2 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
2 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
1 months ago
User2: I agree, extending the API interface seems like the right way to control access.
upvoted 0 times
...
Yuki
1 months ago
User1: I think option D is the best choice.
upvoted 0 times
...
...
Tambra
2 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
15 days ago
Extending the product API interface is another valid approach for restricting access.
upvoted 0 times
...
Tracey
16 days ago
D) New attributes must be created by extending the product API interface, to restrict access using ACL.
upvoted 0 times
...
Launa
21 days ago
That's correct. Extension attributes are the way to go for restricting access.
upvoted 0 times
...
Nickolas
29 days ago
B) New attribute must be created as extension_attribute to restrict the access using ACL
upvoted 0 times
...
Johnetta
1 months ago
Extending the product API interface is also a valid option for restricting access.
upvoted 0 times
...
Vicente
1 months ago
D) New attributes must be created by extending the product API interface, to restrict access using ACL.
upvoted 0 times
...
Destiny
1 months ago
That's correct. Extension attributes are the way to go for restricting access.
upvoted 0 times
...
Daniel
2 months ago
B) New attribute must be created as extension_attribute to restrict the access using ACL
upvoted 0 times
...
...
Oliva
2 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
2 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
3 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
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77