MENU
How can we add custom objects to an OpenAPI Specification 2.0?
Suggested Answer: B
Get Premium Google Cloud - Apigee Certified API Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
30 comments · newest first
HO
Hollis
6 months ago
C seems off. I’ve never seen ext- used for this purpose.
AL
Allene
6 months ago
I feel confident about A too. It’s widely used in APIs.
BU
Bulah
7 months ago
Definitely not D. A is the right choice.
PR
Princess
7 months ago
I’m not sure. What if it’s D? No custom objects allowed?
BL
Blondell
7 months ago
Yeah, I agree with A. It makes sense for custom objects.
TY
Ty
7 months ago
I think it's A. The x- prefix is common for extensions.
NO
Norah
7 months ago
I thought custom objects were a no-go in 2.0!
CH
Cheryl
8 months ago
I've always used x- too, makes sense!
SH
Shanice
8 months ago
Wait, are you sure D) isn't true?
RO
Rodrigo
8 months ago
Totally agree, x- is the way to go!
WI
Willodean
8 months ago
A) is correct, you use x- for custom objects.
VA
Vanesa
9 months ago
A) By prefixing x- before the name of the custom object. Easy peasy!
AN
Anastacia
9 months ago
D) Open API specification does not allow custom objects. Wait, what? I thought we could do anything with APIs these days!
PA
Pansy
9 months ago
C) By prefixing ext- before the name of the custom object
TR
Truman
9 months ago
I feel like the x- prefix is correct, but I also remember something about c- and ext- prefixes from another practice question.
MA
Margarita
9 months ago
I thought OpenAPI 2.0 didn't allow for custom objects at all, but maybe I misread that section in the notes.
SI
Silvana
9 months ago
I remember practicing a question about OpenAPI where we had to identify custom fields, and I feel like it was definitely the x- prefix.
LA
Lashawnda
10 months ago
I think we can add custom objects by using the x- prefix, but I'm not entirely sure if that's the only way.
SA
Salome
10 months ago
Okay, I think I've got this. The key is to use the x- prefix for any custom objects you want to add to the OpenAPI spec. Options B and C are not correct.
RO
Royce
10 months ago
A) By prefixing x- before the name of the custom object
NO
Nobuko
10 months ago
Ah, I remember learning about this in class. I'm pretty sure the answer is A - we prefix custom objects with x- to distinguish them from the standard OpenAPI elements.
CO
Corrinne
11 months ago
I'll just go with C) By prefixing ext- before the name of the custom object. Sounds more professional.
SE
Selene
11 months ago
I'm a bit confused by this question. I know OpenAPI has some flexibility for custom extensions, but I can't recall the specific syntax. I'll have to review my notes to be sure.
DU
Dulce
11 months ago
Hmm, I'm not entirely sure about this one. I know OpenAPI has some rules around custom objects, but I can't remember the exact prefix to use. I'll have to think this through carefully.
TO
Tonette
11 months ago
This looks like a straightforward question about OpenAPI Specification 2.0. I'm pretty confident I know the answer.
JE
Jesusita
6 months ago
A is definitely the right choice!
JO
Jolanda
6 months ago
D seems wrong too. Custom objects are allowed.
MA
Marleen
6 months ago
No way, I thought it was C.
SA
Sabine
6 months ago
Yeah, I agree with you, Allene.
AL
Allene
10 months ago
I think it's A! You just need to prefix with x-.