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

Salesforce Exam Platform Developer II Topic 5 Question 113 Discussion

Actual exam question for Salesforce's Platform Developer II exam
Question #: 113
Topic #: 5
[All Platform Developer II Questions]

A developer is developing a reusable Aura component that will reside on an sObject Lightning page with the following HTML snippet:

How can the component"5 controller get the context of the Lightning page that the sObject is on without requiring additional test coverage?

Show Suggested Answer Hide Answer
Suggested Answer: A

By implementing force:hasSobjectName, the Aura component can retrieve the sObject context of the record page it is placed on without needing additional information. This interface provides the component with the API name of the sObject being displayed.


Aura Components Developer Guide

Contribute your Thoughts:

Chan
1 months ago
Wait, so we're supposed to get the context of the Lightning page without writing any tests? Sounds like a job for the magical App Builder fairies. D all the way!
upvoted 0 times
...
Cassandra
1 months ago
A? Really? Adding force:hasSobjectName to the implements attribute? That's like using a sledgehammer to crack a nut. D is the way to go, no doubt.
upvoted 0 times
...
Tarra
1 months ago
Hmm, B seems a bit too complicated. Why use an Apex class when we can just use the built-in Aura capabilities? I'd go with D.
upvoted 0 times
...
Lakeesha
2 months ago
Option C looks interesting, but I'm not sure if setting the sObject type as a component attribute is the best approach here. Seems like it might be a bit of a hack.
upvoted 0 times
Kizzy
4 days ago
A: Yeah, it could get messy. Option D seems like a cleaner way to handle it.
upvoted 0 times
...
Rana
5 days ago
B: I agree, setting the sObject type as a component attribute might not be the most elegant solution.
upvoted 0 times
...
Margurite
16 days ago
A: I think option D might be a better approach. Creating a design attribute and configuring it via App Builder seems more straightforward.
upvoted 0 times
...
...
Della
2 months ago
But wouldn't adding force:hasSobjectName provide the context of the Lightning page without needing additional test coverage?
upvoted 0 times
...
Nina
2 months ago
I think the answer is D. Creating a design attribute and configuring it via the App Builder seems like the most straightforward way to get the context of the Lightning page without additional test coverage.
upvoted 0 times
...
Sue
2 months ago
I disagree, I believe the correct answer is C) Set the sObject type as a component attribute.
upvoted 0 times
...
Della
2 months ago
I think the answer is A) Add force:hasSobjectName to the implements attribute.
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