Free Professional Cloud Network Engineer Exam Braindumps (page: 20)

Page 19 of 55

You want to use Partner Interconnect to connect your on-premises network with your VPC. You already have an Interconnect partner.

What should you first?

  1. Log in to your partner's portal and request the VLAN attachment there.
  2. Ask your Interconnect partner to provision a physical connection to Google.
  3. Create a Partner Interconnect type VLAN attachment in the GCP Console and retrieve the pairing key.
  4. Run gcloud compute interconnect attachments partner update <attachment> / -- region <region> --admin-enabled.

Answer(s): B

Explanation:

https://cloud.google.com/network-connectivity/docs/interconnect/concepts/partner- overview?hl=En#provisioning "To provision a Partner Interconnect connection with a service provider, you start by connecting your on-premises network to a supported service provider. Work with the service provider to establish connectivity.



You need to centralize the Identity and Access Management permissions and email distribution for the WebServices Team as efficiently as possible.

What should you do?

  1. Create a Google Group for the WebServices Team.
  2. Create a G Suite Domain for the WebServices Team.
  3. Create a new Cloud Identity Domain for the WebServices Team.
  4. Create a new Custom Role for all members of the WebServices Team.

Answer(s): A



You are using the gcloud command line tool to create a new custom role in a project by coping a predefined role. You receive this error message:

INVALID_ARGUMENT: Permission resourcemanager.projects.list is not valid

What should you do?

  1. Add the resourcemanager.projects.get permission, and try again.
  2. Try again with a different role with a new name but the same permissions.
  3. Remove the resourcemanager.projects.list permission, and try again.
  4. Add the resourcemanager.projects.setIamPolicy permission, and try again.

Answer(s): C


Reference:

https://cloud.google.com/iam/docs/understanding-custom-roles



One instance in your VPC is configured to run with a private IP address only. You want to ensure that even if this instance is deleted, its current private IP address will not be automatically assigned to a different instance.

In the GCP Console, what should you do?

  1. Assign a public IP address to the instance.
  2. Assign a new reserved internal IP address to the instance.
  3. Change the instance's current internal IP address to static.
  4. Add custom metadata to the instance with key internal-address and value reserved.

Answer(s): C

Explanation:

https://cloud.google.com/compute/docs/ip-addresses/reserve-static-internal-ip- address#reservenewip Since here https://cloud.google.com/compute/docs/ip-addresses/reserve- static-internal-ip-address#reservenewip it is written that "automatically allocated or an unused address from an existing subnet".






Post your Comments and Discuss Google Professional Cloud Network Engineer exam with other Community members:

Professional Cloud Network Engineer Discussions & Posts