ServiceNow Exam CIS-CPG Topic 2 Question 33 Discussion

Actual exam question for ServiceNow's Certified Implementation Specialist - Cloud Provisioning and Governance exam

Question #: 33
Topic #: 2

[All Certified Implementation Specialist - Cloud Provisioning and Governance Questions]

When creating a new CAPI API, what is the suggested starting version number to prevent conflicts with out-of-the-box CAPI APIs?

A2.0

B1.5

C0.1

D1.1

Show Suggested Answer

Suggested Answer: A

by Trina at May 31, 2024, 10:39 PM

Limited Time Offer

25%

Off

Get Premium CIS-CPG Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Justa

3 months ago

I don't know about you, but I'm picturing a epic CAPI API battle royale. May the best version number win!

upvoted 0 times

Loren

3 months ago

B) 1.5

upvoted 0 times

...

William

3 months ago

A) 2.0

upvoted 0 times

...

Merilyn

4 months ago

1.1? Seriously? That's so boring. Where's the excitement in that? I'm going with 0.1 just for the fun of it.

upvoted 0 times

...

Lorenza

4 months ago

2.0, all the way! Go big or go home, I say. Take those CAPI APIs head-on and show them who's boss!

upvoted 0 times

Carmen

3 months ago

I see your point, but I still think 2.0 is the way to go. It's all about pushing boundaries and innovation.

upvoted 0 times

...

Thaddeus

3 months ago

I think 1.1 might be a safer choice to avoid conflicts with existing APIs.

upvoted 0 times

...

Joye

3 months ago

I agree, starting at 2.0 is a bold move. It sets a high standard right from the beginning.

upvoted 0 times

...

Laura

4 months ago

Nah, 1.5 is the way to go. That way, you can show you mean business, but you're still leaving room for growth.

upvoted 0 times

Chan

3 months ago

Yeah, it strikes a good balance between stability and progress.

upvoted 0 times

...

Royal

3 months ago

I agree, it's a safe choice.

upvoted 0 times

...

Kassandra

4 months ago

I think 1.5 is a good starting point.

upvoted 0 times

...

Chantell

4 months ago

I disagree, I believe it's 2.0 to prevent conflicts

upvoted 0 times

...

Casey

4 months ago

I think the suggested starting version number is 1.1

upvoted 0 times

...

Wade

4 months ago

I think 0.1 is the way to go. Start small, right? No need to step on the toes of the big boys at CAPI.

upvoted 0 times

Amber

3 months ago

I agree, let's not cause any conflicts with the existing APIs.

upvoted 0 times

...

Dona

3 months ago

Starting at 0.1 sounds like a safe bet.

upvoted 0 times

...

Alesia

3 months ago

D) 1.1

upvoted 0 times

...

Pansy

3 months ago

I would go with 2.0 to show that your API is up-to-date and robust.

upvoted 0 times

...

Tien

3 months ago

C) 0.1

upvoted 0 times

...

Ona

3 months ago

B) 1.5

upvoted 0 times

...

Laura

3 months ago

I think 1.1 might be a better choice to align with existing versions.

upvoted 0 times

...

Dino

4 months ago

A) 2.0

upvoted 0 times

...

Ilene

4 months ago

I agree, starting at 0.1 seems like a safe bet.

upvoted 0 times

...