Automation & Scripting Flashcards

Which flag is required by 'peer lifecycle chaincode approveformyorg' to link the approval to a specific installed package?

Answer: --package-id

--package-id supplies the installed package identifier the organization approves.

Which command lets a script see which organizations have approved a chaincode definition before committing it?

Answer: peer lifecycle chaincode checkcommitreadiness

checkcommitreadiness prints a true/false approval status per channel member org.

When upgrading a chaincode with the Fabric 2.x lifecycle, what must happen to the --sequence value in the new definition?

Answer: It must be incremented by one

Each update to a committed definition requires the sequence to increase by exactly one.

A chaincode is committed with --init-required. How must the first transaction be sent?

Answer: With --isInit on peer chaincode invoke

Init-required chaincode must have Init invoked first using the --isInit flag before other invokes succeed.

A CLI invoke fails with an endorsement policy error on a policy requiring Org1 and Org2. What is the most likely script fix?

Answer: Add --peerAddresses and --tlsRootCertFiles for peers of both orgs

The invoke must target enough peers from the required orgs so the client collects the needed endorsements.

For chaincode-as-a-service, which file in the package's code archive tells the peer how to reach the external chaincode server?

Answer: connection.json

connection.json holds the address and TLS settings for the external chaincode server.

Why must a script run 'peer lifecycle chaincode install' against each endorsing peer?

Answer: Each peer needs its own copy of the package to execute it for endorsement

Chaincode is installed per peer, and only peers with the package can simulate and endorse transactions.