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

Salesforce B2B Commerce for Developers Accredited Professional (AP-202) Exam - Topic 6 Question 72 Discussion

Actual exam question for Salesforce's B2B Commerce for Developers Accredited Professional (AP-202) exam
Question #: 72
Topic #: 6
[All B2B Commerce for Developers Accredited Professional (AP-202) Questions]

An administrator has just provided a developer with a new org and username. Which two sets of steps can the developer use to authorize the org and begin deploying Lightning web components?

What should a developer do to expose a public property in a Lightning web component?

Show Suggested Answer Hide Answer
Suggested Answer: C

To make an integration available for selection in Salesforce B2B Commerce, a developer must create a RegisteredExternalService record. This can be accomplished using tools like Workbench, which allow for direct interaction with Salesforce's backend database. By registering the external service, the integration becomes selectable within the B2B Commerce setup, allowing it to be associated with specific stores or contexts. Salesforce documentation on integrating external services with B2B Commerce provides step-by-step instructions on registering these services to enable seamless integration and functionality within the platform.


Contribute your Thoughts:

0/2000 characters
Nan
3 months ago
Just to clarify, @api is the correct answer here, right?
upvoted 0 times
...
Karon
3 months ago
I thought @public was a thing too, but I guess not?
upvoted 0 times
...
Elvera
4 months ago
Wait, isn't @track still relevant for reactive properties?
upvoted 0 times
...
Breana
4 months ago
Totally agree, @api is the way to go!
upvoted 0 times
...
Oliva
4 months ago
You need to use @api to expose a public property!
upvoted 0 times
...
Holley
4 months ago
I definitely recall that @api is the correct decorator for exposing public properties, but I need to double-check the steps for authorizing the org.
upvoted 0 times
...
Ressie
4 months ago
I feel like there was a similar question on the last practice exam about decorators, and I think @track was mentioned, but it doesn't seem right for public properties.
upvoted 0 times
...
Lizette
5 months ago
I remember practicing a question about public properties in Lightning components, and I think it was related to using @api, but I could be mixing it up with something else.
upvoted 0 times
...
Pearly
5 months ago
I think to authorize the org, we might need to use the Salesforce CLI, but I'm not completely sure about the exact commands.
upvoted 0 times
...
Rochell
5 months ago
Alright, let's do this. The key here is to remember the different decorators used in Lightning web components. I'm pretty sure the answer for the public property part is @api, but I'll double-check the other options just to be sure.
upvoted 0 times
...
Bo
5 months ago
I'm a little confused by the first part of the question. I know there are different ways to authorize an org, but I'm not sure which two sets of steps they're looking for. I'll have to think about that one.
upvoted 0 times
...
Franchesca
5 months ago
Ah, this is a good one. I remember learning about the @api decorator for exposing public properties in Lightning web components. I'm pretty confident I can select the right answer for that part.
upvoted 0 times
...
Josue
5 months ago
Okay, let's see here. The first part of the question is asking about authorizing the org and deploying Lightning web components. I'm a bit unsure about the specific steps, but I'll try to think it through.
upvoted 0 times
...
Teddy
5 months ago
Hmm, this question seems straightforward. I think I'll start by reviewing the steps to authorize the new org and then look at the options for exposing a public property in a Lightning web component.
upvoted 0 times
...
Lewis
10 months ago
Decorating with @property? That's not even a real Aura/LWC decorator. This exam is testing our knowledge, not our ability to make up new syntax!
upvoted 0 times
...
Barrie
10 months ago
I'm gonna go with D. Seems like the obvious choice to make a property public. Maybe I should've tried that first before wasting time on the other options.
upvoted 0 times
Deeann
8 months ago
Ilona: Good to know we're on the same page. Let's try it out and see if it works.
upvoted 0 times
...
Ilona
8 months ago
User 2: Yeah, I agree. @api is the way to go for that.
upvoted 0 times
...
Noah
8 months ago
User 1: I think D is the right choice. It makes sense to use @api to expose a public property.
upvoted 0 times
...
...
Britt
10 months ago
Hah, decorating the field with @track? That's for internal state, not public properties. Rookie mistake!
upvoted 0 times
Adelina
9 months ago
Dorthy: Oh, my bad. Thanks for the clarification!
upvoted 0 times
...
Dorthy
9 months ago
User 2: No, @api is the correct way to expose a public property in a Lightning web component.
upvoted 0 times
...
Jarod
9 months ago
User 1: I think the developer should decorate the field with @api.
upvoted 0 times
...
Viki
9 months ago
User 3: Definitely not @track, that's for internal state
upvoted 0 times
...
Lai
9 months ago
User 2: Lai is right, @property is used to expose public properties
upvoted 0 times
...
Margurite
9 months ago
User 1: A) Decorate the field with @property
upvoted 0 times
...
...
Arminda
10 months ago
I tried option C earlier and it didn't work. Guess I need to read the docs more carefully next time.
upvoted 0 times
...
Floyd
10 months ago
Option D is the correct answer. The @api decorator exposes the field as a public property in the Lightning web component.
upvoted 0 times
Barrett
9 months ago
D) Decorate the field with @api
upvoted 0 times
...
Odette
9 months ago
C) Decorate the field with @public
upvoted 0 times
...
Leila
10 months ago
B) Decorate the field with @track
upvoted 0 times
...
Mertie
10 months ago
A) Decorate the field with @property
upvoted 0 times
...
...
Jolanda
11 months ago
I'm not sure, but I think @track is also a valid option for exposing a public property.
upvoted 0 times
...
Sharen
11 months ago
I agree with Glory, @api is the correct way to expose a public property.
upvoted 0 times
...
Glory
11 months ago
I think the developer should decorate the field with @api.
upvoted 0 times
...

Save Cancel