Opiniones sobre Develop and Secure APIs with Apigee X: Challenge Lab

3211 opiniones

Michal P. · Se revisó hace alrededor de 3 años

Srikanth S. · Se revisó hace alrededor de 3 años

Vgfdf X. · Se revisó hace alrededor de 3 años

corrie k. · Se revisó hace alrededor de 3 años

Moe H. · Se revisó hace alrededor de 3 años

asd f. · Se revisó hace alrededor de 3 años

Cannot pass Task 3 Checks, but tests are passing and everything appears to be complete and correct. Error is: Please add the 'Q-EnforceQuota' Quota policy with the correct configuration to the proxy endpoint preflow and redeploy the API proxy.

Angelo I. · Se revisó hace alrededor de 3 años

Bridget L. · Se revisó hace alrededor de 3 años

Jason C. · Se revisó hace alrededor de 3 años

Task 2 throws error but responses returned are as expected

Ayush A. · Se revisó hace alrededor de 3 años

finally managed to get it completed but error messages or problems can be explained in a better manner. thanks for fixing the issues

Aakash S. · Se revisó hace alrededor de 3 años

Manikanta A. · Se revisó hace alrededor de 3 años

Srikant B. · Se revisó hace alrededor de 3 años

its ok

Edgar L. · Se revisó hace alrededor de 3 años

Srikant B. · Se revisó hace alrededor de 3 años

task 2 and 3 are in bug

alaaeddine z. · Se revisó hace alrededor de 3 años

Dmytro K. · Se revisó hace alrededor de 3 años

Task 2 , Completion validation is quite weird kind of, It took a lot of time in understanding how the evaluation works, eventhough the proxy was working fine, Rating/Review section helped me :D , regarding the double quotes in w.r.t JS file. The error messages aren't that helpful also.

Sujith T. · Se revisó hace alrededor de 3 años

This lab was definitely a "challenge" as the name stands. I find it very hard to someone who doesn't have experience with Apigee to pass on this lab on the first attempt, because there are some requirements that we haven't learned during the course. I have some difficultly specially with the "jsonPath" template, because I was having some difficulty figuring the second part of the command where we have to point to the variable (response.content for example). I gave two stars because I got very frustrated for two reasons: 1) Despite the fact that my API was working as intended, I was still getting errors saying that my AssignMessage policy was incorrect. That was because I had some line breaks in there because of indentation that I added, after I put the entire json in a single line it worked. I again had this errors with my JavaScript file because I was using single quotes instead of double quotes. Kind of dumb but I failed on my second attempt because I was debugging this and trying to understand why I was getting a wrong answer despite the fact that my API was working. 2) Apigee code panel is very bad! It doesn't have autocomplete, doesn't have highlight, do only basic validation. Like, come on Google, you can do better than that! It's specially frustrating because I need to wait for the API to deploy, start a debug session, sometimes the debug session takes some time before the requests start showing up... Well, very time consuming! I really love Apigee and it's functionalities, but the code editor needs some serious improvements. I know that Google already have code editor components out there, they just need to add those to Apigee!

Anderson P. · Se revisó hace alrededor de 3 años

Pablo P. · Se revisó hace alrededor de 3 años

Mario C. · Se revisó hace alrededor de 3 años

Saurabh D. · Se revisó hace alrededor de 3 años

No garantizamos que las opiniones publicadas provengan de consumidores que hayan comprado o utilizado los productos. Google no verifica las opiniones.