Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam Associate Cloud Engineer All Questions

View all questions & answers for the Associate Cloud Engineer exam

Exam Associate Cloud Engineer topic 1 question 256 discussion

Actual exam question from Google's Associate Cloud Engineer
Question #: 256
Topic #: 1
[All Associate Cloud Engineer Questions]

You have deployed an application on a Compute Engine instance. An external consultant needs to access the Linux-based instance. The consultant is connected to your corporate network through a VPN connection, but the consultant has no Google account. What should you do?

  • A. Instruct the external consultant to use the gcloud compute ssh command line tool by using Identity-Aware Proxy to access the instance.
  • B. Instruct the external consultant to use the gcloud compute ssh command line tool by using the public IP address of the instance to access it.
  • C. Instruct the external consultant to generate an SSH key pair, and request the public key from the consultant. Add the public key to the instance yourself, and have the consultant access the instance through SSH with their private key.
  • D. Instruct the external consultant to generate an SSH key pair, and request the private key from the consultant. Add the private key to the instance yourself, and have the consultant access the instance through SSH with their public key.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Cynthia2023
Highly Voted 10 months, 3 weeks ago
Selected Answer: C
A. Using Identity-Aware Proxy (IAP): While IAP is a secure method of accessing Compute Engine instances, it typically requires a Google account for authentication, which the consultant does not have.
upvoted 7 times
...
JB28
Highly Voted 10 months, 1 week ago
The correct answer is **C**. To allow an external consultant to access a Linux-based Compute Engine instance, you should: - Instruct the external consultant to generate an **SSH key pair**. This will result in a public key and a private key. - Request the **public key** from the consultant. The public key can be shared without compromising security. - Add the public key to the instance yourself. This will allow the consultant to authenticate with the Compute Engine instance. - Have the consultant access the instance through SSH with their **private key**. The private key should be kept secret and not shared. The other options (A, B, and D) are not correct because they either require the consultant to have a Google account, expose the instance to the public internet, or involve sharing the private key, which is a security risk.
upvoted 6 times
...
FormacionCloud314
Most Recent 1 week, 5 days ago
The correct answer is C, why is option A discarded, being complementary with previous answers, see question number 152... It says it very clear, the auditor is connected through the VPN network, if we observe the documentation based on IAP, it is recommended for uses outside the VPN, (...IAP is a building block toward BeyondCorp, an enterprise security model that enables employees to work from untrusted networks without using a VPN....). My answer will be C https://cloud.google.com/iap/docs/external-identities
upvoted 1 times
...
Chetantest07
1 month, 3 weeks ago
Selected Answer: A
A. IAP can work with no google account.https://cloud.google.com/iap/docs/external-identities
upvoted 3 times
...
denno22
2 months ago
Selected Answer: A
https://cloud.google.com/iap/docs/external-identities.
upvoted 1 times
...
C0D3LK
2 months, 2 weeks ago
Selected Answer: C
Although its confusing and contradicting with Question 152, I would proceed to choose C for this. Question states no google account and the consultant is connected through VPN to the corporate network also its "an instant", not many..
upvoted 1 times
...
Timfdklfajlksdjlakf
2 months, 3 weeks ago
Selected Answer: C
This is correct. For IAP you need a google account. Read the damn question, it clearly states that he doesn't have a google account goshdarnit!
upvoted 1 times
...
user636
4 months ago
IMO answer is "A". IAP does not require Google account. There are other authentication methods supported by IAP too. Ref: https://cloud.google.com/iap/docs/authenticate-users-external-identities
upvoted 1 times
...
ccpmad
6 months, 1 week ago
A requires a Google account and the consultant has not. So it is C.
upvoted 1 times
...
adsdadasdad
6 months, 3 weeks ago
Selected Answer: A
Should be A based on the previous questions
upvoted 3 times
...
STEVE_PEGLEG
9 months, 3 weeks ago
Selected Answer: A
See responses on question #152 And https://cloud.google.com/iap/docs/external-identities. RE: IAP "This is useful if your application is already using an external authentication system, and migrating your users to Google accounts is impractical"
upvoted 5 times
leoalvarezh
9 months, 1 week ago
but the consultant is already in the corporate network through VPN, no need an external access
upvoted 2 times
...
...
YANGGE
9 months, 4 weeks ago
A (IAP) is the solution
upvoted 3 times
...
KelvinToo
10 months, 3 weeks ago
Selected Answer: C
Per ChatGPT, Option C provides a secure and recommended method for granting the external consultant access to the Compute Engine instance using SSH key authentication without the need for a Google account.
upvoted 4 times
...
shiowbah
10 months, 4 weeks ago
C. Instruct the external consultant to generate an SSH key pair, and request the public key from the consultant. Add the public key to the instance yourself, and have the consultant access the instance through SSH with their private key.
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...