Google Cloud - Apigee Certified API Engineer Exam - Topic 11 Question 14 Discussion

Actual exam question for Google's Google Cloud - Apigee Certified API Engineer exam

Question #: 14
Topic #: 11

[All Google Cloud - Apigee Certified API Engineer Questions]

How can we add custom objects to an OpenAPI Specification 2.0?

ABy prefixing x- before the name of the custom object

BBy prefixing c- before the name of the custom object

CBy prefixing ext- before the name of the custom object

DOpen API specification does not allow custom objects

Show Suggested Answer

Suggested Answer: B

by Golda at Nov 20, 2025, 09:05 PM

Limited Time Offer

25%

Off

Get Premium Google Cloud - Apigee Certified API Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Hollis

7 days ago

C seems off. I’ve never seen ext- used for this purpose.

upvoted 0 times

...

Allene

12 days ago

I feel confident about A too. It’s widely used in APIs.

upvoted 0 times

...

Bulah

17 days ago

Definitely not D. A is the right choice.

upvoted 0 times

...

Princess

22 days ago

I’m not sure. What if it’s D? No custom objects allowed?

upvoted 0 times

...

Blondell

27 days ago

Yeah, I agree with A. It makes sense for custom objects.

upvoted 0 times

...

Ty

1 month ago

I think it's A. The x- prefix is common for extensions.

upvoted 0 times

...

Norah

1 month ago

I thought custom objects were a no-go in 2.0!

upvoted 0 times

...

Cheryl

2 months ago

I've always used x- too, makes sense!

upvoted 0 times

...

Shanice

2 months ago

Wait, are you sure D) isn't true?

upvoted 0 times

...

Rodrigo

2 months ago

Totally agree, x- is the way to go!

upvoted 0 times

...

Willodean

2 months ago

A) is correct, you use x- for custom objects.

upvoted 0 times

...

Vanesa

3 months ago

A) By prefixing x- before the name of the custom object. Easy peasy!

upvoted 0 times

...

Anastacia

3 months ago

D) Open API specification does not allow custom objects. Wait, what? I thought we could do anything with APIs these days!

upvoted 0 times

...

Pansy

3 months ago

C) By prefixing ext- before the name of the custom object

upvoted 0 times

...

Truman

3 months ago

I feel like the x- prefix is correct, but I also remember something about c- and ext- prefixes from another practice question.

upvoted 0 times

...

Margarita

3 months ago

I thought OpenAPI 2.0 didn't allow for custom objects at all, but maybe I misread that section in the notes.

upvoted 0 times

...

Silvana

3 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.

upvoted 0 times

...

Lashawnda

4 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.

upvoted 0 times

...

Salome

4 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.

upvoted 0 times

...

Royce

4 months ago

A) By prefixing x- before the name of the custom object

upvoted 0 times

...

Nobuko

4 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.

upvoted 0 times

...

Corrinne

5 months ago

I'll just go with C) By prefixing ext- before the name of the custom object. Sounds more professional.

upvoted 0 times

...

Selene

5 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.

upvoted 0 times

...

Dulce

5 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.

upvoted 0 times

...