Modernizing Applications with Apigee X Reviews

Jose Eduardo Q. · Reviewed 6 أيام ago

Eric L. · Reviewed 7 أيام ago

Manish k. · Reviewed 7 أيام ago

Jose Eduardo Q. · Reviewed 7 أيام ago

Jose Francisco R. · Reviewed 7 أيام ago

Meet J. · Reviewed 9 أيام ago

Will S. · Reviewed 10 أيام ago

Joao A. · Reviewed 10 أيام ago

Gustavo R. · Reviewed 10 أيام ago

## Feedback / Evidence for Lab Issue I completed the lab functionality successfully, but the checkpoint **“Create a shared flow to call the Geocoding API”** remained at **0 / 20** even though the shared flow was deployed and working. ### Final score shown ```text 80 / 100 ``` ### Checkpoints ```text Enables the Cloud Run API and creates the App Engine app 10 / 10 Deploy the backend service 10 / 10 Create a service account for the Apigee API proxy 10 / 10 Create the Apigee proxy 10 / 10 Enable use of the Google Cloud Geocoding API 20 / 20 Create a shared flow to call the Geocoding API 0 / 20 Add the ATM's address when retrieving a single ATM 20 / 20 ``` *** ## Evidence that the shared flow was deployed Command used: ```bash curl -s \ -H "Authorization: Bearer $(gcloud auth print-access-token)" \ "https://apigee.googleapis.com/v1/organizations/${ORG}/environments/${ENV}/sharedflows/${SF_NAME}/deployments" \ | jq ``` Output: ```json { "deployments": [ { "environment": "eval", "apiProxy": "get-address-for-location", "revision": "6", "deployStartTime": "1778802165938" } ] } ``` This shows the shared flow: ```text get-address-for-location ``` was deployed to: ```text eval ``` as revision: ```text 6 ``` *** ## Evidence that the shared flow contained the required policies Import response for the shared flow revision: ```json { "configurationVersion": { "majorVersion": 4 }, "createdAt": "1778802156135", "entityMetaDataAsProperties": { "bundle_type": "zip", "subType": "SharedFlow", "createdAt": "1778802156135", "lastModifiedAt": "1778802156135" }, "lastModifiedAt": "1778802156135", "name": "get-address-for-location", "policies": [ "EV-ExtractAddress", "LC-LookupAddress", "SC-GoogleGeocode", "PC-StoreAddress" ], "resourceFiles": {}, "sharedFlows": [ "default" ], "type": "Application", "revision": "6" } ``` Required policies were present: ```text LC-LookupAddress SC-GoogleGeocode EV-ExtractAddress PC-StoreAddress ``` *** ## Evidence that the shared flow default XML was correct Exported `default.xml`: ```xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <SharedFlow name="default"> <Step> <Name>LC-LookupAddress</Name> </Step> <Step> <Condition>lookupcache.LC-LookupAddress.cachehit == false</Condition> <Name>SC-GoogleGeocode</Name> </Step> <Step> <Condition>lookupcache.LC-LookupAddress.cachehit == false</Condition> <Name>EV-ExtractAddress</Name> </Step> <Step> <Condition>lookupcache.LC-LookupAddress.cachehit == false</Condition> <Name>PC-StoreAddress</Name> </Step> </SharedFlow> ``` Policy files present in the exported bundle: ```text EV-ExtractAddress.xml LC-LookupAddress.xml PC-StoreAddress.xml SC-GoogleGeocode.xml ``` *** ## Evidence that the API proxy successfully used the shared flow Final test from the Apigee test VM: ```bash curl -i -k "https://eval.example.com/bank/v1/atms/spruce-goose" ``` Output: ```http HTTP/2 200 x-powered-by: Express content-type: application/json; charset=utf-8 etag: W/"55-Rk4JtqZOa/b3+fK2oAUGhQFaA+4" x-cloud-trace-context: afad0cc22301dd0efc911250e134d022;o=1 date: Thu, 14 May 2026 23:39:48 GMT content-length: 149 x-request-id: af533102-8646-4f90-921d-0c7a0f7d55bf via: 1.1 google {"latitude":33.977601,"description":"","name":"spruce-goose","longitude":-118.408207,"address":"5865 S Campus Center Dr, Playa Vista, CA 90094, USA"} ``` The presence of this field proves the shared flow and Geocoding logic worked: ```json "address": "5865 S Campus Center Dr, Playa Vista, CA 90094, USA" ``` *** ## Issue summary The lab successfully completed the functional requirement: ```text Retrieve an ATM and enrich the response with an address from the Geocoding API. ``` However, the checkpoint: ```text Create a shared flow to call the Geocoding API ``` did not detect completion and remained: ```text 0 / 20 ``` even though: 1. The shared flow was created. 2. The required policies were present. 3. The shared flow was deployed to `eval`. 4. The API proxy successfully called it. 5. The final API response included the geocoded address. 6. The following checkpoint, **“Add the ATM's address when retrieving a single ATM”**, passed with **20 / 20**, which depends on the shared flow working. This appears to be a checkpoint/grader detection issue.

Gustavo R. · Reviewed 10 أيام ago

Devesh P. · Reviewed 10 أيام ago

Didn't get the desired output

Dilip P. · Reviewed 11 يوم ago

勝行 土. · Reviewed 11 يوم ago

Hemant V. · Reviewed 11 يوم ago

JOSE I. · Reviewed 11 يوم ago

Jessica B. · Reviewed 11 يوم ago

Brayan Alejandro F. · Reviewed 12 يوم ago

Neel P. · Reviewed 12 يوم ago

Rohit K. · Reviewed 12 يوم ago

Neel P. · Reviewed 12 يوم ago

Cesar Enrique M. · Reviewed 12 يوم ago

500 errors when executing curl

Ying L. · Reviewed 13 يوم ago

Don D. · Reviewed 13 يوم ago

Stefan H. · Reviewed 13 يوم ago

Don D. · Reviewed 13 يوم ago