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 I Topic 3 Question 65 Discussion

Actual exam question for Salesforce's Platform Developer I exam
Question #: 65
Topic #: 3
[All Platform Developer I Questions]

A developer must create a Lightning component that allows users to input Contact record information to create a Contact record, including a Salary c custom field.

What should the developer use, along with a lightning-record-edit-form, so that Salary__c field functions as a currency input and is only viewable and editable by users that have the correct field level permissions on Salary _c?

A)

B)

C)

D)

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Kina
28 days ago
I'm just going to go with Option C and hope I don't have to deal with any currency formatting issues. After all, money doesn't grow on trees, and neither do good solutions, apparently.
upvoted 0 times
Charlie
6 days ago
User 2: Yeah, I agree. It's important to make sure the field is only viewable and editable by users with the correct permissions.
upvoted 0 times
...
Stephaine
10 days ago
User 1: I think Option C is the best choice for handling the currency input.
upvoted 0 times
...
...
Jacinta
1 months ago
Option A? Really? Who would use a plain old text input for a currency field? It's like trying to put a square peg in a round hole. I'm going with Option C, no doubt about it.
upvoted 0 times
...
Bulah
1 months ago
Hmm, I'm a bit torn between Option B and Option C. Both seem to address the requirements, but I think I'll go with Option C. The lightning-input feels a bit more straightforward.
upvoted 0 times
Deangelo
13 hours ago
User 2: Yeah, I think Option C is the best choice for making the Salary__c field function as a currency input.
upvoted 0 times
...
Arminda
6 days ago
User 1: I agree, Option C with the lightning-input seems like the way to go.
upvoted 0 times
...
...
Glory
2 months ago
I'm going with Option D. The lightning-formatted-number component will give us the currency formatting, and the lightning-input-field will handle the permissions. Seems like a clean solution to me.
upvoted 0 times
Rupert
1 months ago
Yes, Option D provides the necessary components for currency formatting and field level permissions.
upvoted 0 times
...
Mee
1 months ago
I agree, Option D seems like the best choice for this scenario.
upvoted 0 times
...
...
Jaclyn
2 months ago
I'm not sure, but I think Option C might also work well for this scenario. It looks like it could handle field level permissions effectively.
upvoted 0 times
...
Anglea
2 months ago
I agree with Hannah. Option A seems like the best choice for ensuring the Salary__c field functions correctly.
upvoted 0 times
...
Jess
2 months ago
Option C looks like the way to go. The lightning-input with the type='currency' should give us the currency functionality we need, and the lightning-input-field will handle the permissions for us.
upvoted 0 times
Rosita
30 days ago
Option C is definitely the right choice. The combination of lightning-input with type='currency' and lightning-input-field will meet the requirements for the Salary__c field.
upvoted 0 times
...
Alyce
1 months ago
I think Option C is the most suitable. Using lightning-input with type='currency' will provide the currency functionality, and lightning-input-field will control the field level permissions.
upvoted 0 times
...
Alyce
1 months ago
Yes, Option C is the way to go. It's important to ensure that only users with the correct permissions can view and edit the Salary__c field.
upvoted 0 times
...
Thomasena
2 months ago
I agree, Option C seems like the best choice. The lightning-input with type='currency' will handle the currency input, and the lightning-input-field will take care of the permissions.
upvoted 0 times
...
...
Hannah
2 months ago
I think the developer should use Option A because it looks like it provides a currency input field.
upvoted 0 times
...

Save Cancel